Currently Being ModeratedApr 24, 2012 5:50 AM (in response to docmars)
Hi docmars, strange you've had no reply!
I'm sorry I'm not able to help you, though, as I'm having the same problem.But can we just share some information here please? On your PC when you click on Network in explorer, can you see an entry for your mac. It sounds from the above as though you can, since you enabled file sharing on your mac account. However, on my PC I can see no entry for my macbook at all.
But like you, I have perfect communication in the mac >> pc direction.
There must be someone out there to shed light on this!
Currently Being ModeratedApr 24, 2012 6:03 AM (in response to docmars)
Try turning off the Mac firewall. If you are behind a router you don't need it enabled.
In the options section of Sharing make sure your username is listed and checked and that you have input the correct password.
Currently Being ModeratedApr 24, 2012 6:44 AM (in response to docmars)
I had this problem too. Interestingly, one Lion machine which I had worked perfectly, i.e. Windows 7 could connect fine; this machine had been upgraded through many OS X versions over the years. A new Mac with a clean Lion install exhibited the problem you describe.
I compared the two smb config files and there was a difference. Take a look at your
My working Mac had one extra entry in its plist:
So I edited the plist (you'll need to use sudo to do this) and added this key, then turned File Sharing off and on again -- or reboot if you're superstitious -- and it began to work for me.
Currently Being ModeratedApr 26, 2012 7:28 AM (in response to docmars)
On the Lion side try turning off SMB shares then back on again. Then try to map your network drive or browse the networks from the windows side. I must toggle SMB shares every time I reboot the Lion "server".
Currently Being ModeratedMay 3, 2012 4:40 PM (in response to CGraffix)
I just tried both of these possibilities (AllowGuestAccess: true, and unchecking/checking the SMB share option) with no solution.
This is so strange!
Currently Being ModeratedMay 4, 2012 1:08 AM (in response to docmars)
To be honest, my AllowGuestAccess tweak was most likely a red herring. Even after that change, I had a recurrence of the problem later on (after machine restart), The next time I just turned sharing off and on again and it fixed the problem for me, so that was probably what had fixed it before too.
Another factor is that when my Windows machines can't connect, other Macs can connect using an smb:// URL. The Windows machines are all joined to an Active Directory domain and would be automatically attempting a connection with (Kerberos?) domain credentials first, which would fail. I wonder if a non-domain Windows machine would work? I'll test that next time it bites me,
Currently Being ModeratedMay 4, 2012 1:22 AM (in response to docmars)
One more comment, of a diagnostic nature: rather than using the Windows GUI to connect, try connecting from the CMD prompt. It will probably still fail, but you may get a better or at least different error message back that gives you a clue. If you've got a server called MAC with an smb share SHARE you would map this to your X drive as follows:
net use x: \\MAC\SHARE password /user:username
Oh, and you don't say so specifically, but I presume you have verified that your Mac machine name is resolvable by Windows, i.e. "ping MAC" works? You could also try using the Mac's raw IP address in place of MAC in the connection command, to eliminate DNS issues.
Currently Being ModeratedMay 4, 2012 10:21 AM (in response to ben43)
ben43: I tried your suggestion with both my Macbook's hostname and the local IP. I was able to ping the IP successfully, but not the hostname.
net use does not work for either. "The network path was not found." every time. I've never had this much trouble trying to network Windows + Mac. Although, this is my first Lion machine, so that's the difference.
Currently Being ModeratedMay 8, 2012 1:17 AM (in response to docmars)
If you can't ping the machine by name then this sounds like a different problem and it's not to do with Lion's SMB configuration, but is a DNS issue. It sounds like you think your Mac is machine name "MAC" but your router does not agree. In System Preferences / Sharing, under "File Sharing: On" what does it list as the machine name? You may need to do something to make your Mac and the DNS agree what the name is.
Alternatively, since the IP address works, add a hosts file entry to the Windows machine to manually name that IP address.
And if you try to connect to the share by IP address on Windows, e.g. \\10.1.x.y\SHARENAME, does that work?
Currently Being ModeratedMay 31, 2012 12:31 AM (in response to docmars)
Try checking your Advanced TCP/IP Settings under Windows 7. Mine was somehow set to append a custom DNS suffix (in this case my remote workplace domain) -- I believe my VPN client software might have been the culprit. Once I changed it to 'Append primary and connection specific DNS suffixes' (the generic option for name resolution), I had no problem connecting by hostname to my Lion-based Mac.
Currently Being ModeratedMay 31, 2012 6:50 AM (in response to markopolo73)
I checked my Advanced TCP/IP settings and since I haven't installed any software that depends on this feature, it was already set to the default. I am still not able to connect, even after trying everything you all have suggested. It's so crazy!
I even tried installing Samba3 on Lion and setting it up... still a no go.
Currently Being ModeratedJun 3, 2012 10:18 PM (in response to docmars)
I, too, have spent hours today troubleshooting this.
At this point, it is working, but I don't yet know if the 'temporary nature' of this 'working' condition, as described by others, has yet to expire.
Between now and when it may stop working, here is what I have found to be relevant in solving the problem for:
- a straighfroward sharing setup between Windows 7 and a Mac OS X Lion ( 10.7.4 ) workstation
- where Lion is hosting a share with SMB sharing enabled
- where Lion was installed fresh, without carrying over any history from previous versions of the OS
- where Lion can connect to Windows 7 shares with ease
- where the same Mac machine was performing SMB sharing flawlessly while running Snow Leopard, but everything stopped working once I installed Lion
- Windows: LAN Manager authentication in Local Security Policy on the Windows machine does NOT appear to be relevant ( this was required back in the Leopard days, but was not required by Snow Leopard, and does not appear to be required by Lion ); I have two Windows 7 clients working, and one of them has the value 'NT & NTLM + NTLMv2 if negotiated', while the other has 'Not Defined' as the value; both of these configurations are currently working.
- Windows: IPv6 settings don't need to be altered from the defaults
- Lion: The WORKGROUP setting in Network Preferences/Advanced/WINS must match the name of the workgroup to which the Windows machine belongs. The workgroup name does NOT have to be "WORKGROUP", but it does need to match the Window's machine's workgroup name. NOTE: it is easy to omit the "Apply" step when making this change, but unless you hit "Apply" you will find that your changes do not stick.
- Lion: The WINS server IP address value is blank
- Lion: The configuration changes prescribed here MAY be CRITICAL, but I am unsure. In my working configuration, this prescribed configuration is in effect. ( if you are curious about the 'com.apple.smb.server.plist.lockfilefile' living alongside 'com.apple.smb.server.plist', read this.
- Windows: to Map the Network Drive in Windows to the Lion SMB share, using Windows Explorer is the quickest, most straighforward method: enter \\LIONNETBIOSNAME in the address bar, and expect to be prompted to enter your Lion user account credentials
- Windows: choose "use a different account"
- Windows: the username must be fully-qualified, as in LIONNETBIOSNAME\shortusername. ( The advice given in Lion's Sharing Preferences pane to use IPADDRESS\username is unnecessary )
- Lion: in my case, despite having gotten all of the above in place, I was still unable to connect. The final piece of the puzzle appears to have been, in Sharing/FileSharing/Options:
- uncheck the box next to your user account
- authenticate the change
- click DONE
- Again in Options, uncheck SMB sharing
- click DONE
- Again in options, enable SMB sharing
- Check the box next to your name
- click DONE
- Repeat steps 6, 7, and 8
My guess is that step 5 is critical, but it may be rendered useless by having completed step 9 first, such as during previous attempts to get SMB sharing working without ( knowledge of ) it.
In all of the Googling I've done today, every single one of these pieces of information was available, but none of them was synthesized into anything useful as a stand-alone solution. My hope is that the next person to stumble across my recipe finds that it also works for them; better still if they can further refine it to eliminate the uncertainty that remains in my account...
Currently Being ModeratedJun 17, 2012 6:53 PM (in response to abwc)
HOLY CRAP!!! I've been plagued with this bizarre problem for months, with absolutely no concrete idea as to why. On a lark, I decided to just try your final steps... nothing else... AND IT WORKED!!! All I did was:
uncheck the box next to your user account
authenticate the change
Again in Options, uncheck SMB sharing
Again in options, enable SMB sharing
Check the box next to your name
And instantly my Windows machine can login to the Lion shares with nothing more than entering the Lion machine username & password into the Windows 7 prompt.
Thank you so much for posting this. Obviously some setting internal to OSX was just "stuck" and systematically unchecking & rechecking everything in just this way, fixed it. I had previously checked & unchecked just about everything, but not in this specific, methodical way. THANKS AGAIN!!!