Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) more stuff!
Mark,
You are 100% correct regarding how telnet works. Unfortunately it has
nothing to do with the problem at hand. :-)
It is not an echo problem. If it were an echo problem, typing 'helo' or
'quit' to an smtp server would get a response -- nothing happens. It
looks like something is screwy with the socket connection.
Try it for yourself...
Steve
On Mon, 6 Jul 1998, Mark C Hudson wrote:
> -----Original Message-----
> From: Rob Myers <rmyers@unicom.net>
> To: ascend-users@max.bungi.com <ascend-users@max.bungi.com>
> Date: Monday, July 06, 1998 3:45 PM
> Subject: (ASCEND) more stuff!
>
>
> >This happens whether you are using NAT or not. I don't understand why,
> >but for some reason you can -ONLY- telnet to port 23 of a box from the
> >'ascend%' prompt.
> >
> >If you try to telnet to port <anything else> you don't get any of your
> >keystrokes echoed back.
>
> This just depends on what it is you are telnetting to. Most other services
> (inc smtp) don't echo keystrokes back to you. However, the connection still
> works. Turn on local echo if you want to read it....
>
> The exact same behaviour occurs on a windows telnet, and it is not a bug.
>
> Most unix telnet programs switch to line-by-line mode if you telnet to
> anything other than port 23, which is why you get characters echoed back. MS
> Windows telnet and the telnet program on the ascends do not, and
rely on the
> host at the other end to echo characters back. This does not happen with
> most protocols.
>
> Mark
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: