Copying to Network Drive Error code -36

1) VMWare image files and any files in some directories
2) copying to a FAT32 drive
3) No problem with copying the same files to my other MacBookPro on the network.

The only way I am able to copy the files is if I navigate to the lowest directory where the files are directly. Then copy the files without copying a folder. It appears to be a folder linkage issue when copying the files.

I hope this helps in correcting the problem. I have back up massive amounts of VMWare image data. I hope this problem can be fixed quickly.

Imac 2008 version 2.6Ghz etc.

Same error code - retrieved a FOLDER full of wav files and tried to drag/drop in to a USB stick on the desktop. Code 36 comes up.

Solution was to drag and drop the individual files within the folder - no problem. But why...

Steve1812

Yes, definitely.

In early December a downloaded DMG file was copied on my system (iMac 27 inch) to a network RAID drive (Netgear) over SMB. Bad idea. The SMB file protocol was knocked out, or had its capacity reduced to between 10 and 1% percent of previous values.

The workaround was to use NFS instead, although the character issues are troublesome (NFS differentiates between upper and lower case).

The late in December another problem appeared as I started backup and file sync procedures again. They started to hang because completely unrelated files were absent.

I have subsequently found one such file in the /Volumes directory, where it is impossible to delete. The file is designated as a directory (zero length), permissions are such that the file can not be discarded, not even as a sudo user.

For more on the subject, see the posting at:
http://discussions.apple.com/thread.jspa?threadID=2284881&tstart=210
here on this forum.

It is my belief that something creates this directory entry when the machine is booted.

Applecare has the problem, but have yet to come up with a solution.

Any ideas on how to remove cause?

BR,

peter

Zipping the pacakged file or using the "cp" command in terminal works where Finder gives you the -36 error... Apple please solve this!!!

Hi, I am having the same problem. In my case, my network share (a Time Capsule I use for sharing, not backups) uses AFP. I have only experienced the problem with applications, not with ordinary files. I have tried to repair disk permissions but this does not help, and I have checked the file permissions for some files, but this is not the issue. One workaround I have found is to create a compressed version of the application and copy the compressed version to the network share.

If you could provide more information about the cases where you have experienced the problem, that would be helpful: what kind of file(s), what kind of network drive, how you are mounting (AFP, SMB, etc.).

Also:

4) What protocol are you using to connect to the share: AFP, SMB, etc.
5) Have you successfully copied other files to the same server? If so, try to describe the differences in these files (name, size, type, permissions, etc.)

I'm seeing this on two machines upgraded to SL connected to a Windows 2008 Server running Active Directory and using AD integration on both Macs. This setup was fine before the upgrade to SL, now I get almost permanent errors with Finder copying files - both small and large - to the server but never an error using Terminal with cp. Sometimes the copy actually completes but Finder ends with a -36 error. I'm also using Mobile User Home Sync but so far that hasn't generated any errors but I'm starting to get nervous.

Lots of the following in Console logs, not sure if it is related:

9/7/09 2:54:13 PM /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[1054] * process 1054 exceeded 500 log message per second limit - remaining messages this second discarded *

So far, not a happy bunny with SL; I have everything on the network server so might be time to revert to Leopard.

I can confirm that I have this error message when copying files to a D-Link DNS313 NAS via SMB (over 100mbit ethernet).

Everything worked fine in Tiger, and worked in Snow Leopard (10.6.1) fine for a while, then suddenly stopped working and hasn't been working since.

I have resorted to opening Windows XP via Parallels Desktop to copy files to my NAS. It really isn't good enough that it hasn't been addressed yet.

I opened a new but in the Apple bug reporter about 2 weeks ago, but the status is currently "open".

I really hope 10.6.2 fixes this problem because it is a big one for me.

TidBITS wrote about this bug recently: http://db.tidbits.com/article/10772 - this issue is broader than just SMB. I wish Apple would address this ASAP. Several of us have reported it but I have heard little about fixing it.

There are two issues: copying to an SMB (Windows) share and copying to an AFP (Apple) share. Apple claims that 10.6.2 fixed the issues with copying to an SMB share but there are still problems with copying to an AFP share.

Dear all!
First of all gentlemen have you searched the net for this problem with -36 error.

1. Have you defined if it's a Windows error or an OS X error?
2. Have you defined if it's a Windows driver error or not?

I my self wrote on this discussion thread a long time ago and got help and was able to find a work around. My problem was not error - 36. It was SMB (Samba) and OS X together. Nothing to do with Windows. But in the same time it was.
The error 36 is usually a hardware problem. That will say a driver problem. Look for the proper drivers or new/changed drivers.

We have on the other concluded that their is a bug within 10.6.2 between OS X and SMB 3.0 - 3.3.4 which builds on Windows. For exemple on Linux servers we use SMB as the Windows communication shell. We create shares and users for Windows and for Macs to use their common networking shares and applications.
If that isn't working properly a lot of companies with Linux servers and MACs have problems.
With 10.6.2 a lot of companies have to have workarounds for Office for MAC, for example. So, the problem is not error 36. It's SMB(Samba) (Windows (not Netbios)) and OS X10.6.2.

I personally have my MACs connected to Linux servers with SMB and they are working fine as long as I'm not saving Excel work sheets directly to my share.
I instead save it to my work space and afterwords copy it to my share.

To conclude. Both my MACs ar connected to hardware's that keep my backups via TimeShare. One is a IOmega drive and the other is a Netgear ReadyNas. They both works fine under 10.6.2. Both my MACs are also connected to my Linux Server with Suse Linux Enterprise Server 10.3. That's my problem where I cannot save directly to my share without saving to workspace first and then copying. I can live with it for the time beeing but I am certain that Apple already knows what the problem is and that they will solve it in the next upgrade.

Best regards
Dag S.

CarCode:
Thanks for the tip on muCommander. From this discussion thread, the problem with NAS drives using SMB appears to have been introduced in a recent release and that Apple is aware of the problem.

In my configuration, I can write to the drive but the write fails after creating a zero byte file. Could be very dangerous copying back.

muCommander provides me with a partial work around pending a new release to fix the problem. At this point, my take is to wait for the next release before investing additional hours.

See here whats happening with wireshark:

10.0.0.200 is the Windows 7 machine. 10.0.0.253 is the iMac.

No. Time Source Destination Protocol Info
23 6.200303 10.0.0.200 10.0.0.253 SMB Negotiate Protocol Response, Error: Out of memory

Frame 23 (105 bytes on wire, 105 bytes captured)
Ethernet II, Src: 02:23:54:80:b4:22 (02:23:54:80:b4:22), Dst: Apple_f2:be:60 (d4:9a:20:f2:be:60)
Internet Protocol, Src: 10.0.0.200 (10.0.0.200), Dst: 10.0.0.253 (10.0.0.253)
Transmission Control Protocol, Src Port: microsoft-ds (445), Dst Port: 49177 (49177), Seq: 1, Ack: 52, Len: 39
NetBIOS Session Service
SMB (Server Message Block Protocol)
SMB Header
Negotiate Protocol Response (0×72)

Same problem here. Cannot copy a Numbers file to the Windows server. Same error -36. Leopard worked just fine. Saving the file from Numbers using "Save As" seems to work though.

Try changing the color label of the folder.