Group, I really appreciate Kevin's help I have implemented the exec-timeout 0 0 into the lines. I just wanted to add another note for everyone on the list reading this. I have been using Caslow's second edition (which I am very impressed with so far) for my lab study. There is an additional note listed in Bruce's book saying "With many versions of the IOS Terminal Server configurations may result in lines listed as being used when they never have been used. A remedy to this problem is adding the "Modem host" command in line configuration mode in addition to the "transport input all" command. Along with Kevin's advice and this additional command sessions shown are accurate and don't timeout. It's working great. Thanks Kevin and Bruce. >>>Brian >From: "Kevin Wigle" <[EMAIL PROTECTED]> >To: "Brian Lodwick" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> >Subject: Re: terminal server flakey >Date: Sat, 20 Jan 2001 17:04:30 -0500 > >"I have configured the lines with no passwords or timout" > >If you didn't do anything then by default, exec will time out after 10 >minutes. > >So if you got all 8 lines up its pretty easy to think that a few might be >standing there unused for 10 minutes while you're playing with the >others..... > >So you have to give the command "exec-timeout 0 0" which will disable >timeout completely. > >from CCO - the font of all knowledge (and the first hit on my search on >exec-timeout) > >**************** >Setting the EXEC Timeout Intervals >The EXEC command interpreter waits for a specified interval of time until >the user starts input. If no input is detected, the EXEC resumes the >current >connection. If no connections exist, the EXEC returns the terminal to the >idle state and disconnects the incoming session. > >To set this interval, use the exec-timeout line configuration subcommand. >The full syntax of the command follows. > >exec-timeout minutes [seconds] >no exec-timeout >The argument minutes is the number of minutes, and the optional argument >seconds specifies additional interval time in seconds. The default interval >is ten minutes; an interval of zero specifies no time-outs. > >The no exec-timeout subcommand removes the time-out definition. It is the >same as entering exec timeout 0. > >Example: >This command sets an interval of 2 minutes, 30 seconds. > >exec-timeout 2 30 > >This command sets an interval of 10 seconds: > >exec-timeout 0 10 >******************** > >Every console (con 0) needs the command. > >We just had this discussion on this list a few days ago........ > >Kevin Wigle > > > > values, ----- Original Message ----- >From: "Brian Lodwick" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Saturday, 20 January, 2001 14:13 >Subject: terminal server flakey > > > > hi group, > > I have configured a terminal server on a 2511. It works great in the > > beginning, but then it starts to flake out on me. I'll try to report >what > > happens. I notice right when everything is powered up I can connect to >all >8 > > of the routers connected using their hostname and it is exactly as I > > expected. The issue normally occurs after I've been reverse telnetted >into >a > > router for a little while then I back back out of that one and try to >telnet > > to another one and I can't get to it then after I can only get to a >couple > > of them. All of the connections are disconnected after I back out. It >just > > appears to be a glitch or possibly a timeout? Has anyone seen anything >like > > this before? The only way I can fix it is to reboot. I will outline the > > config. > > > > This may be the kicker I am using IOS 11.1 on the term. server. I am > > planning to upgrade, but wanted to see if I was overlooking something. > > > > All I did was on the terminal server I configured a host file for each > > router calling them r1, r2, r3... using the loopback for the ip, and >200_ > > for the port. I have configured the lines with no passwords or timout > > values, I only added transport input all for lines 0-8. Speeds are set >to > > 9600. > > > > On each of the other routers I have left the console line blank not even >a > > password is set. > > > > Like I said everything works great in the beginning, but... > > Thanks in advance guys! > > > > >>>Brian > > > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > _________________________________ > > FAQ, list archives, and subscription info: >http://www.groupstudy.com/list/cisco.html > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] > _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com _________________________________ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
