NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

sixpiece's avatar
sixpiece
Aspirant
Feb 14, 2021
Solved

Would like to enable Telnet for R6200

I tried Port Forwarding, and Port Forwarding Telnet. 

 

I tried some of the tools designed for Windows and a C program and a python script and a TelnetEnable1 and a TelnetEnable2 for Windows tools.

 

I tried the local host, local host and the specific host reserved via port forwarding for Telnet. I tried the password they recommended and the password of my router.

 

I am still unable to get Telnet to work from my computer, any suggestions?

  • > Would like to enable Telnet [...]

     

       Why?

     

    > [...] for R6200

     

       Firmware version?

     

    > I tried Port Forwarding, and Port Forwarding Telnet.

     

       If you want to Telnet _into_ the R6200, then port forwarding won't
    help.

     

    > I tried some of the tools [...]

     

       "tried" is not a useful problem description.  It does not say what
    you did.  It does not say what happened when you did it.  As usual,
    showing actual actions (commands) with their actual results (error
    messages, LED indicators, ...) can be more helpful than vague
    descriptions or interpretations.


    > I tried the local host, local host and the specific host [...]

     

       I don't know what any of that means.

     

       Telnet access to Netgear routers is not a supported feature, and it
    seems to have disappeared from recent firmware versions on models where
    it had worked previously.

     

       Possibly interesting:

     

          https://community.netgear.com/t5/x/x/m-p/1813948

4 Replies

  • > Would like to enable Telnet [...]

     

       Why?

     

    > [...] for R6200

     

       Firmware version?

     

    > I tried Port Forwarding, and Port Forwarding Telnet.

     

       If you want to Telnet _into_ the R6200, then port forwarding won't
    help.

     

    > I tried some of the tools [...]

     

       "tried" is not a useful problem description.  It does not say what
    you did.  It does not say what happened when you did it.  As usual,
    showing actual actions (commands) with their actual results (error
    messages, LED indicators, ...) can be more helpful than vague
    descriptions or interpretations.


    > I tried the local host, local host and the specific host [...]

     

       I don't know what any of that means.

     

       Telnet access to Netgear routers is not a supported feature, and it
    seems to have disappeared from recent firmware versions on models where
    it had worked previously.

     

       Possibly interesting:

     

          https://community.netgear.com/t5/x/x/m-p/1813948

    • sixpiece's avatar
      sixpiece
      Aspirant

      yes, sorry, I wanted to use Telnet to check SMTP connections but also to get a feel for the RFC requirements. I enjoy for example learning whether an email would be RFC 5322 compliant or not. It's of interest to me since I am running some mail servers and I want to understand the handshaking signals. It's also of interest to check the ports.

       

      Long and short, thanks to a Microsoft representative, I realize that the ports such as port 25 are blocked by my ISP. So I can still check through a proxy network or use other ports that are not blocked such as 587.

       

      The information you interpreted such as telnetting into the router is perhaps of interest but it's not actually pertinent to me at the moment.

       

      Thank you for your help.

      • antinode's avatar
        antinode
        Guru

        > [...] I wanted to use Telnet to check SMTP connections [...]

         

           "connections" between what and what?  Without a better idea of what
        you're actually doing, it's tough to say what should or shouldn't work
        and why.

         

        > [...] I am running some mail servers and I want to understand the
        > handshaking signals. It's also of interest to check the ports. [...]

         

           You can talk to a server on your LAN from a client on your LAN
        without any port forwarding on your router.  Or any interference from
        your ISP.

         

        > [...] I realize that the ports such as port 25 are blocked by my ISP.
        > [...]

         

           That would be typical for residential service, but I'd expect it to
        affect only incoming connections.  Ask your ISP?

         

           For the usual problems with port forwarding, see:

         

              https://community.netgear.com/t5/x/x/m-p/1859106