Dfs drive mapping errors.

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.
Thanks,
Daniel
FUS IT ServicesAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jebCommented:
Are your scripts deleteing then re-mapping the drives or just mapping the drives?
0
FUS IT ServicesAuthor Commented:
Just mapping. Now that you mention it, windows is sometimes iffy when it comes to persistent drive mappings. You reckon I should delete and remap them every time at login? what about a non persistent drive mapping it should have the same effect as deleting before re-mapping, right?
0
jebCommented:
we setup  our scripts to delete then map to avoid the issue you are having.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

jebCommented:
Deleting first also removes the problem of a user doing a mapping and using a drive letter that is in your scripts.
0
PRIVATERENCommented:
See below link is of any help

http://support.microsoft.com/kb/893231
0
FUS IT ServicesAuthor Commented:
@jeb I think your answer might be the right solution, but could you give me a couple of days to confirm it before I accept your solution?

thanks
0
jebCommented:
Fine with me. Always best to test.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.