Here's the scenario.
The clients are running win XP, the DFS target runs on win2k3 servers and the DFS root servers are running on a combination of win2k and win2k8 servers. The drives are mapped automatically with a group policy login scripts that maps drives based on the user's group membership.
Now the problem is. When a user tries to click on the mapped drive there is an error connecting to the location. However if you type in the full path, in say, start -> Run, it connects without a problem. All of this started when one of the dfs targets went down with a dead power supply.
I am think the problem is caused by by a cached target/link state, in that, because the target was unavailable at one point, it saved the state of target and the computers still think the target is unavailable. As I had mentioned, if you type in the full path even though the target is "unavailable" it connects to the right link and the mapped drive becomes available.
So does anyone know how I can reset this cache, or any other way I can fix this problem? I tried using Sonar, but it doesn't really give me any helpful diagnostics.
Any pointers are appreciated.