I have a similar problem in 2 environments, my office/home testbed environment and at a client. I'll start with the home office. Windows 2000 Server (fileserver) with two shared directories -- permissions set for everyone. The shares were mapped drives, but then the system started showing that it could not connect (so it was working). The server appears in the network discovery. Clicking on the server gives the bad password/user message. Logging in as fileserver\username and using the correct password does not work -- same error. RDP to the server with that user/password works. The kicker to this is two fold: 1. it used to work (only changes is updates) and maybe adding MS Security Essentials. 2. It works on my Vista Business system. The client environment is: Server 2008 in a Workgroup, shares are fine with XP systems, adding a new Win7 system has the same 'bad username/password' error. I think I have covered the simple things: All same workgroup, File sharing on servers are Everyone, all rights Works fine with same user on other O/Ss HELP! Thanks.

About 100 views but no suggestions/help; let me be more specific/technical. Server 2008, Win7 and Vista are all smb2. I think Server 2000 SP4 is also smb2... let me know if that's wrong. Are there any logs that I can look at to see (specifically) why the connection/pipe is being rejected? It's not in the application or system logs. I have use the win7 password manager to delete the record for the server "fileserver" on the PC. I enabled the guest account on the server (one suggestion from previous posts), still no change, still getting the same login message. Are there registry parameters that would impact or change the login or security process that I should look into? I don't think it's a firewall issue since: a) it worked before, and b) I can access files on the Vista PC from Win7 and the other way around. Suggestions for how to chase this issue down would be helpful. Thanks.