I've already searched EE for hours but can't quite find a solution to my exact problem, so thought I better post my dilemma.
I have a Windows 2000 DC (don't ask) with AD, DNS, DHCP, etc and 120 XP clients. Things have been running happily without issue until recently when a small number of random XP clients would lose their connection with the domain. I think I've narrowed it down to (some) PC's that have been shutdown for a week or more (staff on holidays, or not in use).
Once powered on, the affected PC takes 20+ mins to login, after which the user discovers that they can't access any AD resources (login script, email, etc). Upon further inspection, the affected PC can ping other network devices/servers by IP address, but not by name. BUT, the weird thing is that it can't ping the DC by IP (and vice versa)! Other servers can ping the affected PC's by both name and IP... just not the DC.
The affected clients can still renew their IP via the DHCP. The AD server has been set as the sole DNS server on all client NICs (and the server NIC itself). DHCP leasing is set to 4 days. Nslookup fails (timeout) on the affected PC's. The PC's still have an entry in DNS.
To get around it in the interim, I re-image a spare PC for them (which logs in fine afterwards) but I can't keep that up for much longer. I'm sure its DNS-related (or maybe DHCP's interaction with DNS?), but I'm not sure which steps to take to resolve it.
I'd appreciate any clues/feedback.