This issue has come to light over the last week or so and for the life of me I have no idea what is causing it.

A few windows seven machines (definitely new PCs bought and added to the network) have started failing to get/renew DHCP address on reboot, after logging in locally you see the network icon trying to determine an address and failing. In the dhcp log on the server it looks like the windows 7 PCs in question are continuously requesting and address and successfully being assigned it, maybe 10-20 times per second.

Extract from the log:
Aug 3 14:36:00 magrathea dhcpd: DHCPDISCOVER from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPOFFER on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPREQUEST for 10.0.0.214 (10.0.0.210) from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPACK on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPDISCOVER from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPOFFER on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPREQUEST for 10.0.0.214 (10.0.0.210) from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPACK on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPDISCOVER from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPOFFER on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPREQUEST for 10.0.0.214 (10.0.0.210) from f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0
Aug 3 14:36:00 magrathea dhcpd: DHCPACK on 10.0.0.214 to f4:4d:30:1d:7d:b5 (PC0AUQUG) via eth0

DHCP is running on Suse Linux OES 11 SP2, it was migrated across from Netware about 12 months ago and seemed to be running fine until recently, no changes have been made.

TIA,
Mark.