Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

dtfreak05

macrumors newbie
May 27, 2016
1
0
Hi,

The registry variable:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\control\LSA\LMCompatibilityLevel

is used to set the minimum challenge/response algorithm.

The DWORD value can be: 0, 1, 2, 3, 4, 5.

Please know that the Mountain Lion OSX, Mavericks OSX and Yosemite OSX domian controllers does not accept LM, NTLM, LMv2, and NTLMv2 responses so if the Win 7 and Win 8.1 sends the LM, NTLM, LMv2, and NTLMv2 responses to MAC with these OSes it does not get responses back so the connection is unsuccessfull from the Win 7 or Win 8.1 side so the problem is in the Win 7 or Win 8.1 operating system which does not allow the connection to be made!

If you need this DWORD line in the registry you can stil connect from the MAC environment to the Win 7
or Win 8.1 shares!
But you can not connect from Win 7 or Win 8.1 environment to MAC OSX shares!

Best regards,

Gorazd.

First post here, sorry to dig up an old thread but I just wanted to say this absolutely worked for me with a Win 7 machine and an OS X El Capitan Mac...I've tried everything I could find to try to log into my Mac from the Windows machine and this is the only thing that worked. I had previously tried enabling, disabling, and enabling again all the previously discussed settings in OS X, and Windows, nothing worked but this. What an obscure solution, but it worked immediately. Thanks Gorazd!
 

Johnfli

macrumors newbie
Aug 18, 2016
1
0
That is all fine and dandy..... I am having the same issue, with a slight twist.
I have one server (Snow Leopard) and it has a couple of shares on it. Shared with AFS and SMB. Most Windows machines (all windows 7 ent) can access them just fine (using \\computer name, or \\ip address) yet, I have some machines that cannot(again, Windows 7 ent).

As big of a pain as that is, it gets better......

if they open windows explorer and try to goto \\mac name they get an error saying to check the spelling of the name. [they can ping it by name just fine] but if they try \\ip address they get asked to enter a username and password. I have tried a domain name that has permissions, I even tried the local Apple admin account name and nothing, it still says logon failure.
I check the smb log and it reports "FAILED with error NT_STATUS_WRONG_PASSWORD" yet, if I contrinue to try to log in time after time after time....the domain controller does not lock my account, which shows that crAPPLE isn't trying to autheticate.

But seeing how most machines are able to access, that would point to the MAC being setup right and somethign wrong with windows........ but the registry settings (all the various items listed in this thread) on the non working machines and the working machines are the same.

BTW:
The Windows machine in the above issue, is able to connect to other Mac servers just fine. All are on the same domain.

So.....any other ideas??
 
Last edited:

manman

macrumors regular
Aug 18, 2008
125
1
Just change settings on OSX

Just an update for future people that find this thread: You do NOT need to go changing registry keys in Windows to get this to work.

Do what SStamatis has mentioned, which is simply to change file sharing settings on OSX (Yosemite in my case) to use SMB _and_ individually select which OSX accounts should be accessible by the windows machine.

Here are SStamatis instructions again (edited for clarity):

"on Your mac computer, Go to System Preferences, enable File Sharing, click on the Options button, enable "share files and folders using SMB" and then enable (via the checkbox) each OSX account in the "Windows file sharing" section"

This did not work for me (or to be more specific, these are the standard steps everywhere that I had already done but didn't work). Nothing worked for me until I tried Gorazd's solution, and it worked immediately like others said. I can't vouch for how secure the change is though, the explanation he gave for what it does makes sense in the context of everything I read trying to figure this problem out, but I don't know the big picture/system-wide implications of making this change.
 

SamWI

macrumors newbie
Jan 2, 2018
1
0
Hi,

run regedit.exe as administrator on the Win 7 machine.

Delete this DWORD line in the Win 7 registry and you shall be fine:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel

You do not need to restart the Win 7 system in order that you can now successfully connect for example to the: \\MACPRO\HARDDRIVESHARE from Win 7 machine.

You only need to fill the administrator name and password login for the Mac OSX computer and you shall now successfully map the Mac network drive on the Win 7 machine.

Best regards,

Gorazd.


After spending a LOT of time on this issue, your solution was the only one that worked, in my case.

Deleting the DWORD immediately solved the problem where Windows 7 would see the Mac Mini but would refuse to log in no matter what value was in that DWORD (possible values 1 - 5.)

I did not need to fill in the password when login in to the Mac from the Windos 7 share login as I had created a guest account on the Mac without a password.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.