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

I just found this article:

"About named streams on SMB-mounted NAS, Mac OS X, and Windows servers; "-36" or "-50" alerts may appear"

http://support.apple.com/kb/HT4017?viewlocale=en_US&locale=en_US

Didn't someone say they were "escalating" this topic? This is a nightmare for someone who just convinced people not to use a Windows Server. I'm still on hold with our 10.9.2 server waiting for a fix.

This error has become a complete nightmare for our company....  Since we all pretty well use Mac's, I tried the turn off SMB box to force AFP connections as was suggested.  That seems to work fine for any station that hasn't upgraded to Maveriks, but most of us are on Mavericks.  When using a Mavericks client, the server doesn't show up with SMB turned off.   Am I missing something,  How are you guys connecting your Mavericks clients with AFP?    APPLE PLEASE FIX THIS ASAP!!!!!!!

Apple doesn’t routinely monitor the discussions.

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

Try "Connect to server..." in the finder's "Go" menu with afp://servername. Or use cifs://servername, that should connect via the legacy SMB implementation without error 36 (works with me, anyway).

To facilitate reconnection via afp, you might want to drag the frequently used shares into finder's sidebar. Doesn't work that way with cifs, I'm afraid, it has to be done manually each time the connection has been severed.

Thanks FlyingLemming, that seemed to work.  This error was driving me nuts.  At least I can now function but it leaves me with wasting my time teaching everyone else in my company on how to do this.

Eric Root.  Thanks.... I have just submitted feedback as you have suggested.

In another thread (https://discussions.apple.com/thread/5944699) someone stated that Apple support has been able to reproduce the error and escalatedmit to engineering. Chances are good that they are working on it since it is a severe issue regarding Apple-to-Apple connections. If it affected access to windows shares they'd probably not care that much... ;-)

Found a working solution to this issue by now, or let's call it a "permanent workaround". ;-)

See my post from 03/23/2014, 05:06 at https://discussions.apple.com/thread/5944699?start=30&tstart=0

If possible use AFP over SMB1. It's more reliable and faster.

10.9.3 beta 3 is out (hopefully this means the official update is soon). If people are desperate enough to try it you can find it here.

http://store.heaveniphone.com/2014/03/mac-os-x-mavericks-beta-11093-13d21-mac.ht ml

Ben, that might be true, but in my specific case AFP is no solution. Although not recommended,  i am depending on hardlinks to folders on my server, and AFP has some issues with that (they are not showing up at all).

CAUTION: There has been a little typing error in my posting of the workaround in the other thread. The correct lines for nsmb.conf would be:

[default]

smb_neg=smb1_only

Mind the "neg" instead of "net" on the second line...

I just closed all connections to the server. After I made a new one with "connect with server" from the Finder Menu and I connected to: afp://192.168...../

...and it worked out!

Bevor the connection was made to the name of the server, not the IP address and there the issue occured, like all other people wrote. Same with SMB.....

OSX server & client: 10.9.2

OS Server version: 3.11

10.9.3 out, still no fix for the bug... will it ever be fixed?

I'm yet to update. Has anyone had a good experiance with 10.9.3?

10.9.3 appears to have fixed it for me.  At first I thought it did not fix it as I only updated a client machine and checked but after updating the server to 10.9.3 everything seems to be back to normal (Server and clients need to be updated).  I made sure I was connected solely through SMB and I was able to do a multi-file copy without errors (something I was not able to do in 10.9.2).   I noticed it did not work fro Fredrokk so I'm not sure why it worked for me and not him.  Lucky me I guess. LOL...

Hi,

I can confirm that updating the server to 10.9.3 seems to fix this problem.

Cheers!

Updating the OS or Server app on my Mac server always scares the **** out of me, but this time it might be worth the sweat... ;-)