Copying to Network Drive Error code -36

same problem here.

Connected to a machine with XP Pro with a shared folder on an external drive ( connected via firewire ).
If I try to copy/move a file from Snow Leopard to the shared folder, I'll get the error -36.
No problems copying from Windows to Snow Leopard.

and... no problems copying from Snow Leopard to Windows if the shared folder is located in the internal hard drive.

(no problems with Leopard)

I have the same problem. Here are the details:

External Hard Drive with LAN (Buffalo Drivestation Flexnet: http://tinyurl.com/kk5mmu)
Mac OS X 10.6, on 3 different Mac Mini's

This error occurs on all computers when trying to copy a file to the 'SHARE' sharepoint on the SMB Drive:
+"The Finder can't complete the operation because some data in "filename" can't be read or written. (Error Code -36)"+


*I CAN*
Access / Read / Write this Drive in Windows XP
Access / Read / Write this Drive in OS X 10.5.7
Make new folder on this Drive in OS X 10.6
See a .DS_Store file which 10.6 has written to the Drive
Save a document to the drive from the Text Edit save dialog in 10.6
Save a document to the drive from the Pages save dialog in 10.6
Duplicate a document on the drive using Terminal (cp Untitled.pages Untitled2.pages) in 10.6
Copy anything to any other computer on the Network using 10.6


*I CAN NOT*
Copy a document to the Drive in 10.6
Duplicate a document on the Drive in 10.6
Save a PDF or JPG to the drive from the Preview save dialog in 10.6

*This error happens every time. It is easily reproducible.*

I hope that this information helps Apple get on to the problem soon.

Message was edited by: Luke Carbis 

Message was edited by: Luke Carbis 

Hi,

I got the file copying errors too, and the situation is the following:

1. I got a Synology DS-107+ NAS, and I got different shared mapped to my Mac using SMB.
2. I got a Windows XP PC using the same drives.

Before I upgraded to Snow Leopard all was working perfectly on both Windows and Mac using these shares, and to be honest I am unsure if the problems occurred with the SL 10.6 version or with the update to SL 10.6.1. The Windows PC still works perfectly, but when I attempt to copy any file to the shared drives on my Mac I get an error telling me that the action could not be completed as I do not have the rights to one or more of the items. (attempt to translate the Danish message I get to English). In any case it complains about missing rights.

Interestingly enough I am allowed to create a new folder, and delete this folder too, but an attempt to copy any type of file to the new folder or any existing path on the drives fail. There is no doubt it is an error in Snow Leopard, and I just came from the Synology support forum where people reported this error too, and someone referred to this discussion, and here I can see it is a general problem with NAS devices, and not just the Synology boxes.

I sure hope Apple reads through these discussions and takes immediate action (meaning fixing it with highest possible priority). I am new to the Mac side (just 3 1/2 month into my Mac life), but after many years in the Windows world I would say that one point where Apple falls through hard is their ability to send out updates that really screws up things that worked before the update. :/ I hope my future Mac experience will prove me wrong.

Could the problem we related to one that is discussed in the ReadyNAS forum? The new security (anti virus) in SL controls the copying or moving of files that are downloaded from the internet (or network?) using a new ACL. When these files are accessed for the first time you get a warning and you have to approve. If this has not been done yet, you get some deep access error when you try to copy them to a network share with a different file system and security setup.

When it has worked before with Leopard and after updating to Snow-Leopard without changing anything else it does not work anymore, it will be obviously a bug in Snow-Leopard.

Furthermore using muCommander with Snow-Leopard I am able to launch a file from the NAS as before without any problem, but launching the same file with Finder I get error -36.

So what?

By the way who is William? Does he belongs to the Apple staff?
So why he does not post something like: Yes, the bug is known and Apple works for an update.

I guess it might be a problem with different Samba (smb) versions. Samba runs on several computers in my network, but I cannot change the version on the NAS. With Snow-Leopard the special Apple Samba version has changed. Perhaps some config commands in the Apple Samba config file may solve the problem, but Apples Samba documentation is rather poor and I do not have the time to dig further into it.
Facts are that it has worked sufficient with Leopard and failed with the Snow-Leopard update.

chad, you should not have to unjoin your domain.
Follow the hint from Chris Eads: http://www.macwindows.com/snowleopardAD.html#121009a
This fixed it for me while I remain bound to my AD domain and can do a single login to my account and my shares.
I also want to make clear that no editing of /etc/nsmb.conf was necessary as well.

regards
Oliver

I ran into this same failure mode attempting to use a coolmax NAS CN390. I finally gave up on getting the NAS to work, it would never allow me to log on using any of my Mac computers (all snow leopard), I solved the problem by using one of my old IBM Pcs which was running Windows XP Pro. I am able to sign on to that system and store and share files and my printer, however, I have to keep another box running in the background on my network. It appears that only a NAS running Apples File control will work with Snow Leopard. SMB will work but only over a machine which is actually running Windows. Must be some scaled down version of SMB which is burned into the ROM on the NAS single drive servers which relies on components installed with windows or the older version of Leopard in order to operate correctly.

Seemed top have found an low tech non-terminal solution for error-50.

Label the folder a color, then drag on top the server. Should be good to go, and certainly weird!

Hi, if you're having these problems, could you provide the following information:

1) What type of files cause the problem - Applications, ordinary files, etc.
2) What kind of network storage is involved - Time Capsule, an OS X server, another type of server
3) Can you copy the file to another Mac via the network?

In our office re run a small Windows Server 2003 network - about 50% of the users are on Macs (15 laptops or so). We are seeing massive issues with SL Finder. Error 39, permissions issues and really weird and funky behaviour (you can create a folder but can't access it or save anything to it because you don't have the permission too). Very odd, please contact me if you are having same issue, right now many of us want to go back to Leopard...

OK, I'm having this same issue when copying files from Mac 10.6 to XP. In addition, the issue has manifested itself in another way also. Rather than repeating the issue, here's the URL on Apple. This is clearly a 10.6 issue.

http://discussions.apple.com/thread.jspa?threadID=2145198

I'm a bit late to this thread, but I posted a similar problem on the Finder and Dock forum. My iMac and my PC laptop are each connected to my internet router using ethernet cables. When copying from my iMac to the PC Shared Documents folder, I get the -36 error message, but individual files are copied successfully. However, if I copy a folder, only the first file in the folder is copied. The unix files (._, .DS-Store, etc.) that usually appear on my PC are not present.

i have leopard 10.5.8
I can log in to windows xp webdisc on server from work, get all documents and work with all documents.
If i want to put those documents or folders back from Leopard to the Windows xp webdisc i get error code -36
On top of that , after i got the error -36 warning, the originial document has dissapeared from the webdisc !

I want to replace my pc laptop at work with an iMac, but not when this problem can not be fixed

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.