NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Permission problems with Windows 10 Pro - ReadyNAS 2120 v2 - Office 365
Dear All, Since moving to Windows 10 Pro I am having significant permission issues with our ReadyNAS Share access. I have tried the basics but cannot seem to create a username/pass combination to ...
I created a test user called AG with Pass "test" and no email. Then set folder permissions to:
Network Access:
admin + AG -----READ/WRITE
File Access:
folder owner - guest
folder group - guest
Unchecked "Grante rename and..."
admin + AG -----READ/WRITE
I run the DOS command and the Network location appears but I do not have permission to access it
C:\Users\AndrewJSGebhardt>net use t: \\172.16.105.196\Scan /user:AG test
The command completed successfully.
Start by allowing everyone access in the file permissions (and re-check the "grant rename" box). Then reset the file permissions (which will apply them to all the files and subfolders in the share).
Then move to the Network Access tab, and disable everyone and anonymous access there. Then either set the group permissions for the AGTest user's group (likely users) to read/write, or give the AGTest read/write access. If you intend to have lots of users access the share, then it is simpler to use group access (and put the individual accounts in appropriate groups).
To have access, users need to have both network access and file access. In many (IMO almost all) situations, it is better to manage share-level access using only Network Access, and leave file access set to allow everyone read/write. That is administratively simpler.
One aspect here is that users with write access can change the file permissions from their PCs, but changing network permissions requires admin access to the NAS. So you do choose to restrict access using the file access tab, you also need to restrict access on the network access tab.
One exception to using only network access for management would be if you intend to allow some users ssh access to the NAS, and you need to restrict their access when they are using ssh.
The other consideration here is that changing file access on an existing share does not change the permissions for existing files and folders in the share, you have to do the permissions reset for that. So if you will be adding users or groups along the way, StephenB 's method of using nertwork permissions also makes that easier, as no reset is required (and can be forgotten). If the only protocol you are using for file access is SMB, then it all works just fine. If you need to add NFS, then that complicates things a bit.
Edited Several Times! As I had forgotten to check "Folder Owner" and "Folder Group" in the File Access Menu
I cannot Connect the share via "Map Metwork Drive", Windows requires an email address and password and when I enter "AG" and "test" I get asked again for the User/Pass and get a pop up saying that the folder already exists. However no folder appears.
C:\net useShows no shares in existance.
If however I create the Netword drive by using:
C:\Users\AndrewJSGebhardt>net use t: \\172.16.105.196\Scan /user:AG testI then created a brand new share called "Test", dumped 20Mb of files in there and ONLY changed Network Access to "admin" and "AG"
However via Windows I cannot get access to the whole share. I can only connect via command line. When I connect via command line everything works seemingly fine.Actually, using command line is 100 times better than File Manager, just set all the family shares in minutes.
Thank you for the help!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
