I have a question regarding permissions and SMB shares in Unraid. I have the problem that when I upload a file in my cache disk share, for example, that the user created for another SMB private access becomes the owner. I read somewhere here in the forum that this is due to Windows and that only one user is supported by Windows. Well is stupid, but then that is probably so.

 

But also the permissions are not quite correct, because they are set to -rwxrw-rw- instead of -rw-rw-rw-, as set by the Fix Permissions Tool. Is there any possibility there? Of course I would also always prefer the owner to be nobody instead of smb_user, but I don't think that can be done differently for private access, can it?

4 hours ago, sasbro97 said:

Of course I would also always prefer the owner to be nobody instead of smb_user, but I don't think that can be done differently for private access, can it?

 Not to my knowledge.  I have never found a problem with the owner being the Share user that writes the file-- apparently, in your case, smb_user.   

 

4 hours ago, sasbro97 said:

I read somewhere here in the forum that this is due to Windows and that only one user is supported by Windows. Well is stupid, but then that is probably so.

It seems so when when looked at casually.  However, if you think about it, each client computer only needs one SMB logon because that client can be assigned permissions--- no access, read only, read/write --to each Share consistent to the client's needs.  In larger systems with hundreds of users, allowing more than one login per client computer would be an administrative nightmare.  Remember that MS is really more concerned about the big corporate and government SMB users than the small percentage of home users who use SMB!  Most, if not all, new Windows computers are now setup to prevent access to servers unless the client has a SMB login to that server-- no more server access using 'Guest' privileges allowed!

 

IF you absolutely require a second login, there are two 'tricks' you can try:

 

First, try to access the server via the IP address or the server_name --  \\192.168.2.238 or \\TOWER --depending on what the first connection was established with.  (I have not been able to use this trick for some time and I suspect MS may have plugged this hole.)

 

Second, you can knock down all LAN connections from the client computer as follows:

 

Quote

you would close any windows that might have a previous connection to the first public share, then open a command window and type "net use * /delete".  That command closes all current server connections.  Now click on your Private share and enter "curly" user name it will work this time.

From   https://forums.unraid.net/topic/25064-user-share-problem?tab=comments#comment-228392