I have an interesting problem with a small 2 DC domain:
My customer had a 2000 server DC and I installed a new Windows 2003 DC following MS white papers, I did the 2000 to 2003 ADPrep and transferred the FSMO roles to the new 2003 DC.
The new DC is used mostly for file sharing, but it is configured with DHCP, DNS and WINS.
Two times the old 2000 server suffered a hardware failure and would not boot, after this happened, only about half of the users could open their shared folder on the server, if I deleted their mapped drive and tried to re-map, it would ask for credentials and when supplied, it would give an error that the ÃƒÂ¢Ã‚Â€Ã‚Âœlogin credentialsÃƒÂ¢Ã‚Â€Ã‚Â have already been tried and have failed.
I found out if I reboot the PC even though they have been rebooted many times before while the mapped drive was attached, then tried to map again it would ask for credentials and accept the login credentials creating the mapped drive.
I noticed that when you do a ÃƒÂ¢Ã‚Â€Ã‚ÂœsetÃƒÂ¢Ã‚Â€Ã‚Â command from the command prompt, the LOGINSERVER was the 2000 server and not the 2003 server. It seems that itÃƒÂ¢Ã‚Â€Ã‚Â™s using the cached credentials to log on, but not getting authentication from the 2003 server if the 2000 server is unavailable. The 2003 server is set in DHCP as the DNS server and WINS server. IÃƒÂ¢Ã‚Â€Ã‚Â™m baffled as to why it will not authenticate users trying to use a share on itself.
Any ideas what I should be looking for here?