I have 5 user shares that all have identical sharing settings and have their smb sharing options set to "public". However, on 2 of these shares, I'm unable to write as any other user than root.

 

I have three users:

- root

- htpc (my htpc user)

- <windows username> (to match my login on my win7 box)

 

I have tried connecting to the troublesome shares as all of above three users, but only root is able to write. I have tried both creating a directory as well as creating a new file. Both fail if not root on the two shares, but work on the other three.   Windows 7 pops up a dialog with title "Destination Folder Access Denied" and text "You need permission to perform this action" and then the name of the folder. Incidentally the shares with problems are my video shares, "Movies" and "TV Shows". Probably unrelated, or... ?

 

I have tried setting the sharing options on the troublesome shares to both "secure" and "private" and with both setting the full read/write access for the htpc and windows user, but that didn't change anything.

 

There are no immediate issues in syslog nor in smbd.log. The only thing that smells a little like problems is the following line that appear sometimes in syslog (but not correlated with my connection tries):

Storage logger: /usr/sbin/nscd: relocation error : /usr/bin/nscd : __nss_services_lookup, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

 

Any help or insight would be greatly appreciated!

I would like to know a solution to this to.  I find the problem happening when I add, remove and add the same user name.  The best solution I found was to add a user of a different name and set the rights and it would work.

I have the same type of setup as randominator and some shares will work just fine but then other would that are setup the same way will have access control problems.

 

Additional information: I tried accessing the shares using the commandline smbclient to eliminate the client being the problem. Again, same results: Could not put files or create directories.

have you run the update permissions utility?

@Joe L.: Thanks! That did the trick!

 

Before running it, I went and had a look at the folders through the commandline. Most folders had been created from copying a mounted ext4 disk with my exisiting data to the array. I had used rsync to be able to restart it if it failed along the copy, and had (foolishly) set the -a flag (archive = preserve permisions and ownership). Hence, (some of) the folders were owned by root, which appeared to be what was causing the problems.

 

Thanks again for the prompt help! I'm a total newbie to unRAID so I had overlooked the util in the menu, thanks for pointing it out.