Normally, my DHCP server gives me very few problems…
Symptoms:
User tries to log in in the morning and it takes 5-7 minutes to get an IP address.
The DHCP server has issued them one, but they either don’t take it, or take it and drop it as soon as they boot to desktop completely… and wind up with the APIPA address.
Ok, so basically the Client says “Gimme an address!” and the DHCP is sending NACK’s “I gave you one, hoser! Wait till the lease is up to get another!”.
I have to go and manually delete the IP address before the DHCP server will issue a new one and normally the client picks it up right away after that. Rarely, I have to do the whole ipconfig /release-renew thing on the client.
The client machines are all newer laptops with at least 2 NIC’s, onboard gigabit and wireless-G. Some have additional NIC’s for other purposes.
Most are Dell, but not all.
Due to it hosing the Users when they travel, I can’t put “wait for network at startup” requirements in Group Policy. Note: Doing this for my DESKTOPS cured the exact same problem!!!
The server is Win2k3 and all clients are WinXP.
I seem to remember a MS solution to this, but I’ve searched and I’ve Googled and I just am at the end of the rope.
Thanks!
