I added a 2nd administrator level user profile to a Windows 7 Pro work group computer and tried to map a drive to a SAMBA share on a SCO Unix server. This is the same thing I've done before on the other computers in the office, and it's always taken mere seconds to do.
1. Open Windows Explorer
2. Click Tools/Map network drive
3. Select the drive letter
4. Browse to the correct share and click OK
5. Check Connect using different credentials
6. Click Finish
7. Enter User name as domain\name
8. Enter the password and click OK
The result is "The specified network password is not correct."...except it is.
The other user profile on this computer has the same drive mapping and works perfectly.
A terminal emulation program used on both profiles connects perfectly to the server using the same credentials.
I created a 3rd user profile in case the 2nd was corrupt, and had the same failure.
While Googling I've seen the procedure below, but I'm reluctant to make changes because the current settings work for the other profile:
1. Run: gpedit.msc
2. Console Root -> Local Computer Policy -> Computer Configuration -> Windows Settings -> -> Security Settings -> Local Policies ->Security Options
3. When you're there change the following policies
Microsoft network client: Send unencrypted password to third-party SMB server: Switch it to "Enabled".
Network security: LAN Manager authentication level: Select the option: Send LM & NTLM - use NTLMv2 session security if negotiated.
I've also seen some procedures having to do with settings changes on the Unix box.
The Unix server was install YEARS ago by another consultant, and I know very little about Unix. I have root access to it and have had to make changes to it over the years...directed by someone who knows they're doing. I say all this because if the solution requires changes to server, the solution should come with detailed instruction on how to get where I should be going!