No rights to write on SMB mounted volume after updating on 10.6.3

Hey guys,

This was the post I sent to apple feedback

"Please see http://discussions.apple.com/thread.jspa?threadID=2382501

This problem is affecting anyone running a NAS over SMB. This was not an issue till the 10.6.3 update

Users getting
"The operation can’t be completed because you don’t have permission to access some of the items."

This is only affecting FINDER copies. Copies or file distribution (itnues or other apps) are not affected."

Note that the supplemental update was not intended to fix this problem:

Tip: If you don't see the Mac OS X v10.6.3 Supplemental Update in Software Update, you don't need to install it.

Note: The Supplemental Update is for any system that was updated from Mac OS X v10.6 using the Mac OS X Update Combined v10.6.3, build 10D573. It is not needed on systems that were updated from Mac OS X v10.6.1 or 10.6.2, and it is not needed on systems that were updated from Mac OS X v10.6 using the Mac OS X Update Combined v10.6.3, v1.1.

http://support.apple.com/kb/HT4014

i got this same problem as well!

apple please look into it!

link to my thread is here http://discussions.apple.com/post!reply.jspa?messageID=11426367

I am using a Thecus N5200 and macbook pro here. I have had some suggestions connecting to the server via afp://xxx.xxx.x.xx

When i mounted the server using afp://xxx.xxx.x.xx it was acceptable in copying across pdfs and documents. It worked fine. I have heard though that the transfer rate is diminished as compared to the smb protocol. However after trying that i tried mounting the server again through smb:// this time i realised that there was a difference - recently i had been mounting the server as smb://n5200 as opposed to smb://N5200. Therefore i tried mounting it by smb://N5200 again and it seems to work flawlessly. The only difference was a capital N but it seems to like it more.

Will run more tests and diagnostics to see if its "fixed" if not i hope apple has a solution by next update

We shall see how it goes. Keep us posted please!

Message was edited by: nairdajun

Snow Leopard 10.6.4 was released today (2010.06.15):

http://support.apple.com/kb/DL1048

Apple says:

The 10.6.4 Update is recommended for all users running Mac OS X Snow Leopard. It includes Safari 5 and general operating system fixes that enhance the stability, compatibility, and security of your Mac, including fixes that:... *+_address issues copying, renaming, or deleting files on SMB file servers_+*

I'm having similar (or same) issues when interacting with SMB mount. See my other post:

http://stackoverflow.com/questions/3040456/snow-leopard-mounted-directory-change s-permissions-sporadically

I will be testing 10.6.4 to see if it fixes the problem. However my issue is accessing not "copying, renaming, or deleting ..." as stated in

http://support.apple.com/kb/HT4150

-- Galen

I, on the other hand, had the problem before 10.6.3. And was happy to see that this update would fix it. But the only way now OSX lets me copy to the smb share is save through the application related which is not a very fast way to copy files...
Finder says that i have read/write permissions but i actually don't! The only things i can do through Finder is delete and quicklook.
Lies on update fixes or am i missing something?
Please help...

Can not offer a solution but can report my results.

Updated to 10.6.3 on a new machine with 10.6.0 pre-installed.

Mounted an SMB share via Go menu Connect to Server then "smb://(server name)/(sharename) entered username and password.

Mounted, able to create, delete, move, and copy items via the Finder. Create and save Office 2004 Word docs and Excel spreadsheets.

The smb share is on a Windows 2008 Enterprise Server. Tested as a local machine admin and as a network user with no admin rights. None of the accounts used have admin rights to the smb share.

All I can suggest at this point is to review the console logs and the Event viewer logs if on a Windows server.

I will be monitoring for any issues in this area as we are a cross platform environment with users on Mac OS and Windows XP with both Mac shares and Windows shares with dedicated servers for both. I wonder if the issue is confined to NAS volumes via SMB?

Same problem here. With 10.6.3 i can't add files to a shared directory on my debian server. With 10.6.2 everything was working just peachy, so i'm kinda disappointed. Updates in general shouldn't add new bugs, but resolve current ones.

I've restarted, repaired file permissions, run monthly, weekly and daily scripts (the whole shebang with Cocktail).

The actual message is
- "The operation can’t be completed because you don’t have permission to access some of the items."

