Jan 212009

When trying to access a network share on a Mac OS X network share supporting Windows Sharing Service from a Windows 7 PC you may be thrown with errors like

Network path not found error (0×80070035)

or go in cycles prompting for logon passwords.

Windows 7 by default will only use NTLMv2 for authentication, which is not supported by Mac OS X's Windows Sharing service and can also be caused by the new “Minimum Session Security for NTVLM SSP based Clients” security feature found in Widows 7 and Windows Server 2008.

To workaround this problem,

1. Click Start – search secpol.msc, right-click and choose “Run as Administrator
2. Click “Local Policies” and then “Security Options” in the leftpane.

3. In the rightpane, locate “Network Security: LAN Manager Authentication Level” in the list. Double-click and change the setting from “Send NTMLv2 response only” to “Send LM & NTLM – use NTLMv2 session if negotiated” and click Apply and OK

5. Now, double-click on Network Security: Minimum session security for NTLM SSP Based (including secure RPC) Clients and uncheck “Require 128 bit encryption” and click OK.


This should resolve the problem.


Incoming search terms:

  16 Responses to “Unable to access Network share on MacOS X from Windows 7”

  1. Thanks for the fix! Worked like a champ with Mac OS X 10.5.6. :-)

  2. did this and was able to mount the share or map it afterwards. however, after about 5 minutes of having connected to the share, windows 7 crashes and restarts. it happened to me 6 times. all i had to do was have a mapped network drive to the mac os x share and that would trigger the crash in about 5 minutes. disconnecting the share resolves the problem, no more crashes. i tried other settings (ntlm responses) but still no dice.

  3. You’re the man! Trying to connect my Windows 7 laptop to a Buffalo LinkStation – this worked! Thank you, Thank you, Thank you!!!!

  4. i had this working in windows 7 build 7000 but in 7057, it doesn’t work.. is there any update to this?

    also, not sure if it’s related- but i can see my windows computer from my mac, but when i connect to it, no files show up.. i see the shared folders and ‘connect’ to them, but no files appear..

    help please!


  5. yea i’m having the same problem, thi no longer work on buil 7057…

    please help,

    thank you

  6. i went through lots of steps and finally figured it out.

    Advance system settings – Computer Name – Network ID – (click on) This is a Home Computer …. Restart.

  7. None of this is working. When I type in secpol.msc the computer does not find it. Or when I go to Computer Name I can not click on Network ID. I was able to connect this Vista Home Premium to one Mac but I can not connect it to my Mac server. Can some one please help?

  8. i have almost the same problem with my wife’s vaio with a win 7 starte. i find the secpol.msc, but when i run it, it says it tells me something i can’t translate from russian. somethen the console can’t create…

  9. i have the same problem as the last to guys.

    error in secpol.msc

    and i can not click on the Network ID tab…

    what cant PC and Mac just get along already :P

    any thoughts how to fix this?

  10. Hi all,

    I’m having the same restarting issue. I have a Windows 7 PC on a network with a OS X 10.5 Mac and when the Mac opens the shared folder from the PC, I can see the files just fine, but after a few minutes, the PC gives me a blue screen and restarts.

    I’ve tried the above changes to both the secpol.msc (no problems getting access or making the changes) and to the Network ID (set it to Home Computer and restarted) but the problem is still there.

    Has anyone tried to analyze the crashdump report after one of these BSOD restarts?

    Also, does it make any difference that the Mac is connected to the PC by ethernet crossover cable to share the PC’s wireless internet access?

  11. I’m having an issue with step one seeign as when I search for secpol.msc, it doesn’t exist. I have tried searching for all the keywords I can think of but can’t find what I need.

    I can actually see my Mac on the PC and access all of my Mac files, but when I go to the network screen on the Mac, it doesn’t show anything at all.

  12. HI All

    Also have Windows 7 home premium and trying connect to Windows 2000 shares, with no success – get repeated login request.

    After searching myself blue in the face, I found something that works:

    The solution: Registry editing for LAN manager authentication level (in Home edition this can be configured through registry)

    How to do it:
    1 . Open registry editor ( Start search – regedit)
    2 . Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    3. Create a new DWORD value with the following properties: NAME: LmCompatibilityLevel
    VALUE: 1
    4. Restart your PC and try the connection again…

    Hope this works for you too!

  13. Trying to share Win7 Home Premium and Mac OSX 10.5.8

    I cannot use the secpol option because Win7 Home doesn’t allow that.

    I can mount the Win share drive onto my mac, but have no rights to add data to it. I can extract data on my win share to my mac though.

    Win7 does not see my mac nor my Ubuntu machine – but all sharing options are turned on.

    I have been searching everywhere for the golden ticket for this. I’m on the cusp of getting these shares to work properly but still hitting a few glitches

    anyone have any ideas?

  14. this is the solution to your problem I think, it is a Windows problem.

    if you have a MAC – PC network and you MAC soddenly refuses to mount PC shares this will fix it:
    Open regedit.exe and :

    Set the following registry key to ’1?:
    HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory

    and set the following registry key to ’3?:


    the restart the “server” service.

  15. Man, that worked like a charm. I worked on that for over 3 hours. Tried lots of other sites for a solution. Yours was the only one that worked.
    I am SO grateful I found this, and it worked!!

  16. Thanks. This works with Windows 8 & Mac OS X 10.8.2.

Sorry, the comment form is closed at this time.