Currently Being ModeratedApr 1, 2012 7:08 AM (in response to gerdgruhn)
Was having issues connecting to my Mac from my Windows 7. The correct answer on this thread got my thinking. Found that my workgroup name was blank on my Mac. Filled that in on my Mac and bam...done. I am working in a Active Directory LAN. Both the PC Windows 7 and the Mac Lion are not on the domain.
Currently Being ModeratedApr 2, 2012 2:54 PM (in response to gerdgruhn)
I have had this issue for a while now. I actually gave up on it and just went back to my SL server. I started messing with it again and was having the same issues. I then went and downloaded all updates. made sure my shared DNS name in the sharing preferences was the same as my hosted name. Dropped and re-added the server to the domain. Renewed DHCP (if not on static) and went to hit it from a Windows machine and BAM, it worked. Tested it from a OS X client and it worked. It also removed the issue of having to type in .local after the DNS name as well.
Currently Being ModeratedApr 8, 2012 9:52 PM (in response to mambro)
This solved my problem on a Vista Home Premium to a Mac OSX Lion SMB share where it seemed to have worked intermittently then stopped working altogether a few days ago for some reason - unsure if a Windows or Mac OSX update brought the problem to the fore or perhaps a combination of logged credentials.
Many thanks my friend!
Currently Being ModeratedApr 25, 2012 7:16 AM (in response to mambro)
This trick with "regedit" works like a charm :-) Thanks mate!
Currently Being ModeratedAug 5, 2012 8:36 AM (in response to pkaplan2524)
Which servername are you using - the server is named as intranet.local, but no amount of login attempts succeed; log excerpt:
2012-08-05T16:34:18 digest-request: uid=0
2012-08-05T16:34:18 digest-request: user=intranet.local\\accounts
2012-08-05T16:34:18 NTLM domain not configured
2012-08-05T16:34:18 digest-request: kdc failed with 36150275 proto=unknown
2012-08-05T16:34:18 digest-request: guest failed with 22 proto=ntlmv2
I have tried INTRANET\accounts, and the IP address, but none work....
Any ideas, as this is driving me (and my client) MAD!!
Currently Being ModeratedNov 3, 2012 11:04 AM (in response to Alex Narvey)
Thank you very much, Alex!
I'm on Windows 7 Home Premium connecting to a Mountain Lion server and this worked for me.
Now I can connect with the method described by you manually, BUT my server is still not shown on the Explorer window.
Anyone can guess why?
Currently Being ModeratedNov 29, 2012 12:29 PM (in response to mambro)
I tried all what is said here (thanks all b.t.w.) and it worked .... only once ....
When I rebooted VISTA, I could not reconnect to MAC (window popping with same old nasty request for username and password that never works)
But ... I found a fix, by chance :
- go to "System Preferences/Sharing/Options"
- Uncheck "Share files and folders using AFP"
- go to "System Preferences/Users & Groups"
- Click the lock to allow changes
- Click on "Guest User"
- Uncheck "Allow guests to connect to shared folders"
And now... it seems to work flawlessly, but please don't ask me why !
After all, these hours were not spent uselessly.
Currently Being ModeratedNov 29, 2012 2:11 PM (in response to Clemgill)
By enabling Guest access to your shares, have you not just bypassed your user access security. Now anyone can access your files?
Currently Being ModeratedNov 29, 2012 7:35 PM (in response to TRA2010)
I actually disabled the Guests connection to share folders on the MAC.
I still have same name and password on WINDOWS and MAC.
Not sure I understand your point.
Currently Being ModeratedFeb 11, 2013 1:52 AM (in response to gerdgruhn)
There has been no update to this thread since November so I don't know how people are doing with this issue.
I don't have a fix, just a workaround. The problem is related to Kerberos. The password doesn't pass the Kerberos stage when connecting with SMB.
My workaround is to create a local user on the Lion Server that hosts the share and to use those credentials on the PC.
Currently Being ModeratedFeb 11, 2013 6:37 AM (in response to ludovic leroy2)
I have given up. I'm just telling my Win7 users to buy a Mac!
Currently Being ModeratedFeb 11, 2013 6:51 AM (in response to Don Seher1)
It works for some, as it does for me. Make sure you have DNS lookup(s) working for your server at the client, and both server and client are using a common NTP server so that the time is completely sync'ed between workstation(s) and server.
I have an entirely stock 10.7.5 server and a stock Windows 7 (sp1, 64-bit) client connects to it always without issue - note - using an Open Directory not "local" (non-OD) account on the server.
Currently Being ModeratedFeb 11, 2013 6:54 AM (in response to Don Seher1)
Upgrading the server to Mountain Lion and Server.app 2.2.1 would be a lot cheaper than buying a new Mac.