Console.app reports:
- "Finder [821] Unable to quarantine `FILENAME_REMOVED': 1"

Same thing here.. I updated to 10.6.3 and the access to one NAS (Thecus N5200 Pro) doesn't work anymore. Same write errors as described by others. But the access to the old Terastation NAS still works. Access on both with SMB.

Does anyone has a workaround?

Message was edited by: PhilWe

Message was edited by: PhilWe

Same problem here. My QNAP-NAS shares refuse to accept new files via SMB and the Finder.

Read, modify and delete works but copying a new file to the share fails:
"The operation can’t be completed because you don’t have permission to access some of the items."

What I find most interesting: If I copy the same file via Terminal it works flawlessly. Did anyone of you try this?

--
Markus

Markus Barta wrote:
Same problem here. My QNAP-NAS shares refuse to accept new files via SMB and the Finder.

Read, modify and delete works but copying a new file to the share fails:
"The operation can’t be completed because you don’t have permission to access some of the items."

What I find most interesting: If I copy the same file via Terminal it works flawlessly. Did anyone of you try this?

--
Markus

Yes, i did try copying with the terminal, and that did work ok.

The odd thing is, the problem has magically disappeard for me. It has never happened before, it was surely related to the 10.6.3 update, but for me at least, it works again. Maybe i did something to make it work? I dunno.

Did anyone of you having this problem, mess with the quarantine settings? I had previously turned off the warning prompt for newly downloaded files, and wondered if that was related (if you check my previous post, there is something related to quarantine in the console log).

This is the console message

3/31/10 7:09:15 AM kernel Locum (map: 0x93ee8f8) triggered DYLD shared region unnest for map: 0x93ee8f8, region 0x7fff82800000->0x7fff82a00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Still unable to copy anything to the NAS -

Same problem here, also copying via Terminal works perfectly.

I have two MacBooks and upgraded only one of them. The one with 10.6.3 cannot copy via Finder, while the one with 10.6.2 works flawlessly.

I have the same problem just after updating to 10.6.3. The problem occurs when copying local files to a Samba server when the local file has extended attributes. Look at the extended attributes of a file with the xattr command.

For example, I drag a URL from the address bar of Safari looking at Apple.com to my Desktop. This will create a shortcut file that has the extended attributes

@crispy:~/Desktop $ xattr Apple.webloc
com.apple.FinderInfo
com.apple.ResourceFork
com.apple.quarantine


Finder will not copy this file to my Linux samba server, complaining that I do not have sufficient privilege. If I remove all the extended attributes with the xattr -d command, then the file will copy.

xattr -d "com.apple.FinderInfo"
xattr -d "com.apple.ResourceFork"
xattr -d "com.apple.quarantine"

In the terminal, rsync will copy the file, even when given the -E switch, which copies extended attributes. This seems only to be a Finder issue.

My Linux server version is Debian Lenny which uses Samba 3.2.5. Compiling the latest stable version of samba on Linux does not fix the problem.

I tried turning on Windows file sharing on another Mac desktop computer running 6.3.2. I can copy to that computer without errors.

I own a Network Appliance filer with native smb support. I do not get errors when writing to that server. So this seems to be an issue with Finder when writing to a non-apple samba server.

There are suggestions to disable "darwin stream" support in the Linux server. At least in my case, doing so, completely breaks my ability to mount shares from OS X. In any case, here are the lines in smb.conf that I attempted to use.

vfs objects = darwinacl
stream support = no
ea support = no

I also tried touching .com.apple.streams.on in the root of my share. No effect.


1. Does anyone see these problems when copying to an apple server?
2. Is this problem new to 10.6.3? Many posts described this problem long ago, but I've not experienced it until 10.6.3.
3. Anyone have a workaround that works short of removing extended attributes.

I've recommended that my users not apply the 10.6.3 patch until I have a workaround. This is fatal for my group so far. Everyone is having to use the terminal to copy their files.

This bug combined with a graphics bug affecting Aperture really makes you wonder about Apple's quality control. They just made my system unusable, corrupt previews in Aperture and no backup to NAS. Great!

BTW, terminal copying to NAS works while displaying an error message about extended attributes. But files do get acrosss. Not that this is an acceptable solution by any standards.