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

[Jaime Valencia · Accepted solution]

This is not UC related, might want to move to the routing forum, or search for telnet on CSC and see where most of those questions are.

I assume you have checked the config on the ISR does allow you to telnet, right???

[John Cheetley]

Thanks Jaime for your reply

I assume you mean via enable secret etc. then yes.

[paul driver]

Hello

Have you tried turning off the software FW in this windows pc and testing?

res

Paul

[John Cheetley]

Hi Paul,

Thanks for your response. Yes. I have done that already.  :) 

[Rajeev Sharma]

Hey John,

Can you please collect #show ip socket from hyper terminal window and confirm that device is listening on port 23 moreover collect #show user and #show line as well.

Regards,
RS.

[John Cheetley]

Hi Rajeev,

Thanks for your response.

I have checked that device is listening on port 23. I will get that output for you tonight. At work now.

I only have access to hyperterminal 

I've also done a command line history check for this

shows that i used :

login local

transport input ssh. 

I did this part by mistake unfortunately. I presume this can be undone/reversed.

[John Cheetley]

Hi Rajeev,

Output as requested. Please find attached :) 

[Rajeev Sharma]

Hey John,

Please add telnet as well in the command:

#transport input ssh telnet

HTH.

Regards,

RS.

[John Cheetley]

Hi Rajeev,

Have done that command to no success via hyperterminal

conf t

transport input ssh telnet

C:\Users\Administrator>
C:\Users\Administrator>telnet 192.168.0.12
Connecting To 192.168.0.12...Could not open connection to the host, on port 23:
Connect failed

C:\Users\Administrator>

Thanks again :) 

[John Cheetley]

Hi Rajeev,

I have disabled ssh and just using telnet.

I await your comments.

[Richard Burts]

What you posted shows entering the command in global config mode

conf t

transport input ssh telnet

But you should be in line config mode to use this command

conf t

line vty 0 15

transport input ssh telnet

HTH

Rick

[John Cheetley]

Hi Richard,

Thanks for your comments.

Example of what I have done

cme_router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
cme_router(config)#line vty 0 4

cme_router(config-line)#transport input telnet
cme_router(config-line)#end
cme_router#
Mar 1 01:02:40.943: %SYS-5-CONFIG_I: Configured from console by admin on consol
ewr
Building configuration...
[OK]
cme_router#

I then get same error again 

Interestingly.

I can telnet to the 192.168.0.2 (switch)

Do sh arp

Switch>sh arp

Switch>sh arp
Protocol Address Age (min) Hardware Addr  Type    Interface
Internet 192.168.0.102 0      fcaa.14af.197f    ARPA VLAN1
Internet 192.168.0.12 0        Incomplete         ARPA

But ping and tracert times out is 2 seconds as for some reason the hardware address is missing

I started CUCM on router. Hardware address appears now

Can ping and telnet to router from switch (190.168.0.2) OK but not from DNS server of 192.168.0.102 like I used to be able to do

Interested in your thoughts :) 

[Richard Burts]

It is interesting to know that you are successful in telnet to the router from the switch but not from the server. That does demonstrate that telnet is enabled. It is possible that something in the router configuration is preventing telnet from the server (perhaps something like access-class on the vty or perhaps something else) and it is possible that something changed on the server that is preventing telnet. To help us understand the issue would you post the configuration of the router?

HTH

Rick

[John Cheetley]

Hi Richard, 

Thanks for your comments

That's what I thought. But it worked 1 week ago. 

I will supply the config file tonight when I get home.