From: Greg Ferro (gferro@xxxxxxxxxxxxxxxxxxx)
Date: Sun Jan 28 2001 - 22:12:25 GMT-3
This is normally a sign that you haven't put a no exec on the serial lines.
Try this:
line 1 16
no exec
transport input none
And you should find that these problems go away.
At 11:39 AM 28/01/2001 -0800, you wrote:
>OK, I think I am starting to get a feel for terminal server gotcha's. And
>based solely on my experience here at home, and never having been in the Lab
>itself, but trying to anticipate the kinds of things that can happen during
>troubleshooting.....
>
>It seems that the asynch lines can get "hung" for whatever reason. I am
>finding that even after fooling around doing things like changing the flow
>control that often I can still get into most of my routers. Occasionally, I
>will get a "connection refused" from one or two of them.
>
>This of course could be disastrous if it were to happen during any part of
>the lab prior to troubleshooting. It could also be one way a crafty Lab
>Proctor might try to bushwhack someone. Screw with the terminal server
>settings and let the unprepared candidate waste his three hours getting the
>TS to connect!
>
>Some combination of clear tty line X or clear line X seems to do the trick.
>Never hurts to do both.
>
>
>Chuck
>http://www.1112.net/lastpage.html
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:46 GMT-3