Permission problems with Windows 10 Pro - ReadyNAS 2120 v2 - Office 365

Question

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 match the one used in the PC (login both PIN and Password). Even set as "Anonymous" I am unable to overwrite files, and am asked to rename files on each save.&nbsp;I do not mind creating separate users for each person but I tried that and failed.&nbsp;Please imagine we are starting with a blank canvass, do I need to delete any Credentials in Windows first?NAS Model: ReadyNAS 2120 v2&nbsp;Firmware: 6.10.3Windows 10 Pro version 20H2OS Build 19042.685Thanks.Andrew.

StephenB · Answer

It sounds like you are using Microsoft accounts, and not local accounts. I don't think you can get Microsoft logins to work.&nbsp; But you can specify different user credentials for the NAS in the windows credential manager.
&nbsp;
It makes sense to start by deleting any credentials that are already in the windows credential manager.&nbsp;
&nbsp;
After that, try creating a single user account in the NAS.&nbsp; The user account shouldn't match the name of any of the PCs accessing the NAS, and it also can't match any share name.
&nbsp;
Then you can test access using that account using CMD in the windows system:
net use * /delete /y
net use t: \nas-name\sharename /user:username userpassword
using the real nas-name, user name, and user password (and of course a real share).&nbsp; Be careful on the typing - particularly the two slash directions.
&nbsp;
The first command terminates any open SMB sessions in the PC; the second attempts to map the share to drive letter T.
&nbsp;
Once you've confirmed that works, you can enter a windows credential in the Windows credential manager for the NAS (specifying that username and (optionally) the password).
&nbsp;
Note you can use a single (shared) NAS account on all the PCs if you like (though that assumes that you don't need the private folder feature, and also that you don't need to restrict access to some shares).

AJSG1969 · Answer

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.

StephenB · Answer

Start by allowing everyone access in the file permissions (and re-check the "grant rename" box).&nbsp; Then reset the file permissions (which will apply them to all the files and subfolders in the share).
&nbsp;
Then move to the Network Access tab, and disable everyone and anonymous access there.&nbsp; Then either set the group permissions for the AGTest user's group (likely users) to read/write, or give the AGTest read/write access.&nbsp; 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).
&nbsp;
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.&nbsp; That is administratively simpler.&nbsp;
&nbsp;
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.&nbsp; So you do choose to restrict access using the file access tab, you also need to restrict access on the network access tab.&nbsp;
&nbsp;
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.
&nbsp;
&nbsp;

Sandshark · Answer

The other consideration here is that changing file access on an existing share does not change the permissions&nbsp;for existing files and folders in the share, you have to do the permissions reset for that.&nbsp; So if you will be adding users or groups along the way,&nbsp;StephenB&nbsp;'s method of using nertwork permissions also makes that easier, as no reset is required (and can be forgotten).&nbsp; If the only protocol you are using for file access is SMB, then it all works just fine.&nbsp; If you need to add NFS, then that complicates things a bit.

AJSG1969 · Answer

Edited Several Times! As I had forgotten to check "Folder Owner" and "Folder Group" in the File Access Menu&nbsp;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:
et useShows no shares in existance.If however I create the Netword drive by using:C:\Users\AndrewJSGebhardt&gt;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.

Forum Discussion

Permission problems with Windows 10 Pro - ReadyNAS 2120 v2 - Office 365

9 Replies

Related Content

RN314 permissions local users permissions problem

Problems downloading make to ReadyNAS RN 212

NAS 516 Permission Problem

allow permission readynas folder torrent

ReadyNAS RN104 permissions issue

NETGEAR Academy

ProSupport for Business