If you look in your windows event log (assuming 2000/NT) then you'll see =
timeout errors to the server at T1 times.  We've seen this before and =
just kind of deal with it because the transaction is usually successful.

-----Original Message-----
From: Paul Apprich [mailto:paul.apprich@verizon.net]
Sent: Saturday, January 05, 1980 1:55 AM
To: port-i386@netbsd.org
Subject: dhecp messages


    I have a unit running NetBSD 1.5.2 that runs dhcpd. When a Windows
system set for DHCP requests an IP address, the NetBSD box issues the
following on the console screen:

<date & time> <machine> dhcpd: if IN A nnnnn.nnnnn.nnn rrset doesn't
exist add 302400 IN A nnnnn.nnnnn.nnn 192.168.0.xxx: timed out.
<date & time> <machine> dhcpd: if IN A nnnnn.nnnnn.nnn rrset doesn't
exist add 302400 IN A nnnnn.nnnnn.nnn 192.168.0.xxx: timed out.

    The request does succeed and thus WINIPCFG reports addresses. I have
tried tweaking the NETWORK NEIGHBORHOOD settings in Windows, but the
same message still appears. NetBSD boxes running dhclient do not give
these errors.

this is the contents of dhcpd.conf

# sample dhcp.conf file
#
#
#
allow unknown-clients;
ddns-update-style ad-hoc;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.2 192.168.0.253;
default-lease-time 604800;
max-lease-time 604800;
option subnet-mask 255.255.255.0;
option domain-name-servers xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx;
option domain-name "xxxxx.xxx";
option routers 192.168.0.1;
}

Is there a fix for this?

PA