Seems that there is something wrong with the terminal types etc.
Evidenced by the following facts.
1. The connection is made so its probably not a filter or basic IP or
routing problem. Also it seems that there is at least one-way
communication to print the daemon banner.
2. My portmasters are set for a telnet port other than 23 and when I
telnet from one portmaster to another on this other port, it works fine
and you get 2-way communication.
So I think that is somehow a problem when communicating from the
Portmaster to a UNIX box and not picking up the vt100 term type or
something similar. I go to a Linux box so the default term type is
"linux" but the portmaster should be passing what it wants.
Wasn't there an issue with this in the past? I seem to remember something
from one of the ComOS release notes. Not surprising since ComOS 3.7.2 was
released back in 1997 for gosh sakes and there hasn't been anything
significant as far as upgrades go for this forgotten product. And stand
by... Look at the debate regarding which platform should see new features
first, the PM4 or the PM3. Hehe
Stephen
On Fri, 30 Apr 1999, Jake Messinger wrote:
>On Fri, 30 Apr 1999, James Courtier-Dutton wrote:
>
>:Works fine here, but I tested to port 25 (SMTP)
>
>I did to. But did you try typing anything? And what unit and com os are you
>using?
>
>Here is a screencap:
>
>ams> ver
>Livingston PortMaster PM-25 ComOS 3.7.2
>System uptime is 11 days 21 hours 14 minutes
>ams> telnet mail.ams.com 25
>Trying 207.235.58.129 ...
>Connected - Escape character is '^]'.
>220 linux.ams.com ESMTP Sendmail 8.9.1/8.8.7; Fri, 30 Apr 1999 08:16:34
>-0500
>
>
>And then NOTHING. TYping is dead.
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>