I am not sure that I have seen quite what you describe. Here are some thoughts:
- are you SURE that there are no open sessions? probably the most common cause of the symptom that you describe is that all of the VTYs have sessions hanging and there is nothing to accept new sessions.
- is there any possibility that there has been some config change? is there perhaps an access-class (or permit list) which is restricting access? is it possible that transport input (or output) has changed and no longer includes telnet? (moving toward SSH)
- is it possible that someone has configured "no exec" on the vty? I have seen this when someone was trying to configure "no exec-timeout" and thought they were using a valid abbreviation when they typed "no exec". The result would be to reject any telnet attempt.
If none of these seem to explain it, then perhaps you could post that part of the running config.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...