SMB -36 ioErr when opening files

Hello everyone:

<---If you are getting the following error message, read this--->
The Finder cannot complete the operation because some of the data in smb://........ could not be read or written. (Error code -36).

Follow the steps below to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords. (You must be an administrator to do these steps.)

Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
Open the Terminal (/Applications/Utilities/).
At the prompt, type: sudo pico /etc/nsmb.conf
Press Return.
Enter your password when prompted, then press Return again.
You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
Enter the following into the file so that it appears as follows:

[default]
minauth=none


Save the file (press Control-O), press Return, then exit pico (Control-X).
Type: sudo chmod a+r /etc/nsmb.conf
Press Return.
Restart your computer.

<----Hope this helps everyone---->

Node927 wrote:
Hello everyone:

<---If you are getting the following error message, read this--->
The Finder cannot complete the operation because some of the data in smb://........ could not be read or written. (Error code -36).

Follow the steps below to configure your computer to use plain text passwords to make SMB/CIFS connections when the specified Samba or Windows (SMB/CIFS) server does not support encrypted passwords. (You must be an administrator to do these steps.)

Make sure that you are not currently connected to any Samba or Windows (SMB/CIFS) servers and that you do not have any Samba or Windows-related error messages open.
Open the Terminal (/Applications/Utilities/).
At the prompt, type: sudo pico /etc/nsmb.conf
Press Return.
Enter your password when prompted, then press Return again.
You should see an empty file and a "New File" notice at the bottom of the pico window. If you do not see the "New File" notice, this file already exists.
Enter the following into the file so that it appears as follows:

[default]
minauth=none


Save the file (press Control-O), press Return, then exit pico (Control-X).
Type: sudo chmod a+r /etc/nsmb.conf
Press Return.
Restart your computer.

<----Hope this helps everyone---->

Nope, I tried and did not work.

same problem here.

OK - I have the same problem with Windows Shares

For example, I want to use a firefox.dmg file on my home server (running WHS). The server is called bigbox and the path to the file is Software/OSX/firefox3.07.dmg

See the screenshot here which shows all the permissions at every level and I have read and write everywhere (As I should because I am connecting as bigbox\administrator)

http://erzz.com/downloads/errorcode36.jpg

If I try to execute the file directly of the share I get the input/output error (also included in the screenshot), if I try to copy the file from the share to my mac I get the error code 36 (also included in the screenshot) and if I try and copy via terminal I get "cp: Firefox 3.0.7.dmg: Input/output error"

Now to add some further mystery I WAS able to use these shares just fine with a fresh install of 10a432. I know this because I installed most of the software on the system from this same share. Thus one of the two(?) updates since could be the culprit?

I can create directories on the share, I can copy files from the mac to the share, and I can happily browse the share .... but not read!

Seriously, this is about the 15th issue I have spent many hours on already with Snow Leopard..... whatever happened to 'Just Works' ???

Node 927 - I also tried your tip and had no joy either. Thanks for trying though 😉

Same problem here, I've got a network drive hooked up to my router and I'm unable to open ANY file on the drive. It's giving me the (-36) error and it's saying that it isn't able to open the application needed to open the file.

Copying FROM the drive TO my MB works FINE. Copying TO the drive FROM my MB does NOT work.

On my iMac which has still got Leopard running, it still works fine, as it did under Leopard on my MB.

Fix please, Apple.

Hello guys
I have also a problem with 2 mac book pro 17 and fedora->Samba.
(that is the raid5 company network share)
I can't save files with firefox anymore... all file are zero bites (looks a full disk but it's not)

I can save files with all other programs even with safari (first set the download folder to the network)

It's really a firefox/10.6 problem becuase it worked the last 6 month without any problems. (all mac with 10.6 has this problem)

- i have removed the Firefox settings
- restarted in 32 bits
- restarted in 64 bits
- downloaded and reinstalled firefox (no new version)
- despered yes

I found a work around to part of this problem. I am connecting to the NAS/SMB through FTP client Filezilla. now I can transfer files to and from the NAS.

The only annoyance is that I can not work the files directly from the Network Attached Storage, but I have to transfer it to my mac, work and transfer back. Very inconvenient for Docs and Excel spread sheets. I hope Apple is working to fix the Finder.

I am also suffering from this problem.
MacBook Pro - connected via wifi to router. Router connected to Packard Bell 1GB external hard drive.

Tried using SMB as usual and get -32 error. Tried using a FTP connection but this does not work either. I get " The file could not be opened." All permissions etc are fine.

This happened as soon as snow leopard was installed, works fine in leopard.

Is this the place to raise the issue with Apple, or do I need to contact them directly ?

I found the solution to this, under these circumstances.

You can read, delete, rename, but not write / copy files TO a Samba share 3.0.x. FROM Snow Leopard
You can copy FROM a Samba share 3.0.x TO Snow Leopard
You can read, write, rename, delete and copy TO a Windows 2003 server FROM Snow Leopard

I tracked this down to "unix extensions = on" (which is default) in smb.conf on Samba share server.

Set "unix extensions = off" in smb.conf, restart SMB.

Snow Leopard can now write / copy to a Samba share.

Hope this helps others. I spent HOURS working this out.

Sounds cool, but I have an usbex landrive and I do not see the smb.conf in there.

I also have this problem and it is absolutely infuriating, I would have held off from Snow Leopard if I had known that this would happen.

Up this topic. Seems that nothing yet from Apple. I still can't write in a LAN Drive through SMB.

Everything is fine with SMB with a shared folder in widows. Is just an external Network Attached Storage.

You said, " I found a work around to part of this problem. I am connecting to the NAS/SMB through FTP client Filezilla. now I can transfer files to and from the NAS."

Hey, thanks for your post. I am having the same problem, but the the FTP workaround is usable for me as well and I really hadn't thought about it. I still need to access my NAS through Finder, but this does help me quite a bit. Again, thanks for posting it.

Message was edited by: Ardnij

Message was edited by: Ardnij