We have a windows 7 HP machine that has/had a mapped drive to a Windows 2003 server. We had a power outtage the other night. Today the Win 7 box will not connect to the 2003 server. We can ping. We can log in via Remote Desktop. We can access it via browser ("it" being the server from the Win 7 machine). I have validated the username and password and they work. All other computers on the network connect to the server just fine through their mapped drives. The issue is when I go to connect via the mapped drive from this Win 7 machine (or remap the drive) it asks for username and password. The user name and password I enter are promptly rejected (although they work from other computers). We've tried creating a new user and password on server and using that, but we still get the (wrong username or password error). It seems to be an issue with Windows 7 itself. FYI, the windows 7 machine acts as a conduit to the server for our bar code readers from operations and cannot be easily swapped out.

Hi, According to your description, I suggest to perform these tests to troubleshoot the issue: 1 Remove the mapped drive and re-map it to see the result. 2 Use \\IPaddress\share or \\servername\share to access share folder. 3 Temporally disable firewall on Windows 7. 4 Check Credential Manager on Windows 7. Remove any incorrect credential and add a new credential of share folder. Hope that helps. Regards, Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Leo, Thanks for the time you took answering. I had spent a couple of hours going through forums where I found others with the exact same problem. They could not map a drive to a server from their Win 7 box. For some, as in my case, it had been mapped before, but then one day would not connect any more and they would get the "incorrect password" error code. I went back to the site with several things i was going to try, but found out the owner had it fixed. In this case (unlike in all the forums I read) it turned out to be that the date/time of the server had been set back to 2000 after the power outtage the night before. When he set the date/time correctly the Win 7 box connect right up. Strange how the XP boxes mapped right up even with the date/time problem. I leave this narration here just in case it helps someone else. I know in most of the cases I read in other forums the date/time was not the issue. But I'm glad this fellow is back in business even if I wasn't the hero.