"all" works because telnet is a subset of "all" - it is included without
being specifically named. Do a "show line" to determine the mapping of line
numbers to ports - then do a "show line 1" or whatever. Lots more output!
Look on the line that starts "Allowed transports"
We are used to configurin
I think, as is often the case, I wasn't clear enough. Let me
try to restate the issue another way.
When you connect a terminal server to a console port, the
telnet protocol is not operating on that link. That link is a
simple async serial terminal session. Because of that, I don't
understa
?
Tim
-Original Message-
From: John Neiberger [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 28, 2002 9:59 PM
To: [EMAIL PROTECTED]
Subject: Re: RE: Transport Input Telnet and Terminal Servers [7:33511]
I think, as is often the case, I wasn't clear enough. Let me
try to restate t
re coffee?
>
> Tim
>
> -Original Message-----
> From: John Neiberger [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 28, 2002 9:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: RE: Transport Input Telnet and Terminal Servers
[7:33511]
>
>
> I think, as is oft
M
> To: [EMAIL PROTECTED]
> Subject: RE: RE: Transport Input Telnet and Terminal Servers [7:33511]
>
> That makes sense except for the fact that the telnet protocol
> is *not* running on the console link! It's called reverse
> telnet but that doesn't describe the protocol tha
5 matches
Mail list logo