cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3972
Views
0
Helpful
5
Replies

Remote access telnet to Router is not working

frank2812
Level 1
Level 1

Even though the router is configure to accept  telnet connection we can not connect. I atached the sh run  of the Router. We can do ping to the router. I proved doing telnet from inside the same router but is not working like you can see in the logs down here. i proved telnet from diferent devices but is not working.

Dayco-CPA#192.168.13.1

*Dec  6 14:16:58.437: %FAN-3-FAN_FAILED: Fan 1 had a rotation error reported.

Trying 192.168.13.1 ...

% Connection refused by remote host

 

1 Accepted Solution

Accepted Solutions

Rolf Fischer
Level 9
Level 9

Franklin,

the exec-timeout is 0, so maybe all the vtys are just in use and never time out.

Could you check this with show line vty 0 4 and clear the lines if necessary?

Saludos

Rolf

[EDIT]:

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ...

% Connection refused by remote host

R1#show line vty 0 4

   Tty Typ     Tx/Rx    A Modem  Roty AccO AccI   Uses   Noise  Overruns   Int

*   130 VTY              -    -      -    -    -      6       0     0/0       -

*   131 VTY              -    -      -    -    -      5       0     0/0       -

*   132 VTY              -    -      -    -    -      4       0     0/0       -

*   133 VTY              -    -      -    -    -      4       0     0/0       -

*   134 VTY              -    -      -    -    -      2       0     0/0       -

R1#clear line vty 3

[confirm]

[Connection to 1.1.1.1 closed by foreign host]

R1#show line vty 0 4

   Tty Typ     Tx/Rx    A Modem  Roty AccO AccI   Uses   Noise  Overruns   Int

*   130 VTY              -    -      -    -    -      6       0     0/0       -

*   131 VTY              -    -      -    -    -      5       0     0/0       -

*   132 VTY              -    -      -    -    -      4       0     0/0       -

    133 VTY              -    -      -    -    -      4       0     0/0       -

    134 VTY              -    -      -    -    -      2       0     0/0       -

View solution in original post

5 Replies 5

Rolf Fischer
Level 9
Level 9

Franklin,

the exec-timeout is 0, so maybe all the vtys are just in use and never time out.

Could you check this with show line vty 0 4 and clear the lines if necessary?

Saludos

Rolf

[EDIT]:

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ... Open

R1#telnet 1.1.1.1

Trying 1.1.1.1 ...

% Connection refused by remote host

R1#show line vty 0 4

   Tty Typ     Tx/Rx    A Modem  Roty AccO AccI   Uses   Noise  Overruns   Int

*   130 VTY              -    -      -    -    -      6       0     0/0       -

*   131 VTY              -    -      -    -    -      5       0     0/0       -

*   132 VTY              -    -      -    -    -      4       0     0/0       -

*   133 VTY              -    -      -    -    -      4       0     0/0       -

*   134 VTY              -    -      -    -    -      2       0     0/0       -

R1#clear line vty 3

[confirm]

[Connection to 1.1.1.1 closed by foreign host]

R1#show line vty 0 4

   Tty Typ     Tx/Rx    A Modem  Roty AccO AccI   Uses   Noise  Overruns   Int

*   130 VTY              -    -      -    -    -      6       0     0/0       -

*   131 VTY              -    -      -    -    -      5       0     0/0       -

*   132 VTY              -    -      -    -    -      4       0     0/0       -

    133 VTY              -    -      -    -    -      4       0     0/0       -

    134 VTY              -    -      -    -    -      2       0     0/0       -

I thought the telnet gets timed out ?

I thought the telnet gets timed out ?

Well, it does; by default after 10 minutes inactivity.

But in this case the exec-timeout was set to zero, which means it never times out.

http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/frf004.html#wp1017909

HTH

Rolf

yeah sure,

then i don't think of any reason why we are not able to telnet

Franklin, try that , removing the no ecex-timeout command and kill all the current telnet sessions

lets see...

amsodhi
Level 1
Level 1

Output is pointing the issue with hardware.

I would like to do some bug scrub, please share show version output.

Also let me know, if it works fine from console.

-Amant
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: