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

Windows 7 can see but not access OS X share

toronado455

toronado455

macrumors regular
Original poster
Apr 2, 2009
214
15
In OS X, Windows sharing is on and I have "Shared folder" checked on the folders I want to share. OS X can access shared folders on the Windows box, but Windows can't access the OS X shared folders. Windows prompts for a "network password". I don't know what that would be, but I set up user accounts on both machines with the same user names and passwords. I've tried entering these credentials but nothing ever works.
 
Got this (sort of) working...

I believe the problem is that OS X isn't on the same workgroup (or ANY workgroup) as the Windows box.

In OS X, System Preferences > Network > Advanced... > WINS tab:
If I enter the NetBIOS name of the OS X computer and the name of the Windows Workgroup (default "WORKGROUP") click OK, then Apply, this fixes it and Windows can access the shares on OS X and doesn't prompt for a network password.

But it is only a temporary fix. Rebooting OS X clears out the values I entered in the WINS tab, even if I have "clicked the lock to prevent further changes".

I'm not even sure that this is the correct place to designate a Windows Workgroup name on OS X. Anyone know?
 
velocityg4 said:
You likely are just running into an issue with changes MS made in Vista's networking that still exist today. Try the following from Post #8 in the thread below. The bottom of the post was updated for there being no Local Security Policy in the Home version of Windows.

https://forums.macrumors.com/threads/776672/
Click to expand...
OK, yeah, thanks. I think I found your thread when I was searching for answers.

But what I really would like to know now is, on the OS X side, why don't the values I enter into the WINS tab stick?
 
Sorry, but this has nothing to do with Vista or Win 7. This has to do with the fact that Apple dumped SMB due to licensing issues and uses a home baked SMB client that does not work well and is buggy. Like the fact that it does not show mounted SMB shares anymore in the left side of finder. The WINS bug is just one of many. If you have a domain controller, join the macs and the pc to the same domain sometimes helps. Sometimes you need to turn off file sharing and then fix the wins and then turn your file sharing back on. I have contacted Apple many times about this...you should as well.
 
itsamacthing said:
Sorry, but this has nothing to do with Vista or Win 7. This has to do with the fact that Apple dumped SMB due to licensing issues and uses a home baked SMB client that does not work well and is buggy. Like the fact that it does not show mounted SMB shares anymore in the left side of finder. The WINS bug is just one of many. If you have a domain controller, join the macs and the pc to the same domain sometimes helps. Sometimes you need to turn off file sharing and then fix the wins and then turn your file sharing back on. I have contacted Apple many times about this...you should as well.
Click to expand...
Wow. So what does Apple expect us to do? Buy OS X server?
 
toronado455 said:
Wow. So what does Apple expect us to do? Buy OS X server?
Click to expand...

No, OS X server has the same problems. Samba changed to the GPLv3 license and apple did not accept the license, so they made their own SMB implementation.

The easiest way to fix this is to setup an old computer as a WINS server for your local network and the OS X box can pull those wins values from the server on boot.
 
alexrmc92 said:
No, OS X server has the same problems. Samba changed to the GPLv3 license and apple did not accept the license, so they made their own SMB implementation.

The easiest way to fix this is to setup an old computer as a WINS server for your local network and the OS X box can pull those wins values from the server on boot.
Click to expand...

Wow. This sucks. Why does Apple's SMB implementation have to suck so bad? I don't want to be running an old computer all the time just to fix this.

What if I entered a "dummy" IP address into the WINS servers list? Would that work LOL? All that's needed is for OS X to know the name of the workgroup it is supposed to be on. As long as it knows that, everything works.
 
toronado455 said:
Wow. This sucks. Why does Apple's SMB implementation have to suck so bad? I don't want to be running an old computer all the time just to fix this.

What if I entered a "dummy" IP address into the WINS servers list? Would that work LOL? All that's needed is for OS X to know the name of the workgroup it is supposed to be on. As long as it knows that, everything works.
Click to expand...

unfortunately no, you have to remember that apple had to write their smb code from scratch starting with lion. Maybe it's based on an old samba version though, not really sure.

perhaps you could put together a script to add the workgroup name at boot up?
 
alexrmc92 said:
unfortunately no, you have to remember that apple had to write their smb code from scratch starting with lion. Maybe it's based on an old samba version though, not really sure.

perhaps you could put together a script to add the workgroup name at boot up?
Click to expand...
OK, I suppose I can try to be a bit forgiving of Apple then. :rolleyes:
I like your idea about the startup script as a workaround. I used to write scripts in AppleScript years ago, maybe I can devise something.
 
See your OS X from Windows 7

on Your mac computer, Go to System Preferences, check File Sharing, on New Window check "share files and folders using SMB"
On Windows file sharing bottom filed you must see your user name, press done

Go to windows pc, go to network, give user name and password !!!!:)
 
Plus going from a 10.9.x or better OS X system and are trying to connect to Windows 7 or better using the string cifs:// instead of the smb://. This forces SMB2 to use the SMB1 connection instead. Windows 7 or better connects better with this command.
 
Try direct IP address

We have two servers running using OS X Server, occasionally and under duress I connect with a Windows machine. One server operates as normal, the other (identical settings, even with lots of tweaks) I have the issue where the Windows machine can "see" the server but never prompts for the login information and gives me "Windows cannot access" I solved this by typing the IP address of the computer I am trying to access instead of using the host name. You can see the IP address when viewing the File Sharing panel in System Preferences.
 
SStamatis said:
on Your mac computer, Go to System Preferences, check File Sharing, on New Window check "share files and folders using SMB"
On Windows file sharing bottom filed you must see your user name, press done

Go to windows pc, go to network, give user name and password !!!!:)
Click to expand...
Wow, way to bump a thread - one year later TO THE DAY! Thanks! I'll give this a try once I've got my network going again. I'm currently in single computer mode.
 
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.
 
Last edited:
  • Like
Reactions: SamWI
Gorazd said:
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\Lsaq\LmCompatibilityLevel
Click to expand...
Hi, what exactly does this registry edit do?
(I like to know what I'm doing and why before messing with the registry.)
 
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.
 
Last edited:
Gorazd,

I have WIN7 Ultimate; is it safe to delete LmCompatibilityLevel as well?

Also, I have disabled smb2/3 in WIN7; can that now be safely enabled?

Finally, are you mapping the Mac shared drive to a drive letter bypassing the NETBIOS name?
 
Awesome!

This worked for me, thanks so much. I was worried that my problem was that my Windows laptop is on a domain rather than a workgroup, and hence my I wouldn't be able to assign the same workgroup in WINS on my Mac. But I tried this and voila, I can map my shared folders onto my Win7 laptop.
 
Windows 7 File Sharing

@Gorazd Thank you ever so much. Your solution was spot on.
 
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"
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back