Win7 assumes a Domain instead of workgroup
Attempting to connect from Win7 to Win XP, same accounts, passwords, shares and workgroup works for XP accessing Win 7 desktop but not in reverse. instead, Win7 asks for a network login on a pop-up which assumes the computer is on a Domain. It isn't, and no guessed password works! I've tried resetting everything in Win7's Advanced Sharing Settings, to no avail. Remote desktop works, and gives a backhanded way to do file transfers, but this is not a permanent solution. Where do I look next?
October 21st, 2011 1:06am

Hi, Did you try to connect "computer name\user name and password" of Win 7?
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2011 1:48am

The "Domain" pop-up assumes the Win7 computer name correctly, and username/password combinations are identical on both machines. The Win7 machine runs Ultimate, the other is XP Pro. Strangely, Win7 accesses the media center files on the XP with no problem, always has. I had temporary success by adjusting Local Security Policy's Security Options, changing LANManager Authentication level to "Send LM and NTLM resposes" but on reboot thie system reverted to its previous bad behavior. So, I think there must be some other settings for these controls that would get it to communicate.
October 21st, 2011 12:30pm

Hi, You could try to modify the following Registry key: Please backup your registry first. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\LMCompatibilityLevel Set the value as 1. Alex ZhaoPlease 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.
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2011 5:58am

Hi, You could try to modify the following Registry key: Please backup your registry first. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\LMCompatibilityLevel Set the value as 1. Alex ZhaoPlease 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.
October 25th, 2011 12:53pm

Thanks for the suggestion; any idea why/how it was set 0? Don't want it or something similar to happen again...
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2011 2:51pm

Hi, The value 0 represents Send LM and NTLM response; never use NTLM 2 session security. Clients will use LM and NTLM authentication, and never use NTLM 2 session security; domain controllers accept LM, NTLM, and NTLM 2 authentication. When we set it as 1, clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication. Alex ZhaoPlease 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.
November 2nd, 2011 4:12am

Hi, The value 0 represents Send LM and NTLM response; never use NTLM 2 session security. Clients will use LM and NTLM authentication, and never use NTLM 2 session security; domain controllers accept LM, NTLM, and NTLM 2 authentication. When we set it as 1, clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication. Alex ZhaoPlease 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.
Free Windows Admin Tool Kit Click here and download it now
November 2nd, 2011 11:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics