Copying to Network Drive Error code -36

For a single file:

cp filename /Volume/sharename

for a folder/ directory,

cp -r foldername /Volume/sharename

Regards,
David

problem fixed...

I use an ftp program , called "Fetch" .
Now i can put all documents back on the webdisc

We have some users having the same problem.

What is the size of your remote network share?

I saw a posting somewhere (I'm sorry, I can't find it now) that suggested the size of the remote drive might be the issue. Drives under 2 terabytes work, drives over 2TB don't. We have one user (10.6) who has verified that he can write to all network shares except those which are larger than 2TB.

Windows Server 2008, Windows Active Directory domain, etc. CP works from the Terminal, but Office applications and many Finder operations fail with the same read-only errors everyone else is reporting.

All drives in my setup are smaller than 1TB. It also does not seem to be directly related to file size - I have colleagues, along with myself, that can repro this with a wide variation of file sizes. I am going to attempt a packet sniff to try to understand what is happening at the SMB protocol layer.

Same problem over here. Trying to connect to SMB shares, and I get this silly error. Single files appear to copy before I get the type 36 error. They are about 4K smaller then the original and I can seemingly open and read the copied files fine. However, this error blocks me from transferring more then one file at once.

Moreover, I can open files on the network and edit them without getting any error messages.

I was fine with 10.5.x, and all of the 10.5.x / 10.4.x Macs in my office still work fine.

Please look into this. This is a nasty bug that really impacts daily work.

As others have described, copying files results in error -36 after one file successfully copies. In addition, the update to 10.6.1 is no help. I am mounted to a distributed file share (DFS) via SMB. Worked before I upgraded to SL.

I am getting around the problem for now by creating a ZIP of local files and copying the single compressed file to the DFS. Once copied, I can successfully decompress the ZIP in the DFS location.

Man! I hope a fix to this is coming soon.

So 10.6.1 is out already. It appears that Apple let Marketing take precedence over Engineering in their rush to get SL out before Windows 7 is released. We're now all Beta testers. Apple is getting more like Microsoft every day. Here's hoping 10.6.2 fixes our problems.

same problem here. setup: 10.6.1 mount a 3TB share via nfs(opensolaris server)

i have big problems with reading files / folders with special characters (worked with 10.5)

and the same copy error. BUT: sometimes it works, when i create a new folder in the share-root i can copy a file to this folder, but when i copy a file to the new createt folder in "/tank/multimedia/dll/foldername" i get the "-36 error"...

and i only copy files, no moving, after i moved 50GB of files and all new were 0b and the older were deleted...

i switched from linux to osx 3weeks ago, and i am very unhappy. it can't be that thee are bugs in the filemanagement. 😟

papierschiff

I have this problem, too.

Here are the specifics:
10.6.1 (also had the problem with 10.6)
I'm using finder to copy a local file to a Windows Server 2008 share mounted with cifs.
I get error code -36, but the file seems to copy successfully.
I did not have this problem until I upgraded to Snow Leopard.

On the server, I have 5 shares -- 3 of them are affected by this problem, 2 of them are not.

A call in to Apple support and problem solved!

1) Repair the permissions on your hard drive in Disk Utility.
2) Reboot

That's it. We have no more Error Code -36 on our Windows shares. This worked on both of our Snow Leopard Macs.

Just repaired permissions... still have the same problem.

Didn't fix the problem for us, either. Thanks, though!

Repair disk permissions is the Apple equivalent of take 2 aspirin and call me in the morning. It's their remedy for everything.

Repairing disk permissions is the first thing I tried a week ago. It didn't work. 10.6.1 hasn't solved the problem either.