> 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.
At least Tony Lopez's dos packet driver, eppd, puts the IP number of
your machine in a file called something like ip-up.bat, as one of 4
variables:
set myip=209.3.225.199
set remip=209.3.225.5
set netmask=255.255.255.0
set peermru=1500
Perhaps lsppp does something similar? I assume that, with dsl doing the
connection, and a tcp-ip connection already being present, you can load
a dos packet driver like one of these, assuming you boot from a dos
floppy. If so, the packet drivers will give you the IP address. I believe
windows includes the program, ipconfig that will do the same.
----------------------------------------
Howard Schwartz
----------------------------------------
howardbschwartz "at" california.com
