Copying to Network Drive Error code -36

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.

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

Here's the solution (an anomaly???). Under 10.5, when I connected to my XP computer, I could read / write files in the folders without having to have set permissions on the folder(s). Perhaps this was a bug in 10.5?

I went into my folders on the XP computer, and changed the sharing permissions to read and write. That solved my problem for Word, Excel and Text Edit. It also got rid of the error 36 code when copying files.

is strange but I can't write or read file in shared network drive but temporary file .DS_Store was normally writing by Snow Leopard on network drive.

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.

in my network share the files seems be copied but have size 0.

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.

Same problem. 2 Netdisk network hard drives attached by ethernet to my wireless router. Accessed via SMB. Both drives mount fine. I can copy files from them wirelessly to my Macbook, but cannot access files directly in-situ (bizarrely I can access the preview in the get info dialogue). files are text, pdfs, pictures, mp3s and movies. I cannot write anything to them, instead getting -36 I/O errors.

Both drives still function as they did previously on my desktop G4 running 10.4 Both drives worked fine under Leopard.

After waiting 7 hours for time machine to back up my system onto a USB drive and the best part of an hour for the trash to empty, I'm now regretting the upgrade.

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

PathFinder and Terminal cp don't seem to have this problem so, per my post in the Finder and Dock forum, I'm not convinced that this is a fundamental networking problem. It's a shame to have to install a 3rd party application to fix something that should be working in the OS (which is not to say that PathFinder isn't good in it's own right).

I think it depends on how recent your version of PathFinder is: I have the most recent update, and it definitely has the same problem as Finder.

But you're right, cp seems to work . . .

Regards,
David

could you write the command in full to copy by terminal on network share?

Further investigation:

I can load the files direct from the network drives into a program, but I cannot double click them to launch.

Sep 10 01:27:40 my-macbook kernel[0]: smb_maperr32: no direct map for 32 bit server error (0xc0000161)

I can quick preview the files.

Attempts to write to the drive file, but a file appears in finder with 0k filesize

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 