Telnet to router not functional any more

[John Cheetley]

Please let me know if this is in the wrong forum and will re-assign

Can no longer telnet from windows command line of 192.168.0.102 to 2691 router 192.168.0.XX

Can connect via hyperterminal OK via 9600

Error message is "couldn't open connection to host on port 23: connection failed"

Troubleshooting

Can ping and tracert to router OK

Telnet in services.msc was disabled so enabled and rebooted machine. Tried again to previous above error message

Error message is "% Connection timed out; remote host not responding"

If I close the hyperterminal, power off router and turn on again, open new HT session, am back at the rommon prompt. Can type reset and takes me back to the standard admin prompt and continue working

And windows firewall is off momentarily

I checked port 23 via T1 shopper and advised "the port isn't responding"

Went back to services.msc. Changed telnet to manual. Applied to no affect

And port 23 is in "listening" mode as netstat -a shows

Thanks in advance

[John Cheetley]

Hi Richard,

Sorry about delay.

Please find attached as requested..

[Richard Burts]

Thanks for posting the config. There are a number of things in it that I would question. The biggest issue is that each of the interfaces has the shutdown command. If all the interfaces are shutdown then how can anything work?

Other things include I question why you have configured no ip cef and why you configured no ip classless. It has been a long time since it was common to enforce classful routing and I wonder why you are doing that here?

Also you have configured two DHCP scopes and in both scopes the default router address is not in the subnet of the scope. For the clients to work best the default router should be in the same subnet as the client.

HTH

Rick

[John Cheetley]

Hi Richard,

Sorry about delay

Thanks for your comments.

I have brought both interfaces back up. removed no ip cef, replaced no ip classless with ip classless

I can now access the router via telnet. (I have been staring at this for too long. a second set of educated eyes is better than one)

I assume that for the DHCP scopes, I should be using ip helper-address to assist

[Richard Burts]

I am glad to know that access to the router using telnet is working again. I agree that sometimes a second pair of eyes is very helpful.

Since the DHCP scopes are on the router for subnets that are locally connected on the router I see no need for helper address. Helper address is used when the client subnet is remote from the machine where the DHCP copes are configured.

HTH

Rick

[John Cheetley]

Hi Richard, 

I had thought the phones (Voice) had to go on a separate ip range to the Data for purpose of (for lack of a better word) identification to either the switch or the router

[Richard Burts]

I agree that frequently there are reasons to have one IP range for voice and a different IP range for data.That has nothing to do with whether you need to use helper address. The reason to use helper address would be that the DHCP scopes are configured on a device which does not have a direct (local) connection to the subnet where the clients are. When the clients are remote from the server then you need helper address. In your case the clients are connected to the router where the scopes are configured and you do not need helper address.

HTH

Rick