Hi

 

I upgraded 4.7 to most recent 5.0 (rc6-test2)

 

Then I ran 'NewPermissions'

 

I also created two new users, in addition to 'root'

 

Old files - that were created on 4.7 - work

However, the files I copied after the upgrade - do not.

 

The difference is that their owner is one of the (new) users I created above.

I can only access these new files using the new user.

 

The other problem with Windows is, however, that it somehow authenticates with cached (?) account,

unRaid for some reason allows log-in, but do not allow the access to the new files..

 

thank you guys,

this is already 2nd day into this upgrade and my family has no video neither audio :-(

 

 

 

Since I was not able to playback music.. I ran again NewPermissions (although it was planned to run once, isn't it?)

 

It fixes the issue by changing the owner from 'michaeln' to 'nobody'..

 

I assume next time I copy files to unRaid server they will acquire ownership of 'michaeln' and I will have the same issue..

 

What am I doing wrong?

Since I was not able to playback music.. I ran again NewPermissions (although it was planned to run once, isn't it?)

 

It fixes the issue by changing the owner from 'michaeln' to 'nobody'..

 

I assume next time I copy files to unRaid server they will acquire ownership of 'michaeln' and I will have the same issue..

 

What am I doing wrong?

The fix permissions script needs to be run any time you copy files when logged in as root.  It is NOT meant to be run only once unless all file moves/copies are done via SAMBA or NFS.  They (SAMBA/NFS) properly set the ownership of the files.   

 

SAMBA is accessing the files as user "nobody".  You either need to grant "nobody" permissions to traverse the directories and read the files, or change ownership to "nobody" so it can.

 

In prior versions of unRAID security was lax (nearly non-existant at times) and access was all done as user "root"  This has changed in recent versions to better support access through various protocols.

I was **not** logged as root, but rather 'michaeln'

 

On the other computer, I was trying to access, though, I am not sure at all which user the system was using.

But then I logged in via Putty and with smbstatus I saw that these sessions receiving 'access denied' are using uid=99, which is 'nobody'

 

 

I do not understand what's happening.

All my shares are declared as 'public' and I understand that the ACL are not applied in this case...

restart all the windows machines

First, at which side is the problem?

Machine that created the file?

 

Machines that are accessing?

 

 

Is it normal that the ownership is 'michaeln' for new files?

Is it normal the I can access the directory only when the uid is changed to 'nobody'?

Why the accessing machines were authenticated as 'nobody' but 'readonly' access?

is it kind of guest? I did not see any guest account..

 

I just verified that if I create the file from the machine that (above) could not read - the other can now.. (e.g. the opposite way it works)

E.g. if the file is created with 'nobody' uid, it will be fine.

 

I just don't understand why is it 'nobody' in one case, and 'michaeln' in another..

 

 

 

I see in /etc/samba/smb-names.conf the following line

map to guest =  Bad User

 

and also in /etc/samba/smb.conf there is

invalid users = root

 

First, at which side is the problem?

Machine that created the file?

 

Machines that are accessing?

 

 

Is it normal that the ownership is 'michaeln' for new files?

Is it normal the I can access the directory only when the uid is changed to 'nobody'?

Why the accessing machines were authenticated as 'nobody' but 'readonly' access?

is it kind of guest? I did not see any guest account..

 

If you really have to ask these type of questions, why are you creating user accounts?  When you create a user account, you must understand exactly how Linux is going to handle the access to the files which belong to that user and how you gain access to them in your larger network environment. 

 

Many people never add a user to their unRAID system.  It is not necessary in most cases.  In the default configuration, unRAID grants full access to all files which are shared by either SMB or NFS.  Version 5 changed the requirement that for this to occur that the files have to belong to 'nobody' in an attempt to increase security.  (I have not double checked but I think all system files are owned by 'root' and previously everyone had full access to them.)

you're right, I do not need accounts,

but 'root' account does not work anymore with V5 (does it?)

 

can I remove the accounts except for 'root', run 'newpermissions' again,

..and which user/pass shall I use to access the SMB shares?

..and which user/pass shall I use to access the SMB shares?

none

you're right, I do not need accounts,

but 'root' account does not work anymore with V5 (does it?)

 

can I remove the accounts except for 'root', run 'newpermissions' again,

..and which user/pass shall I use to access the SMB shares?

 

When everything is working correctly, you click on Network (either the shortcut on your desktop or in the left pane on Windows Explorer).  Then you click on your unRAID server.  Your shares should than show up.  You can then browse your shares and access all of the files.  NO PASSWORD IS REQUIRED!!!!

 

If you have a problem, it is because Windows is setup to automatically go a user share and is using a password to access the server.  If this happens, your next question should be how to get rid of this setting.  (Sorry, I don't know how as I have avoided using any Windows file sharing security as it is really, really tricky to get it to work right.)

Thank you, guys.

 

I removed the additional accounts I created,

re-run the 'new permissions' - without closing the browser (otherwise the process stops/freezes the GUI)

 

Looks like it is working now fine.

 

 

 

 

 

 

If it still logs in as a user, you can delete the cached credentials on the windows side. To do this go to the start menu and in the run/search box type credential manager. From there you can remove any credentials being used to access the server

thanks!

re-run the 'new permissions' - without closing the browser (otherwise the process stops/freezes the GUI)

Now that sounds like a BUG.  (the freeze if you close the browser)

re-run the 'new permissions' - without closing the browser (otherwise the process stops/freezes the GUI)

Now that sounds like a BUG.  (the freeze if you close the browser)

yes, this happened to me 2-3 times with test2...

I also double-checked with ps and noticed that the chown/chmod is not there anymore

and the GUI is killed.. until reboot