If your connection is clean, and the telnet program properly written, it will terminate the TCP session correctly when the program is closed.
It's badly written clients, or when your network connection gets cut, or your system crashes that it becomes a problem. In these instances, the TCP session isn't properly shut down. A router with default configuration will never take action to disconnect the hung session. What I typically do is configure a 240 minute (4 hour) timeout. It's long enough to give you time to think about what you're doing, and short enough that if my session is killed by a network problem or an overzealous firewall, I know I'll eventually get back in. There is also another way to deal with the problem - TCP keepalives. http://www.cisco.com/warp/public/471/tcpkeepalive.html Thanks, Shawn Michael Williams wrote: > > Daniel Cotts wrote: > > > > Be extremely careful if you configure an exec-timout of 0 0 on > > a vty port. > > It will never release! So when you drop the connection and > > again telnet into > > the box you now have one less open port. After five times (or > > number of vty > > ports) you are locked out of the box. Should you still be > > inclined to use > > this - then either (a) don't save the config (so someone can > > power cycle the > > box to let you back in) or (b) change the setting before you > > log off. > > Good point..... We have this setup on some of our routers that we commonly > just sit in all day, and if I kill the telnet process (without allowing it a > graceful exit) my session doesn't hang..... it frees up the VTY line I was > using..... Interesting..... Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=45300&t=45268 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
