rmilorjr Posted August 18, 2017 Share Posted August 18, 2017 I just purchased and installed Unraid. I have a share named "Music" with multiple subfolders in which I have music categorized alphabetically. Through windows I can do whatever I want in the main folder, but nothing in any of the subfolders. Everything works fine if I move things around via the Krusader docker. If I look at security in windows it is showing the owner as ServerName/nobody for all of the folders in the share. The main folder allows full access to all other users (the share setting in Unraid is public). The subfolders have full access to user Servername/nobody, but read/ execute for everyone else. I have another folder for pictures where things are organized by date and I am going to want to be able to modify those pictures on other PCs and save them. How do I change the permissions in Unraid for the subfolders to inherit the main share security settings? I appreciate any help. Quote Link to comment
Frank1940 Posted August 18, 2017 Share Posted August 18, 2017 (edited) Let's see what the issue might be. First login in a console ot terminal (PuTTY) session and run this command: ls -al /mnt/user/Music You should end with some like this: drwxrwxrwx 1 nobody users 4096 Aug 17 18:18 ./ drwxrwxrwx 1 nobody users 58 Aug 17 16:42 ../ -rw-rw-rw- 1 nobody users 7726504 May 24 06:44 100-Magic_Act.mp4 -rw-rw-rw- 1 nobody users 169788268 Mar 2 2013 107D_OutdoorCupboard.mp4 If you don't see some of your music files go on down the directory tree by appending another directory/subfolder onto the end of the path. In this case the nobody is the owner of the file and the users is the name for group allowed access with the group permissions. If you don't have this, I would suggestion that you fix it with the Docker Safe New Perms Tool which is installed by the Fix Common Problems plugin. This should fix the problem with the current files but the any new files will be wrong. For this you will have to figure what of your Docker/plugin is generating these files and change its proprieties Edited August 18, 2017 by Frank1940 Quote Link to comment
rmilorjr Posted August 19, 2017 Author Share Posted August 19, 2017 Thank you Frank1940. The permissions were definitely wrong. The tool fixed the issue. Quote Link to comment
mgutt Posted May 9, 2020 Share Posted May 9, 2020 (edited) I have a similar issue. I'm having a share and created a subfolder through its user by an android app. This app is still able to create files inside this subfolder. Now I opened this folder with the same user through Windows and get an network error (Windows can not access ... You do not have permission...). Really strange 🤔 The user rights are looking good as well: And it becomes even more strange. I opened the share through its IP-address instead, entered the credentials, and are now able to open the subfolder without problems 🤪 Seems to be windows related or what do you think? EDIT: Ok, Windows Reboot solved the issue. Ok, thank you Windows 🙄 Edited May 9, 2020 by mgutt Quote Link to comment
Frank1940 Posted May 9, 2020 Share Posted May 9, 2020 (edited) I suspect that you have the 'attempt to login twice to the server' problem. It is discussed quite thoroughly in this post: EDIT: If this is not the problem, be sure to read the next several posts to see if one of the other SMB peculiarities are to blame. Edited May 9, 2020 by Frank1940 Quote Link to comment
trurl Posted May 9, 2020 Share Posted May 9, 2020 11 minutes ago, mgutt said: I opened the share through its IP-address instead, entered the credentials, and are now able to open the subfolder without problems 4 minutes ago, Frank1940 said: 'attempt to login twice to the server' problem Yes, going by IP vs servername makes Windows treat it as a different network computer and so different credentials can be used. Even though Windows will sometimes prompt you for a different login because permission is denied, it won't actually use whatever you enter at the prompt since you are already logged in with different credentials. Definitely a Windows quirk, since it treats other systems (even other Windows on the network) in just the same way. Quote Link to comment
mgutt Posted May 9, 2020 Share Posted May 9, 2020 (edited) 16 minutes ago, trurl said: Yes, going by IP vs servername makes Windows treat it as a different network computer and so different credentials can be used. I did not enter different credentials. I used the same. Now, after restarting Windows both clients use the SMB alias again. 25 minutes ago, Frank1940 said: I suspect that you have the 'attempt to login twice to the server' problem. It seems to be something related to this problem. Because the upload process through my smartphone has been interrupted. But I was able to restart the process without problems. The windows client is still able to open the folder and create files inside of it. It sounds like a bug for me. Something like "new login with same user = interrupt existing connection". I never had similar issues with my Synology NAS. Maybe a special setting needed for the SMB server? I'll try to restart the windows client and try to open the network share again while the upload through the Android Client is running. Let's see if it happens again. EDIT: Hmm no. The upload is still running and windows can access and write as usual. Strange. Edited May 9, 2020 by mgutt Quote Link to comment
trurl Posted May 9, 2020 Share Posted May 9, 2020 2 minutes ago, mgutt said: I did not enter different credentials. Did you enter any credentials at all? If the current Windows username and password will work to access the share, then it won't even ask you to login. Quote Link to comment
mgutt Posted May 9, 2020 Share Posted May 9, 2020 Just now, trurl said: Did you enter any credentials at all? If the current Windows username and password will work to access the share, then it won't even ask you to login. Yes, I did. My windows login is completley different from the smb share on the Unraid server. My Unraid share username is "marc" and for the smb alias I enabled the checkbox to save this login. As you can see I did not save the login for the IP, too: Quote Link to comment
mgutt Posted May 19, 2020 Share Posted May 19, 2020 Is this really related to Windows? I'm able to open any subfolder except of "EF": This happend while Plex (installed through Docker) is playing a movie contained in this specific subfolder: P.S. My user and Plex have only read-only rights in "\Movie". Quote Link to comment
trurl Posted May 19, 2020 Share Posted May 19, 2020 Do you know how to get to the folder from the Unraid command line and list the contents with their permissions? Quote Link to comment
mgutt Posted May 22, 2020 Share Posted May 22, 2020 On 5/19/2020 at 4:16 PM, trurl said: Do you know how to get to the folder from the Unraid command line and list the contents with their permissions? I really don't know why but /EF had other permissions: Quote Link to comment
itimpi Posted May 23, 2020 Share Posted May 23, 2020 5 hours ago, mgutt said: I really don't know why but /EF had other permissions: Those are not the normal permissions for an Unraid system. You normally expect to see the user/group to be nobody/users and not root/root. It sounds as if you copied the files/folders using a tool local to the Unraid server that has not set the standard permissions. Having them set to root/root will stop any access via the network working correctly. The permissions can be corrected by running Tools>>New permissions against the share in question. Quote Link to comment
mgutt Posted May 23, 2020 Share Posted May 23, 2020 (edited) 7 hours ago, itimpi said: It sounds as if you copied the files/folders using a tool local to the Unraid server that has not set the standard permissions. Yes I used rclone to fetch the files from the old NAS through SFTP. I'm not sure, but as I moved a new movie to /EF by using Tiny File Manager, that could be the reason of the permission change. Edited May 23, 2020 by mgutt Quote Link to comment
DaKarli Posted April 27, 2022 Share Posted April 27, 2022 (edited) On 5/9/2020 at 10:13 PM, mgutt said: And it becomes even more strange. I opened the share through its IP-address instead, entered the credentials, and are now able to open the subfolder without problems 🤪 Seems to be windows related or what do you think? EDIT: Ok, Windows Reboot solved the issue. Ok, thank you Windows 🙄 I just wanted to add, that what you describe in the a.m. first sentence is a "regular" Windows behaviour. Simply said, accessing the same fileserver, once by its name and then by its IP address are counted as two different connections for Windows. And this is the reason why you had to enter your credentials one more time and why, in this case, it solved half of your problem. Regards, DaKarli. 👍 Edited April 27, 2022 by DaKarli Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.