MacOS – Copying files to SMB share in Finder: Error code -36

errorfindermacosnassmb

I have a MacBook Air running OSX 10.11.6, and a WD My Cloud NAS device running Linux. It is no problem to copy files using a web interface, SFTP (i.e. SSH), and rsync.

When using Finder to access the network share (which I have mounted using the built-in feature in OS X) it is not working. I can list the files (they are listed slowly), but I cannot copy files to or from the NAS.
I receive an Error code -36, which means an I/O error. I don't know how to find anything more specific.

I have tried using 1 byte files, as well as 2 GB files.

It works when accessing SMB shares on other network devices from my MacBook Air, as well as accessing the aforementioned SMB share from other computers. I can also use Time Machine on my MacBook Air to make backups onto the NAS.
I.e. the only thing that doesn't work is the direct link between my MacBook Air and the NAS when using Finder.

Do you have any suggestions on how to fix this problem?

Best Answer

The problem was solved using the utility Keychain Access.app to delete the keys related to my NAS. After a restart, I had to provide login credentials, and copying files was once again possible.

Related Solutions

MacOS – How to you avoid error -43 when copying symlinked folder in Finder with a SAMBA share

In your configuration, you have unix extensions = no which is fine, but that is why symbolic links on the server are showing up as folders and not aliases. In this mode the server resolves the symbolic links and the client never sees them. If the client tries to create a symbolic link, the server actually generates an alias file, not a host-OS symbolic link. Reasons for this include security (preventing someone from getting access to /etc/passwd on the server by creating a symbolic link to it) and client compatibility, as OS X and Windows and Unix have slightly different ideas about what constitutes a symbolic link but they pretty much agree on what is a directory or a file.

Permissions issues with SAMBA are complex, so it's not clear that you do not have a permissions issue. Likewise symbolic like resolving is complex, so it is not clear that what you are doing should, in theory work, and there's always the possibility of a bug (most likely in the SAMBA server).

When accessing a SAMBA server from a Mac, these identities and permissions are involved:

The Mac User you are logged into the Mac as
The SAMBA user you are logged into the SAMBA server as
The SMABA server host OS user you get converted to
Unix-style file permissions
For NTFS and HFS+, associated file-system ACLs

So even though you have provided a lot of information, it's still not clear that you are not having permissions problems. The fact that you can mv and cp on the server (using what account?) does not mean you do not have a permissions problem preventing you from doing it on the client (using what accounts and with what effective account on the server?).

If the server is supporting ACLs and since you have options like inherit permissions = yes and inherit acls = yes set there could be some kind of ACL problem that is only allowing read access to directories accessed via symbolic links. There are several other avenues of investigation based on the server configuration.

I would really expect you should be able to find more information in the SAMBA server logs than you have communicated. They should give you a much better sense of exactly what is being denied.

For what it is worth, I tried to duplicate your setup using an Ubuntu 12.04 host as the SAMBA server and could not reproduce your problem. Symbolic links worked for me as expected.

MacOS – Cannot write to SMB Share with Terminal OS X 10.8

The problem here is that terminal is trying to write Unix style permissions to the CIFS share during the copy operation.

When you perform "cp" via terminal the data will transfer but the fchmod command will fail as the "core CIFS protocol does not provide unix ownership information or mode for files and directories".

A few solutions:

Mount the share via command line and engage the noperm option to ignore permission errors.
```
mount_smbfs -o noperm "//DOMAIN;username@myshare.com/blah" /Volumes/blah
```
Alternatively you can use rsync to copy files (without the -a flag)
```
rsync -rl source destination.
```

Source: https://www.samba.org/samba/docs/man/manpages-3/mount.cifs.8.html

Best Answer

Related Solutions

MacOS – How to you avoid error -43 when copying symlinked folder in Finder with a SAMBA share

MacOS – Cannot write to SMB Share with Terminal OS X 10.8

Related Question