Question : Really strange AD DNS problem

I'm having the strangest problem with my internal DNS. I'ts a XP/2003 AD environment.

When I arrived a few weeks ago, there was a folder redirection policy in place that I changed to redirect to a more appropriate server location. The new location works, however the old location never stops syncing at user logout. I can't browse to this location as it no longer exists.

Another thing that has begun to happen recently is that some workstations can't access the domain controller. They can log on (using cached credentials, I imagine) however GPOs don't run and if I try to browse by name to the DC (which is the old redirect location) the only thing that appears is the share for the old redirect location. The one that doesn't exist! Clicking into the share brings up the error that the location is unavailable, obviously. I can browse by IP to the DC, no problems there.

I should mention that the second problem started happening after I added a DC at a remote site, however there were no issues with that. I've run DCDIAG tests extensively at both locations and they both come up clean. NSLOOKUP is resolving everything fine. I don't understand what is happening.

What resolved this issue once was deleting a users profile, rebooting, running

1:	ipconfig /flushdns & net stop netlogon & net start netlogon & ipconfig /registerdns

rebooting and adding the users profile. However this only worked once. It fails when I repeat these steps at any other workstation.

This isn't happening on all the workstations, btw, but it is about half (of 50 or so).

At my wits end... Is it possible that some AD information is corrupt?

Answer : Really strange AD DNS problem

Yes I have tried to delete just the offline files. However it doesn't work until I remove the actual profile and recreate it. It's weird and I wish I knew why this happened.

Thank you for the point in the right direction, I wouldn't have thought to disable offline files so quickly.