DHCP request times out but an IP is successfully obtained

I have a small network with 6 public IP addresses. The debian box runs
a DHCP server. I've tried with the standard dhcp server and am now
using the dhcp3-server set.

When my XP SP1a machine (PC4800 Deluxe with onboard 3COM Gigabit
Ethernet) attempts to get an IP via DHCP, windows actually times out.
*but* it *does* get an IP.

For instance ...

<quote>
C:\>ipconfig /release

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :

C:\>ipconfig /renew

*waits 1 or 2 minutes*

Windows IP Configuration

An error occurred while renewing interface Local Area Connection :
unable to contact your DHCP server. Request has timed out.

C:\>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : nooblet.org
Autoconfiguration IP Address. . . : 81.168.82.220
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . : 81.168.82.217

C:\>
</quote>

This has the added effect that any startup programs are unable to
access the internet, as the "ipconfig /renew" command takes up to
2mins to time-out, I dont get an IP on boot-up for 2 mins. Anti-virus
complains it cant update its definitions and MSN Messenger gives up
connecting. The same problem is on another XP machine (also SP1a,
PC-Chips motherboard with onboard Realtek 100mbps NIC), but that
refuses to startup until it has an IP, therefore sits at a blank
desktop for 1 or 2 mins before loading (which to be honest is actually
preffered as that means it has no startup issues with internet
connection).

A workaround would be to issue a static IP to each PC, but I would
really like to get this working as it should.

More info ...

Here is logs from /var/log/syslog concerning an ipconfig /renew from
this PC,

# nooblet is the server name, 81.168.82.220 is this PC

# I first restarted the dhcp3-server process
May 21 14:24:13 nooblet dhcpd: Wrote 0 deleted host decls to leases
file.
May 21 14:24:13 nooblet dhcpd: Wrote 0 new dynamic host decls to
leases file.
May 21 14:24:13 nooblet dhcpd: Wrote 0 leases to leases file.
# ipconfig /release
May 21 14:24:53 nooblet dhcpd: DHCPRELEASE of 81.168.82.220 from
00:0c:6e:70:29:33 via br0 (not found)
# ipconfing /renew (start)
May 21 14:25:00 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via
br0
May 21 14:25:00 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
May 21 14:25:05 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via
br0
May 21 14:25:05 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
May 21 14:25:13 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via
br0
May 21 14:25:13 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
May 21 14:25:30 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via
br0
May 21 14:25:30 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
May 21 14:26:06 nooblet dhcpd: DHCPDISCOVER from 00:0c:6e:70:29:33 via
br0
May 21 14:26:06 nooblet dhcpd: DHCPOFFER on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
May 21 14:26:06 nooblet dhcpd: DHCPREQUEST for 81.168.82.220 (0.0.0.0)
from 00:0c:6e:70:29:33 via br0
May 21 14:26:06 nooblet dhcpd: DHCPACK on 81.168.82.220 to
00:0c:6e:70:29:33 via br0
# ipconfig /renew (end, finally get an ACK)

And my DHCP config ...

(root@nooblet(/var/lib/dhcp)>cat /etc/dhcp3/dhcpd.conf
#
# default options
#

server-identifier nooblet;
default-lease-time 86400;
max-lease-time 86400;
option domain-name "nooblet.org";
option domain-name-servers 81.168.82.217;
option host-name "nooblet";
option routers 81.168.82.217;
option subnet-mask 255.255.255.248;
option time-offset 0;
option time-servers 81.168.82.219;
option netbios-name-servers 81.168.82.219;

#
# dynamically leased ip, will be receiving a further 12 IPs soon but
for now there is only one free
#
subnet 81.168.82.216 netmask 255.255.255.248{
range 81.168.82.222;
}

#
# static ip based on mac address
#
host stalks {
hardware ethernet 00:0C:6E:70:29:33;
fixed-address 81.168.82.220;
}
host bambi {
hardware ethernet 00:0D:87:AA:B1:8B;
fixed-address 81.168.82.221;
}


I understand this may be a windows or a linux issue, and if you feel I
have posted in the wrong newsgroup then I apologise, I would be
grateful if you could point me to the correct group.

--
May the ping be with you ....

Registered Linux user number: 355729