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

Strange Telnet Issue

SystemAdminNet
Level 1
Level 1

I have Cisco 2960-48TT-L Switch ,having a strange problem that i cannot telnet it ,

1-I Am able to get access from console port

2- I can able to access it via Web Browser by giving it IP

3- I am able to access it from Cisco Network Assistant

4- Able to get ping reply

5-But not able to telnet it from my laptop ,or any pc in my my network .

When i telnet its ip command propmt window gone blank continusoly with no errors .I cant understand this issue all i can telnet other switches from same laptop/clients.

Screen shot is attached with ,Please give solution

5 Replies 5

shahhardik
Level 1
Level 1

Hey Jey,

Can you post your config, it will help us out to track the issue.

Regards,

Hardik

steve
Level 1
Level 1

Hi Jey,

As suggested by Kardik, if you post the config we can have a look at what the problem might be.

In the meantime, check the configuration under #line vty 0 15. Make sure that #transport input telnet or #transport input all is configured. In addition, what out for access lists that might be blocking your connection.

If that is all in order, run Wireshark on your machine and filter for all traffic to the switch "ip.address==x.x.x.x". Check to make sure that the three-way handshake is happening? If not, then find out why but if it is, try using a different Telnet client.

Cheers

Stephen

k_srinadh
Level 1
Level 1

Hi Jey,

  I think you might have not conigured Line vty configuration

Regards,

Srinadh.

SystemAdminNet
Level 1
Level 1

Thanks 2 All

Issued resolved by removing switch config.I think

exec-timeout 0 0

or

session-timeout 5

is creating problem so i try with no exec-timeout 0 0

But it arrive again ,So i delete switch config now reconfig IP all is working ok

Enable the "terminal monitor" so we can see some outputs, run a "sh tcp statistics"

1. then do a "debug ip tcp transactions",

2. try to telnet to an affected switch, capture the debugs and also

3. run these commands:

- sh tcp brief

- sh tcp statistics

- sh line

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:

Review Cisco Networking products for a $25 gift card