I have conducted research online for a solution to this issue but have not found one yet.
When attempting to telnet to an unresponsive address from a switch or router, the CLI shows "Trying x.x.x.x..." and eventually times out. Example:
Trying 18.104.22.168 ...
% Connection timed out; remote host not responding
I am looking for the correct break sequence and/or terminal emulator settings that will cause the telnet session attempt to stop so that you do not have to wait for it to timeout.
My colleagues and I have unsuccessfully attempted the following break sequences using SecureCRT version 7 (with terminal emulation VT100) as well as with the Windows 7 Command Prompt:
- ctrl + c
- ctrl + c + c
- ctrl + z
- ctrl + z + z
- ctrl + shift + 6
- ctrl + shift + 6 + 6
- ctrl + shift + 6 then x
- ctrl + shift + 6 then x then x
We are able to successfully break out of traceroute and ping attempts using ctrl + shift + 6.
Does anyone know what break sequence and/or terminal emulation settings should be used to sucessfully break out of telnet session attempts?
I believe the ctrl+shift+6+x (CS6x) only works when you're consoled into the device and then telnetting from there. When you're telnetting from another telnet session, I don't believe this combination will work. You can alleviate some of the pain by changing your syn-wait time to 5. "ip tcp synwait-time 5"
If you want to change to ctrl-c, you can change your escape character to 3:
line vty 0 4