Q: Copy fails with error -36 (introduced with 10.9.2)

Same problem here.

Server: 10.9.2 & Mac 10.9.2 = Error 36

Server: 10.9.2 & Mac 10.9.1 = No error

Im still running Server 3.0.2. Going to hold off on 3.0.3 since most of the mac are working fine. Luckily i only updated one of the Macs for the company i work for.

A "soultion" for me was connecting via afp.

This is so annoying considering 10.9.2 was meant to bring more stability to smb!

You can try turning off smb on your file share. Forcing connecting macs to use afp. Windows machine will be unable to connect of course. If you try this can you let me know how it goes.

Thanks

I'm having this issue with SMB also -- it appears to affect all clients running 10.9.2.

10.9.1 had some SMB stability problems (connections would drop), 10.9.2 made it worse with an error -36 on every copy!

Thank you, it worked for me.

SMB has  not been working well for me since it's began to be the default with 10.9.

I can only hope that Apple fixes the SMB problems really soon and finally. I convinced companies to switch to OS X Server. Now we have the mess.

If your after a stable mac server for file sharing use 10.6.8 (iv had experiance with all OS / server updates and this was the best for file sharing. SMB still had to be tweeked now and again tho, normally was just a restart of the service would cure any problems).

I'm very tempted to use 10.6.8 as a file server on an old mac pro then have 10.9 on a mac mini for the other features.

Lets hope 10.9.3 will be better.

Thanks a lot for evaluation - I have exactly the same problem:

10.9.1 was working 10.9.2 has this bug!

Unfortunatelly I have to use SMB - so this is not a workaround for me.

10.9.3 is in beta testing, which brings much-needed updates to smb according to reports. People brave or desperate enough can find it here.

http://bestblackhatforum.com/Thread-Mac-OS-X-Mavericks-10-9-3-Build-13D12-Update --119828

I'm neither brave nor desperate enough to try a beta in a work environment. Update at your own risk!

I tried the beta, still same problem of error 36

pls apple fix this, bring back Steve if you have to, it is not acceptable to realease bad updates with no possibility to roll back.

A most curious thing, from another post I learned that with an original installer it is possible to revert to earlier versions. I installed 10.9 over 10.9.3 but the problem that was introduced with 10.9.2 persists. I guess the only way to solve it is a fresh install.

Until Apple finally fixes this issue, there might be another workaround: it is still possible to use the "old" SMB implementation by connecting to the server via cifs://myserver instead of smb://myserver. When doing so I do not experience error 36 anymore. Please note that the information window of the mounted network share still shows smb://myserver/myshare, that's all right. The only issue is that upon reconnection after a reboot or wake from sleep finder obviously switches back to Apple's own SMB client again. I have yet to find a possibility to force finder to use cifs:// instead of smb:// on a regular basis. Maybe there's an app for this... ;-)

By the way, using the classic SMB implemention can also solve certain issues when connecting to windows network shares: Apples version is not able to access folder-mapped-drives within a windows share, while using cifs:// it works just fine.

Another interesting fact is that (at least in my case) only network shares making use of ACL are concerned. The user's home directories, for example, completely rely on classic POSIX permission and copying files to those shares works like a charm. But as soon as I add ACL permissions for a specific user (or a group he is a member of) the error 36 shows up. Unfortunately there are some shares to be used by several users, so using ACL on them is imperative for me.