From: sturm AT ost1 DOT ping DOT de (Oliver Sturm)
Subject: Re: Help with TCP/IP package
Date: Thu, 08 Jun 95 17:48:08 MEZ
To: djgpp AT sun DOT soe DOT clarkson DOT edu

In <stanbD9qF3p DOT DLp AT netcom DOT com> you (Stan Brown) wrote :

>     I am trying to get the djgpp TCP/IP package to work. So far I have
>obtained a packet driver for my card (a  3COM Etherlink III 3C589B) and
>managed to get the library compiled. Now when I run the ping program that
>came with the package to test it I get the error message 
>"Can't resolve Host Address" >  I am unshure wheteher this refers to 
>the local or the remote address. I think this is probably a configuration
>problem. Here is the config file:
>
>
>print="using sample configuration" # sample comment
>print="contact local network guru for more details"
>my_ip=205.159.77.248
>netmask=255.255.255.0
>gateway=205.159.77.248
>#                    nameserver=129.97.128.24           ; sample comment
>#                    nameserver=129.97.128.196          # alt nameserver
>#                    nameserver=129.97.128.1            # 3rd nameserver

These lines should be the source of your problem, exactly. I don't 
know if wattcp (that's what I think is used with the tcp/ip-library) 
handles some kind of resolv.conf- and/or host-file, but if it doesn't 
or if these files don't contain the correct values to resolve the name
of the host you tried to `ping', you're desperately in need for a 
nameserver. Usually the host you're directly connected to should be 
able to do this. Anyway, if wattcp isn't too bad (and I never heard 
anything like this), it should be able to do a `ping 205.159.77.248', 
as this way there is no hostname that needs to be resolved. 

>gateway=205.159.77.248
>hostname=faspc4
>#                    domainslist="uwaterloo.ca"
>
>     The problem seems to be in the _arp_resolve(0 function. Can anyone
>help me get this working ?

If this is right (I mean the function), there might be another source 
for the error, as arp is usually a protocol for converting ip-adresses
into ethernet-adresses, which are six bytes instead of four for 
tcp/ip. In this case I can't help you any further, as I really don't 
know anything about wattcp.
>
>     BTW the TCPINFO.EXE program mentioned in the doc files doesn;t 
>seem t be in the distribution that I got.
>
Oliver


--

   Oliver Sturm   sturm AT ost1 DOT ping DOT de