smb fix mavericks 10.9.5 breaks SMB connectivity to my Windows 8.1 PC

I also find smb share not working well on Linux servers.

When I share both '/' as 'root' and '/bak' as 'bak', only 'bak' can work.

$ ls /Volumes/root/bak/archive/

ls: /Volumes/root/bak/archive/: File name too long

$ ls /Volumes/bak/archive/

xxx yyy

SMB_NEGOTIATE AUTO_NEGOTIATE

SMB_VERSION SMB_2.1

Beginning with OS X 10.9.2, SMB connections to Windows 8.1 and Windows Server 2012 R2 (which use SMB 3.02) have been flakey, and we've continued to use the SMB 1 workaround (connecting via CIFS:// from our Macs). See http://macsmbissues.com and 10.9.2 Mavericks and can no longer connect to our SMB file share on the network. for more info, but it appears that Apple continues to deny the existence of this problem. The people at that macsmbissues web site have apparently given up, as have we. I guess we'll have to see if OS X 10.10 (Yosemite) fixes it, but I'm not holding my breath.

I don't think they fixed it at all. It was problematic already and now it works even worse. Not sure what the deal is. Mavericks has a lot of issues.

FYI it appears that OS X 10.10 (Yosemite) may have finally fixed this issue. I upgraded to 10.10 a few days ago, and had a need today to connect via SMB to my Windows 8.1 PC. So far I haven't had any delays or problems...will need to validate this against Windows Server 2012 R2 servers in the office.

Dear PleasantSpectrum,

your evaluation would be of great interest to me, because I testet the new Mac OS X 10.10 with our Windows 2008 R2 Server. The problem stayed the same. The Windows ACLs will be corrupted as soon as a new user logs in and the folders Desktop and Documents are created in the home directory of the server. As soon as the are created one does not have access to them anymore. E.g. if one created a file or a folder on the desktop, it just disappears after a few seconds.

Myself and my colleagues have had no issues with Windows Server 2012 R2 servers at the office, and I am getting reports from Mac users in other locations that Yosemite SMB connections to Windows Server 2008 R2 servers have improved as well. From our perspective this issue is resolved.

It depends on how you connect your Apple Yosemite Client to the Windows 2008 R2 oder 2012 R2 Server. We locate the users "local home directory" on the Windwos server. After the first user login a Desktop, Download and Library Folder (others follow) are created by the client. With Mavericks 10.9.5 all Windows ACLs will be corrupted by the Apple OS with the effect that files or folders which are created on the Desktop or in the Download folder just disappear. Mavericks tells you that your library has to be repaired. But trying to repair does not lead to a solution and the failure message comes up again. With Yosemite the Windows ACLs of the Library Folder are not corrupted, so the failure message regarding library repair does not show up - but the rest stays stays the same. It could be mentioned that it is possible to redelegate the Windows rights that access to the folders is possible again, but this could only be a temporary solution, because we have to create a lot of accounts on and on for guest scientists visiting our institution. We connect the Apple clients to our Windows Server 2003 R2 and 2008 R2 since Mac OS X 10.4. with no or minor problems - but this here is a real pain in the .. and I would like Apple to fix this finally soon! 😠