Unable to rename SAMBA subdirectories?

+1

Best regards

Same here.. I thought it was a pathfinder issue, but now I'm thinking snow leopard.

Hey man do you know something about boot camp?

Same here.
Server: debian squeeze, Client: OS X 10.6.1

Here is my smb.conf

[global]
+workgroup = UNIXGROUP+
+netbios name = %h+
+server string = %h server+
+security = user+
+dns proxy = no+
+name resolve order = bcast host+
+log file = /var/log/samba/log.%m+
+max log size = 1000+
+syslog = 0+
+panic action = /usr/share/samba/panic-action %d+
+username map = /etc/samba/smbusers+
+encrypt passwords = true+
+passdb backend = tdbsam+
+obey pam restrictions = yes+
+unix password sync = yes+
+passwd program = /usr/bin/passwd %u+
+passwd chat = Entersnews*spassword: %n\n Retypesnews*spassword: %n\n password\supdated\ssuccessfully .+
+pam password change = yes+


[homes]
+comment = home directory+
+browseable = no+
+read only = no+
+create mask = 0700+
+directory mask = 0700+
+valid users = %S+

[share]
+comment = share+
+path = /mnt/share+
+read only = no+
+create mask = 0770+
+directory mask = 0770+
+public = yes+
+hide files = lost found,tm

+[time machine]+
+comment = tm disk+
+path = /mnt/share/tm+
+read only = no+
+create mask = 0777+
+directory mask = 0777+
+public = yes+

[www]
+comment = webserver root+
+path = /var/www+
+read only = no+
+create mask = 0770+
+directory mask = 0770+
+public = yes+

I am able to rename a folder into any of these shares. But no way to do it for subfolders. The problem appears only with *Snow Leopard* (work on Leopard), on the Finder (for example i can create a folder and give it a name on the Firefox 'Save As' dialog window).

Message was edited by: san_

So I am going to add another thing strange to the mix.. I have a MacBook Pro with OS X 10.6.1 installed.. I mount several Samba mounts over wireless... On 3 of my 4 shares (all setup the same in smb.conf), I can rename directories without a problem. On the 4th, I can not...
But to even make it more strange, I have a Mac Mini, also with OS X 10.6.1, and the same share that I can not rename the files on my MacBook Pro, I CAN rename it on the Mac Mini..

Uggghhh!

Hi,

Just my 2 cents: same here, but opening a Terminal, mkdir /Volumes/sharename/some/random/subdir works just fine. For me a good enough workaround until the Finder gets fixed. Has a bug been filed with Apple?

Regards,

Guus

I updated the Samba server on version 3.4.0 together with Mac OS X 10.6.2 and it runs.

I'm running Samba 3.4.0 and still have this problem. Snow Leopard 10.6.2. On a Mac with Leopard 10.5.8 there are no problems.

Upgraded to Samba 3.4.2 and the problem went away. How odd.

sorry to bother with a dumb question, but I'm running samba 3.4.0 with the same problem (on ubuntu 9.10) can you tell me how to upgrade to samba 3.4.2?

thanks!

I found a thread on another site that fixed my SAMBA issue with 10.6.3. I have a CENTOS (REDHAT) server with SAMBA.

the thread said to add

to the global settings area of your smb.conf file.


unix extensions = no

reatart samba

I am now able to save files to my SAMBA share drives again from my MAC 10.6.3 laptop.

Way to go APPLE. I guess you have been spending to much time testing the iPad... and not testing some major open source applications with your code roll outs' for lesser Apple products like my MAC BOOK PRO.

Old thread, but upgrading the samba server from Ubuntu 9.10 to 10.04 solved it for me.

Regards,

Guus

Does the hint in the blog post Fixing Snow Leopard 10.6.3 Samba Write Access help at all?

AHH! I just upgraded to 10.6.4, supremely confident that this issue was addressed (connecting to a Linux box with Samba 3.4.0) and I just got a permissions error trying to rename a directory. The I switched to Windows, same login to the fileserver, and the rename worked fine.

Ahh... 😟

And I lost write access to my directory on a remote Windows server that I mount via SMB after upgrading to 10.6.4. Now it mounts read-only, even though "Get Info" reports "read-write" access: any write operation fails with "no permission" message.

Oddly it used to work on 10.6.3 - and stopped working as soon as I upgraded to 10.6.4.

Thanks, Apple!