Member Avatar for kjklls

i'm having a problem when i try to telnet my netgear router (JWNR2000v2)

i could ping it but when i try to telnet it using puTTy, it says that the connection is closed by the remote host.

i tried using telnetEnable.exe but i don't know if its working or not.

i also tried to connect to other routers and it's working just fine, so i'm guessing it has something to do with the netgear router or its settings.

what could my problem be? hope you guys can help me thanks

  • 4 Contributors
  • 9 Replies
  • 795 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by JorgeM

Dani AI

Generated

Brief expert summary and a compact diagnostic checklist based on the thread (references: , , , ).

When PuTTY reports "Connection closed by remote host" after a successful ping, the router is reachable but the TCP session is being dropped. That is different from an outright refusal (no listener). Common causes: no telnet daemon in the firmware or it is disabled, management is allowed only from specific interfaces/addresses, the router drops sessions due to an ACL or firmware behaviour, or the service is present but immediately closes for authentication/host-check reasons. As observed, many consumer devices do not expose a Telnet shell by default; 's nmap idea is the right diagnostic direction.

Practical, non-invasive checks (run from a machine on the same LAN):

# quick port check with nmap
nmap -Pn -p 23 -sV 192.168.1.1

# plain telnet test (Linux/Windows with client enabled)
telnet 192.168.1.1 23

# netcat quick probe (if available)
nc -vz 192.168.1.1 23

Interpreting results: if port 23 is "closed/filtered", no Telnet listener is available. If it shows "open" but the session closes immediately, the device is accepting TCP then dropping the session (often due to ACL/management-scope or because the service expects a different protocol). Confirm tests are run from the LAN side (not WAN), try temporarily disabling the workstation firewall, and verify the router IP/gateway is correct.

If Telnet is not exposed, options are: use the router's web management or any supported secure remote management (SSH if present); check firmware updates or vendor documentation (as pointed out) for management options; or, for advanced users, investigate serial/console access or third-party firmware—both carry risk and may void warranty.

Recommended Answers

All 9 Replies

Member Avatar for JorgeM

so i'm guessing it has something to do with the netgear router or its settings.

Your netgear router may simply not be running a telnet server service. Have you checked its documentation?

Member Avatar for kjklls

thanks. how would i know if my router is not running a telnet server service?

Member Avatar for Member #114542

As JorgeM said, you need to have telnet activated on the router itself.

Netgear's website says to go to the Security tab, and click the Access sub-tab. There, you enable telnet. Source

Member Avatar for kjklls

Thanks Mouche but i think that configuration is for switches

Member Avatar for JorgeM

It maybe that this device does not have the ability to run telnet. That is why i suggested to have a look at the support manual. Telnet isn't available on every network device.

Member Avatar for kjklls

i'll check the device manual. thanks JorgeM

Member Avatar for rch1231

Hello,

You could always try nmap to see what ports are open on the router. Netgears usually have a built in web server for configuration and you just put the IP address of the router in your browser.

Member Avatar for kjklls

i finally got this working for me. thanks for the help guys :)

Member Avatar for JorgeM

Glad you sorted it out.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.