Hello Howard: On Fri, 12 Apr 02 11:34:50, [EMAIL PROTECTED] (howard schwartz) wrote:
>> 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. I figured out how to find out the IP number of the machine. I simply go to a web site which offers a trace-route service which tells me which IP I am connecting from. > 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 Yes, I do know about that, but I don't think it is possible to have both a packet driver and a 3com DSL connection on the same machine. These machines don't have modems, they have hard-wired DSL connections hooked up to a network hub. > Perhaps lsppp does something similar? Yes it does. > 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. Even if you could boot from a DOS floppy you probably wouldn't have the DSL connection present because the DSL connection is probably set up to communicate with some Windows program which is loaded from the network. The network loads wincrap. They probably have these machines set up so that you can't boot from a DOS floppy. Of course I didn't ask if it were OK to try it. I wouldn't want them to have any suspicions that I might be up to no good. You know how system administrators feel about curious people who try to conduct interesting experiments on the machines they have set up. In a later experiment I entered the machine's IP number in CONFIG.TEL. That seemed to help because this time it didn't try to go through an endless loop of failures at trying to do BOOTPs. I still couldn't get the darn thing to work because I would get the error "host name not in configuration file." I tried to fix that by inventing a host name to use for the configuration file. This is perfectly OK to do for a dial-up connection with your home computer, but that didn't solve the problem in this case. Regards, Sam -- This mail was written by user of The Arachne Browser - http://arachne.cz/
