I'm troubleshooting a weird problem with our fileserver at work and wondering if anybody has a suggestion.
Server is running Yosemite, clients a mix of MacOS from 10.6 through 10.10, and some Windows 7 boxes.
With the server on 10.10.1 and the just-prior version of Server, everything basically worked. Last night, I updated the server to 10.10.2 and installed the latest small incremental Server update. Now almost all the Macs are fine, but the Windows clients are all getting permissions errors when trying to connect. Even weirder, one Yosemite client was also getting an error on login when trying to connect via SMB, both on 10.10.1 and 10.10.2; the same computer on AFP works fine.
I'm already aware of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel needing to be at least 3 (or non-existent, so it defaults to 3 on Win7); I figured that out myself, the hard way. These clients already have that registry key set.
Suggestions?
[Edit: I realized that, regardless of whether you're connecting from a Mac or Windows client, if you mount the server without a specified share, it mounts and the user's shared home folder is visible and accessible. So SMB isn't flaking out entirely, it's just not showing any of the main shared volumes when connecting via SMB, regardless of the user connecting or the OS of the client. AFP works as expected. What the heck?]
Server is running Yosemite, clients a mix of MacOS from 10.6 through 10.10, and some Windows 7 boxes.
With the server on 10.10.1 and the just-prior version of Server, everything basically worked. Last night, I updated the server to 10.10.2 and installed the latest small incremental Server update. Now almost all the Macs are fine, but the Windows clients are all getting permissions errors when trying to connect. Even weirder, one Yosemite client was also getting an error on login when trying to connect via SMB, both on 10.10.1 and 10.10.2; the same computer on AFP works fine.
I'm already aware of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel needing to be at least 3 (or non-existent, so it defaults to 3 on Win7); I figured that out myself, the hard way. These clients already have that registry key set.
Suggestions?
[Edit: I realized that, regardless of whether you're connecting from a Mac or Windows client, if you mount the server without a specified share, it mounts and the user's shared home folder is visible and accessible. So SMB isn't flaking out entirely, it's just not showing any of the main shared volumes when connecting via SMB, regardless of the user connecting or the OS of the client. AFP works as expected. What the heck?]
Last edited: