Problem with map drives after AD password change (computer specifi

[PghTech]

Bizarre issue occured when I changed a user's password (win 2003 server
environment). They could no longer access any mapped drives.

Troubleshooting steps:
- days had passed since the user changed their password and logged into
their computer successfully to rule out AD replication issues.

- We were able to change the password from the "windows Security" window
from the actually computer successfully.

- THis only occurs on their daily used PC. Logging onto any other computer
they can access any of their network drives.

- If you reset the password back to the original password everything works
correctly.

It is obvious that it is strictly with this specific computer, but where or
what needs to be done - I haven't been able to locate a reason.

 

[Mark L. Ferguson]

It's likely that the share of the maped drives depended on a matching id/pass
on the the object of the map. There is the two alternatives of explicitly
adding Permissions for the new id/pass on each mapped drive share, or adding
the id/pass account on the target machines.

 

[PghTech]

Thanks Mark.

A few other points that did remember to add:

- I tried disconnecting the drives (one for example) and then reconnecting.
Once attempting to connect it prompted for credentials (though they have
access to the drives and I was able to mapped the drive without prompt on
another computer as them). However, putting in their username and password
wasn't accepted. Even more bizzare was that the network administrator
username/password wasn't accepted either.

What do I need to do to correct this. I want to say I seen something like
this that required changes in the registry but I can't find that any longer.

 

[Mark L. Ferguson]

Nope, I don't get that either. The domain admin should have access to
Permissions anytime. My reaction is 'something is corrupt' in the
permissions of the mapping machines.

 

[PghTech]

Thanks Mark.

Anyone else have any suggestions?

Nope, I don't get that either. The domain admin should have access to
Permissions anytime. My reaction is 'something is corrupt' in the
permissions of the mapping machines.