Network Drive Map problems

[briansdell]

I am currently running a win2000 network with two DC and two member servers. All our workstations are WinXP Pro recently after the last round of micorsoft updates two of my Winxp workstations started having connection problems with drives mapped to one of the DC's. All other drive maps seem to work fine and non of the other network users are having the problem. I have checked the network servers are replicating and no errors in the logs and sense everyone else is fine I eliminated the network as the issue early on.
Next I removed all the recent updates from the workstations that were acting up and the problem persisted. The script runs and places the the drive maps on the computer however when you click on the drive it tells you that your not connected or have no rights. Reboot serveral times and they start working but after several hours suddently stop again.
I placed a pause in the script so I could see what happens when the drives get mapped during the logon process and noticed that when mapping the drives to that DC the script stops and ask you to enter a user name and password if the user enters the information the drive map is completed normally and works for a few hours and drops again.
Both these users can go to any other computer on the network and logon with no problem this tells me that thier accounts are working properly and granting the proper rights.
Lastly I took one of the computers and formated the computer reinstalled XP and that computer has worked fine ever sense.

So my question is in XP could I have some corrupted logon information cached some place that is creating this problem? Or has anyone seen anything like this in the past?

Thanks

Brian

 

[bcastner]

Troubleshooter:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/key_tshoot.mspx

To add to these notes, I have seen instances where the Cryptographic Service and/or the Protected Storage Service would not start that would generate similar issues.

Usually this is because they were updated and failed to re-register the DLLs required.