(ASCEND) more stuff!
owner-asc...@max.bungi.com
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.
Example:
========
ascend%telnet some.host 23
Connecting to some.host (10.0.0.2) ...
Escape character is '^]'
Connected
SunOS 5.6
login: blah
Password:
Last login: Mon Jul 6 07:31:53 from ascend.router.
=========
But at the same time....
=========
ascend% telnet some.host 25
Connecting to some.host (10.0.0.2) ...
Escape character is '^]'
Connected
220 some.host ESMTP Sendmail 8.9.0/8.9.0; Mon, 6 Jul 1998 08:00:18 -0500 (CDT)
(any keystrokes typed in are ignored, except of course the escape
character ^])
=========
This has been a persistent problem for as many releases of Ascend software
as I can think of but I haven't ever gotten upset enough about it to call
Ascend about it.
Does anyone know anything about this??
-Rob-
> From: Steve Mickeler <st...@neptune.on.ca>
> Date: Fri, 3 Jul 1998 10:04:55 -0400 (EDT)
> Subject: (ASCEND) more stuff!
>
> I mentioned in an earlier email I was having trouble with P75 and NAT
> sending connects to a customers SCO box.
>
> When I telnet to 192.168.100.2 25 I get this
>
> ascend% telnet 192.168.100.2 25
> Connecting to 192.168.100.2 ...
> Escape character is '^]'
> Connected
> 220-abc Sendmail 8.6.8.1/SCO5 ready at Fri, 3 Jul 1998 14:04:21 GMT
> 220 ESMTP spoken here
>
> After that I cant make any keystrokes, like doing a vrfy or something.
>
> If I am logged into the sco box, and run a telnet localhost 25, I can.
>
> from the ascend% prompt I can do a standard telnet to the SCO box and
> login and do all my stuff though ... this is weird!
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-use...@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
owner-asc...@max.bungi.com
I reported this problem a while back to Ascend but it happened to be in a
router doing NAT and I *assumed* (never assume so says Felix Unger :-) )
it was a NAT problem. I never tried it in a non NAT configuration until I
read this posting. This is a bogus bug and should be fixed.
The terminal mode of the routers is used mostly for debugging things. I
noticed this problem when using NAT because connections to SMTP servers
were painfully slow. This was because many smtp servers connect back to
the identd port of the machine making the connection (in the case of NAT,
the router itself). I needed to add a NAT static map of port 113 to the
router so it refuses the connection and lets smtp get on with its life. I
had to go to a workstation to test it -- I couldn't connect to smtp from
the terminal mode.
Steve
owner-asc...@max.bungi.com
-----Original Message-----
From: Steve Mickeler <st...@neptune.on.ca>
To: ascend...@bungi.com <ascend...@bungi.com>
Date: Friday, July 03, 1998 4:38 PM
Subject: (ASCEND) more stuff!
>
>I mentioned in an earlier email I was having trouble with P75 and NAT
>sending connects to a customers SCO box.
>
>When I telnet to 192.168.100.2 25 I get this
>
>ascend% telnet 192.168.100.2 25
>Connecting to 192.168.100.2 ...
>Escape character is '^]'
>Connected
>220-abc Sendmail 8.6.8.1/SCO5 ready at Fri, 3 Jul 1998 14:04:21 GMT
>220 ESMTP spoken here
>
>After that I cant make any keystrokes, like doing a vrfy or something.
You can, they just won't get echoed back to you. Try the vrfy anyway and
see! The ascend telnet program doesn't switch to line-by-line mode (just
like a windows telnet), however the unix telnet does. Either switch the
telnet to line-by-line mode when you connect to ports other than 23, or turn
on local echo!
Mark
owner-asc...@max.bungi.com
-----Original Message-----
From: Rob Myers <rmy...@unicom.net>
To: ascend...@max.bungi.com <ascend...@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.
owner-asc...@max.bungi.com
I tried 'typing blind' to a mail server's port 25 and was unable to get a
response to any command, all commands including "quit" resulted in nothing
ever being echoed back, the only way I was able to get out was to type the
escape sequence.
Shouldn't it be relatively easy anyway for Ascend to modify the code to
echo back characters? Maybe we should put in a feature request for that.
Although I rarely use an Ascend to telnet out to a specific port it is
sorely missed on the rare occasions it is needed to help debug things.
owner-asc...@max.bungi.com
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 <rmy...@unicom.net>
> To: ascend...@max.bungi.com <ascend...@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.
>
owner-asc...@max.bungi.com
> 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.
Have you tried sending a CR *and* an LF as a line terminator?
It works (modulo some garbage at the beginning of the session) for me on
port 25 using LF as a line terminator (hit ^j at the end of the line
instead of Enter). But that just depends on how the server is parsing the
lines. I guess sendmail is really looking for the \n and doesn't much
care about the \r.
Therefore this behaviour is correct. I suppose the garbage at the beginning
is failed telnet negociation.
-Phil