12-30-2011 03:44 AM
Hi folks,
i was logged in to this device in monday normally and in tuesday when i trying to
Cisco SW#telnet 172.17.1.1
Trying 172.17.1.1 ...
% Connection refused by remote hos
and i compare the current configuration with last configuration in monday i found no change, any one can help me as this is critical issue and for your information this device in live network also cpu is normally and memory.
Solved! Go to Solution.
12-30-2011 06:07 AM
It could be its vty lines are exhausted.
This sometimes happens when an automated tool is logging in and not releasing the line upon job completion. If you can get in to console the commands "show lines" and "show users" may give you some indicators if my thought is the case.
Besides fixing the root cause, you can try adding a separate vty line with a low timeout set.
12-30-2011 06:07 AM
It could be its vty lines are exhausted.
This sometimes happens when an automated tool is logging in and not releasing the line upon job completion. If you can get in to console the commands "show lines" and "show users" may give you some indicators if my thought is the case.
Besides fixing the root cause, you can try adding a separate vty line with a low timeout set.
01-04-2012 08:53 AM
thank you, it is working after clearing the line vtys
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide