SMB -36 ioErr when opening files

Also running into this issue. Copying and pasting files into Finder from a local disk to a CIFS server (Solaris CIFS) results in "The Finder can’t complete the operation because some data in “xyz.pdf” can’t b e read or written.

(Error code -36)"
And there will be a file of 512 bytes on the CIFS share.
Apps writing directly to the CIFS share have less problems, for now it looks to be a finder only issue.
This worked fine in previous Mac OS X releases.

I have exactly the same issue - My windows box will allow me to set-up folders etc on my work Network shared discs..

The iMac connects via SMB - I can copy files, but get the -36 error (although the file does actually copy).

Secondly, when I try to add folders from the Mac Finder, the folder is created, but has a tiny 'No Entry' sign in the bottom corner.

Trying to access the new folder says that I do not have permission.

10.6.1 hasn't solved anything either.

I don't have Snow Leopard to play with, but I am curious - Is there any difference in behaviour if connecting "smb://" versus "cifs://"?

I get error code -36 when I try to copy files to my network disk but I have been able to work around it using the cp command from the terminal.

Wish I found this thread earlier. I assumed the problem was with the network disk so I backed up the data and reformatted it! Oh well...

J

The latest update did not fix it for me.

Excellent, many thanks iainwhyte. I set "unix extensions = off" in smb.conf [global] section and restarted samba, no more Error -36.

I struggled with Error Code -36 for quite a while, in the end what helped me (YMMV) was using browseable = yes on the share definitions in the server smb.conf file.

Same symptoms as everyone else, inability to open files on NAS, or save new ones through Finder. Either Passwords have to be off or numeric to get a login - even then opening still fails with -36 error and file saves are zero bytes.

The only change to break the system is moving to SL.

Using FTP or changing conf files on the NAS server is not a solution. Many of us use systems with no admin permissions on the server, or the system is embedded and the source code and compiler to build our own conf files is closed source.

If you look at common thread, SL is broken somewhere deep in the authentication and permission algorithms. Every other OS I have (including Leopard) works fine.

similar to everyone else but I can access files on NAS fine thru other Mac apps (iTunes/iPhoto) - here's my post from Windows Compatibility forum:
--------------------------------------------------------------------
glad to find this post and will look under 10.6 Finder - I have exactly the same with accessing files on a NAS drive: thing is iPhoto and iTunes are fine - music and photo libraries of reasonable size are both on the NAS.

I rang Apple support at the weekend and they refused to log a trouble ticket as they said they wouldnt be able to investigate/confirm a problem due to the 3rd party equipment being involved.

Even the logic of "but two of your software products are producing different results" would not sway them!!

Not impressed!

Thanks

----------------------------------------

Will try the "iainwhyte" solution and advise success or otherwise!

Had the same problem (-36), but found a way to get rid of it.
the origin of the problem seems to be file authorization, or
It was a bit of 'try on error', but here are the steps I made:

create a /etc/nsmb.conf
[default]
domain=[WORKGROUP]
minauth=none

and reboot system

Then I created a new user account on my Mac with username:password identical to the user on SMB server. The user must have all the permissions on the share to mount.
In this account I made a connection:
Finder, [apple]+K (Connect to Server pop-up) and made the connection
smb://[WORKGROUP];[username]@[SMB-SERVER]/[PUBLIC]

Fill here your stuff, in my case it was smb://WORKGROUP;beekw@ACACIA/PUBLIC

Added the password in the keychain. Notice that username is [WORKGROUP/username]
Since then the problem is gone, also on the other accounts on the Mac.

I have no idea why I had to create the user (without I still had the problem). Probably having user [WORKGROUP/username] and WORKGROUP set in snmb.conf should be enough.

But anyway, it worked for me and hopefully it helps you too.