Yutaka,

Thanks for the information, I have researched the references you supplied
and with some experimentation I have found a solution.

If the local LAN (192,168,0,8) card is initialised first and  the ISP
broadband LAN second (order given by ipconfig) the system works correctly.
If the initialisation occurs the other way around I get the symptoms I first
described.

Although I have not extensivly exprimented it appears that WIN XP is
initialising the LAN cards in MAC address order and
therfore you get a 50/50 chance of getting it right first time. If I get
time I will examine this futher but for now I have a working
system and I am grateful for that.

thanks again

Stuart

----- Original Message -----
From: "Yutaka Sato" <pficabdyi-jk6bmqu4eqnw.ml@delegate.org>
To: <pficabdyi-jk6bmqu4eqnw.ml@delegate.org>
Cc: <paegabdyi-jk6bmqu4eqnw.ml@delegate.org>
Sent: Saturday, November 19, 2005 12:54 AM
Subject: Re: [DeleGate-En:3079] DNS Server on WINXP]


> In message <_A3075@delegate-en.ML_> on 11/17/05(06:55:31)
> you "SMF" <paegabdyi-jk6bmqu4eqnw.ml@delegate.org> wrote:
>  | > I think a detailed log of DeleGate for debugging the resolver will be
>  | > helpful.  You will get it without "-vt" and adding the following
options.
>  | >
>  | >  -vd RES_DEBUG=-1
> ...
>  |Thanks for the reply I have changed the logging as you suggested, the
>  |results are attached.
> ...
>  |11/16 21:23:32.91 [4076] 0+0: PORT= 53/10 (0,53)
> ...
>  |11/16 21:23:35.07 [4076] 0+1: ## RecvFrom(10) = -1, ECONNRESET
>  |11/16 21:23:35.07 [4076] 0+2: ## RecvFrom(10) = -1, ECONNRESET
>  |11/16 21:23:35.07 [4076] 0+3: ## RecvFrom(10) = -1, ECONNRESET
>
> This message means that recvfrom() failed to receive a DNS/UDP packet
> in some reason.  On Windows, it occurrs when recvfrom() returnes
> WSAECONNRESET.  The documenation of Win32 says:
>
>
<URL:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsoc
k/winsock/recvfrom_2.asp>
> >WSAECONNRESET The virtual circuit was reset by the remote side
> > executing a hard or abortive close. The application should close
> > the socket; it is no longer usable. On a UDP-datagram socket
> > this error indicates a previous send operation resulted in
> > an ICMP Port Unreachable message.
>
> Retrieving in Google, there seems to be a recent bug-fix for Win2K
> as <URL:http://support.microsoft.com/kb/q263823/>
> There might be similar problem in WinXP, but I don't see the problem
> on my WinXP, whitch is labeled as "WinXP Home Edition, Version 2002,
> Service Pack 2."
>
> Cheers,
> Yutaka
> --
>   D G   Yutaka Sato <pfqcabdyi-jk6bmqu4eqnw.ml@delegate.org> http://delegate.org/y.sato/
>  ( - )  National Institute of Advanced Industrial Science and Technology
> _<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller
>