Cannot resolve host's hardware address -Error

[Eli Sasson]

Hello

I'm debugging a DOS program using OpenWatcom and Watt32s (a derivative
of WATTCP).

There are two computers:
A. DOS computer - Target
B. XP Computer

I write, compile and link on the XP machine (B). Then, download and
debug on the remote PC (A).
The application is a network application. When it comes to the
_ping() function, I get - "Cannot resolve host's hardware address".

Looking at the logs, it show that "TcpServ.exe" blocks the reply from
going to the packet driver.

My here is my code.
void main(void)
{

longword lHost, lResult = -1;
printf("Start ping...\n");
dbug_init();
sock_init();

lHost = resolve("192.168.111.70");

printf("lHost = %x\n",lHost);
lResult = _ping(lHost,0,"",0);
if(lResult > 0x00)
printf("Success\n");
else
printf("Fail\n");

}

Thanks

Eli

[Gisle Vanem]

"Eli Sasson" <El...@sureerasure.com> wrote:

> I'm debugging a DOS program using OpenWatcom and Watt32s (a derivative
> of WATTCP).
>
> There are two computers:
> A. DOS computer - Target
> B. XP Computer
>
> I write, compile and link on the XP machine (B). Then, download and
> debug on the remote PC (A).
> The application is a network application. When it comes to the
> _ping() function, I get - "Cannot resolve host's hardware address".
>
> Looking at the logs, it show that "TcpServ.exe" blocks the reply from
> going to the packet driver.

Hi Eli. Like I said in private email to you, the fault is with tcpserv.exe
Look in the archive of this very newsgroup to confirm. Back in 2005,
Bernt Muller wrote:

---------------------------------------------

Path: www-1.scitechsoft.com!not-for-mail
From: muel...@gmx.net (Bernd Mueller)
Newsgroups: openwatcom.users.c_cpp
Subject: Re: tcp/ip remote debugging a DOS 16-Bit real mode target
Date: Mon, 06 Mar 2006 08:54:17 GMT
Organization: SciTech Software, Inc.
Lines: 32
Message-ID: <440bf28f...@news.openwatcom.org>
References: <43f9a0cb...@news.openwatcom.org> <dtfm7q$rib$1...@www-1.scitechsoft.com> <43fc29b...@news.openwatcom.org>
<dtj33i$1o6$1...@www-1.scitechsoft.com> <43fd86a0...@news.openwatcom.org> <dtng9m$eq5$1...@www-1.scitechsoft.com>
<4402b7c3...@news.openwatcom.org> <dugpm3$4jq$1...@www-1.scitechsoft.com>
NNTP-Posting-Host: p54bfe7d4.dip.t-dialin.net
X-Trace: www-1.scitechsoft.com 1141635158 5648 84.191.231.212 (6 Mar 2006 08:52:38 GMT)
X-Complaints-To: ne...@www-1.scitechsoft.com
NNTP-Posting-Date: Mon, 6 Mar 2006 08:52:38 +0000 (UTC)
X-Newsreader: Forte Free Agent 1.21/32.243
Xref: www-1.scitechsoft.com openwatcom.users.c_cpp:21782

On Mon, 6 Mar 2006 18:52:00 +1100, "Matt D" <mde...@ndirect.co.uk>
wrote:

>I have had big problems getting the TCP debug server to run on DOS
>applications. Even simple loops showing the time, the connection to the
>server is lost after approx. 20 seconds. I know there were other users
>having the same problem some time ago on an older thread.
>
>Could you tell me what hardware you are using, also maybe you could send me
>the wattcp.cfg and tcpserv.exe file so I know I'm up to date.

Michal provided the latest tcpserv.exe here:
http://www.openwatcom.org/ftp/devel/dtcpsrv.zip

This is the contents of my wattcp.cfg file:
my_ip=192.168.0.3
netmask=255.255.255.0
gateway=192.168.0.1
nameserver=192.168.0.1
sockdelay=9999
inactive=0
datatimeout=9999

I am running an 386EX embedded SBC, self designed ;-) with an CS8900A
Ethernet controller and a CF Card as removable hard disk. The BIOS is
written from scratch. I am running FreeDos with a modified Crynwr
packet driver. The SBC is attached to a router, but direct connection
via a crossover cable is working too.

At the moment, I am struggeling with the new linker order directive...

Regards, Bernd.

---------------------------------------------

Maybe he's still here to help you? Or try this
http://www.openwatcom.org/ftp/devel/dtcpsrv.zip

--gv