Hello Fellow Arachnids:

Our local library has internet work-stations on a DSL connection
to the same ISP I use, "shentel.net".

The work stations don't have a Telnet client installed.  At the
library of course they don't allow patrons to install their own
software on the library work-stations.  One thing that is allowed
is to run programs on your own floppy disk.  Yesterday at the
library I ran two different Telnet clients from a floppy disk.  One
was a Windows program, YAWTEL32.  This one worked just fine on port
23.  I got into my unix shell account and also I got into
"linuxfreemail.com" and I ran Pine in Telnet session.  One thing I
was not able to do was to get into my pop3 server at "shentel.net"
on port 110.  I was able to contact the server and it responded
with the "+OK" prompt.  I was unable to input anything on the
screen.  I could not enter my "user" and "pass".  Does anybody
have any theory as to why I couldn't even get into my own pop3
account on port 110?  Does the DSL type of connection pose a
problem in this regard?

The other Telnet client I tried was TN3270.EXE, the CUTCP DOS Telnet
client that you can get as an APM for Arachne.  In my CONFIG.TEL
I entered "3com" in place of "packet" for "hardware".  When I tried
to use this program it attempted to do BOOTPs but it was
unsuccessful.  This program can successfully do BOOTP on a DOS
machine having a modem connection to "shentel.net".  The library
machine has a DSL connection.  Maybe the DOS Telnet client would
work if I were to indicate the actual IP number of the machine in my
CONFIG.TEL.  How can I find out the IP number of the machine?  I
know how to find that out on a DOS machine, but not on a Windows
machine.  Normally I don't do Windows.  Normally I do only what the
normal people do.

Please help me.

Sam Heywood
-- This mail was written by user of The Arachne Browser - http://arachne.cz/

Reply via email to