try doing detailed "show line" for each of the vty's and see
if there's something different between a non-echo session and
a normal one.
there's a certain amount of state that seems to get saved between
inbound telnet sessions, that really sholdn't be, the most blatent
example being the "terminal length" value.
George
> From cisco-nsp-request@puck.nether.net Mon Jun 11 17:31:25 2001
> Resent-Date: Mon, 11 Jun 2001 17:31:20 -0400
> Received-Date: Mon, 11 Jun 2001 17:27:27 -0400
> To: cisco-nsp@puck.nether.net
> From: CARL.P.HIRSCH@sargentlundy.com
> Date: Mon, 11 Jun 2001 16:17:18 -0500
> X-MIMETrack: Serialize by Router on mail01/Sargentlundy(Release 5.0.7 |March 21, 2001) at
> 06/11/2001 04:17:24 PM
> Subject: [nsp] Telnet Character Echo on Cat3524
> Resent-From: cisco-nsp@puck.nether.net
> X-Mailing-List: <cisco-nsp@puck.nether.net> archive/latest/6769
> X-Loop: cisco-nsp@puck.nether.net
> Precedence: list
> Resent-Sender: cisco-nsp-request@puck.nether.net
>
> A number of our 3524 switches have stopped echoing characters during Telnet
> sessions. For example - "sh run" would not be visible as you type it, but
> the command does go through.
>
> This can be reproduced from multiple terminals, so I'm assuming it's not
> Telnet client-related.
>
> Nothing in the config seems to be related to the issue.
>
> Any ideas?
>
> thanks,
> -carl hirsch
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:41 EDT