Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Some Windows 7 computers cannot log in to Yosemite Server regardless of user

I just upgraded our office server from Mavericks to Yosemite hoping it would resolve some of the ongoing funkyness I and others have been experiencing with the SMBX server component for Windows file shares.


The upgrade went remarkably smoothly for the most part, with most Mac and Windows clients not even noticing the difference.


However, two of my Windows 7 clients are unable to connect to the server--they get a password failure message regardless of what account they try to log into (including my own admin account), and regardless of what account the local Windows machine is logged in to. Trying to connect to the server, or map a drive on it, simply fails as if the user credentials were rejected. They are, however, able to bring it up the web interface via HTTP, and print through it via CUPS, so it's not a DNS or routing issue. They also bring up the login dialogue correctly, indicating that they're talking to it, it's just that the login fails even with known-good credentials.


I've tried rebooting the Windows clients multiple times, clearing everything out of Credential Manager in Windows, making sure there are no phantom connections listed in Connected Users on the server, even deleting and re-adding users on the server. The only thing I haven't tried is rebooting the server because I can't kick the other 20 users off during the day for the sake of a couple.


All the Windows clients, both working and not, should be configured the same. The only thing I can think of that might be different with the two that are misbehaving is that they may have been left on during the update while the rest were shut down, but it seems like a reboot should have cleared out any stuck connections from this.


Any suggestions? What the heck is going on here? Random errors I'm used to, but not rejecting al logins as if it had a bad password, and only from certain systems.

Posted on Oct 22, 2014 2:28 PM

Reply
27 replies

Apr 9, 2015 8:33 AM in response to Marc Marshall

Does anyone know of a solution to this that does not involved editing registry settings in Windows? I have Server 4.0x installed in a large corporate environment and we have several PCs that need to connect however all the PCs are corporate imaged and cannot be toyed with. I managed to get a few connected via the FTP service but it's far from ideal and convoluted to explain to a user who is used to mapping drives.


I have tried enabling smb:ntlm auth = "yes" and smb:lanman auth = “yes" on the server.


But it makes no difference....

Jul 25, 2016 4:07 PM in response to Marc Marshall

Yes! Your answer finally got my Windows machine to show shared files on my OS X machine! I have only ever seen this work once in my lifetime and I can't believe the answer lies in some obscure registry setting that I don't believe a single OS X or Windows developer even knows about, probably.


Now if I could only find out why it shares my entire hard drive instead of the public folder that I selected...

Some Windows 7 computers cannot log in to Yosemite Server regardless of user

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.