Copying to Network Drive Error code -36

I'm glad you find my posts so amusing.

The bottom line is, these are user-to-user forums, Apple engineers do not officially read them or reply to posts here except on their own time.

If you want an official response from Apple to an issue, you must contact AppleCare or join ADC and file a bug report.

Apple tests their software extensively. There are literally tens of thousands of ADC developers who test new releases along with those recruited explicitly to beta test software, both major releases and individual OS updates, such as 10.6.1, 10.6.2, etc.

But of course, testing doesn't catch everything, and when issues arise, they need to be reported to Apple, and (once again) AppleCare and the *Bug Reporter* are the mechanisms through which that happens.

So what, precisely, have I said that is confusing and/or amusing to you?

Complaining about an issue in these forums is like asking a big group of friends if they know how to fix an issue or if they're seeing the same problems. But asking why Apple doesn't take notice and do something is like having a problem with your car and being mad at its manufacturer for not fixing it without ever taking it into the dealer to be looked at - cathartic perhaps but not an effective way of arriving at a solution.

Very strange. Running dot_clean has helped me about half a dozen times, and have not failed yet. We're probably looking at different (albeit similar) issues here.

I'm sorry the workaround didn't work for you guys.

Ollie.

Correct, it seems there are different reasons for error code -36. Some people can't even copy, other like me can't launch a file which has worked before.
It might be possible the password settings for smb clients are the reason for copy failures.

So copying works here back and forth with windows computers, linux computers and a NAS via smb with no problems.

However launching a file with Finder from smb clients (e.g. open a picture in Preview) works with the smb computers but not when the file sits on the NAS. The thumbnail is shown in Finder but Preview fires up an error message: Preview could not be started, error -36.

Before the update to Snow-Leopard it has worked however.

Because anything works fine with the other clients but not with the NAS, I guess there is some trouble of different Samba versions between Snow-Leopard and the Samba version running on the NAS. Samba version has changed with Snow-Leopard, but I can't change the Samba version of the NAS to make things running as before.

<edited by host>

In most cases it is impossible to update a Samba version running on a NAS. It might however possible to lower the restrictions in a given Samba version to be friendly to different Samba versions running in a network by using the commands in the smb.conf config file settings.

Any Samba specialist is asked here for suggestions.

herveyw,

Thank you so much for posting that link to the apple article. I took the steps listed for disabling the stream, and now I have the functionality of my NAS back without having to ftp files to and from my local drive.

BTW, for those that might be wondering, I have a NexStar LX NAS box and this worked.

problem fixed...

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

Are you testing the latest seed of 10.6.2? That version is not commercially available, right?

I just change the color of the folder I want to copy to the windows server and I seems to work.

It is a major issue and Apple needs to address this pronto.

I was getting error code -50 and changing the color of the folder before copying it fixed it for me.

I just experienced the same. I have a shared drive on a network and prior to SL I was able to copy back and forth no problem. Now, error code -36. I guess we are all the beta testers for SL. I am having some other weird issues, I think I am going to have to revert back to Leopard.

I have spent a couple hours with Apple tech support and they seemed to know less than me about the issue. So here is my problem again in more detail:

1. When copying files between my snow leopard machine and my windows xp machine over smb I get error code -39.

2. When copying files between my snow leopard machine and my other macbook running 10.4.10, the file transfer gets stuck at zero kb.

3. No problems copying files between 10.4.10 macbook and win xp machine over smb.

I have tried via wired ethernet connection as well as over wireless and encounter the same problems. I have not tried a direct connection between the snow leopard computer and either the win xp machine or the other macbook running 10.4.10 because I do not have a crossover cable, if someone does, can they try it and see if they get the same problem? This cant be a universal problem as it is a far too big flaw and 10.6 would never have been released if you couldn't copy files across the network. I'm thinking that in the upgrade, some software is not compatible and is somehow complicating the transfer of files across the network. Could it be something to do with permissions? Anyone have any clues?

here is a screenshot of the issue:
http://www.zshare.net/image/650432085a7911cd/

I have an OpenSolaris system with smb shares: simple names, no spaces or special characters. From my Snow Leopard systems, I can create folders on the share, but I can't copy any files: when I try, the file gets created, but never gets beyond 0kb before I get Error code -36

@rust_ita
You mean the internal hard drive of the windoze box? I wonder how that could possibly make a difference.

Weird.

I neglected to mention that this was also working fine with Leopard for me.

Regards,
David