Windows 10 Permission Restriction

Question

Hello All.&nbsp;I have a ReadyNAS 102 setup, it has 5 shares. &nbsp;2 out of the 5 are open to anonymous access (basic music shares, etc..). &nbsp;The other 3 are restricted to users I created in the ReadyNAS user setup. &nbsp;All shares are SMB and AFP accessible.&nbsp;If I access the drives via my Linux systems (confirmed using SMB) or Windows 7 systems, it works as expected. &nbsp;It prompts me for a login and password, I enter the credentials setup in the ReadyNAS and it logs me in. &nbsp;So I know the drive and accounts are setup properly.&nbsp;However, from my Windows 10 machines it continues to tell me:&nbsp;[UNCPatch] is not accessible. &nbsp;You might not have permissions to use this network resource. &nbsp;Contact the administrator of this server to find out if you have access permissions.&nbsp;If I go back into the ReadyNAS setup and configure the shares to be anonymous, it works fine. &nbsp;It seems that my Windows 10 setup cannot authenticate against the ReadyNAS credentials.&nbsp;Below is a bulleted list of changes I've tried already, none of which helped:&nbsp;* Checking Credential Manager (Windows 10) - no accounts existed to the NAS* Tried adding&nbsp;to the Credential Manager, no success. &nbsp;But even if this worked, it has my system set to one account (two if I do IP and DNS). &nbsp;The point of the credentials is each user has their own login and folder to use and the login to the Windows 10 system is the same for all (generic login).* Multiple regedits on techforums (specifically around enabling cross-authentication, anonymous browsing, discovery, etc..)* Having the workgroup&nbsp;name in&nbsp;SMB setup (ReadyNAS) match the&nbsp;workgroup name of the PC* Disabling all firewalls, anti-viruses, etc..* Clearing all cached sessions (net use * /d and klist purge)* I've tried credential login with NASNAME\login, IP\login, and no domain/system with just the login&nbsp;Most articles I've read are issues accessing the shares at any capacity, most of which resulted in insufficient permissions being setup. &nbsp;Since it works on every system but Windows 10, I know the permissions are set right.&nbsp;The end result of my setup is to have 2 public shares (resources like music, software, etc..) and 3 private shares for each user (3 accounts total). &nbsp;I would have to imagine there is a setting for Windows 10 to do simple SMB access by trusting the device and credentials (like Linux), but I can't find it.&nbsp;Any help is appreciated.&nbsp;

StephenB · Answer

addicted2code wrote:
The point of the credentials is each user has their own login and folder to use and the login to the Windows 10 system is the same for all (generic login).
&nbsp;&nbsp;

That may be&nbsp;your&nbsp;goal, but that is not the way Windows works. &nbsp;It can only use two credentials for each network resource at a time (one using the name, one using the IP address). &nbsp;It doesn't matter if you use the credential manager or not. &nbsp;If you want different NAS accounts for each user, then you need to have a different windows login for each one.&nbsp;

addicted2code · Answer

That may be your goal, but that is not the way Windows works.  It can only use two credentials for each network resource at a time (one using the name, one using the IP address). Thanks for the feedback. &nbsp;I undertand credential manager is limited to two; I don't necessarily need Windows to remember the credentials (and actually don't want it to), I just want it to prompt me and validate against the NAS. &nbsp;I've seen this in enterprise networks and it works fine on Windows 7 and Linux terminals.

StephenB · Answer

addicted2code wrote: Thanks for the feedback. &nbsp;I undertand credential manager is limited to two;
It's not just the credential manager, it is windows itself. &nbsp;
&nbsp;
For instance, if you open CMD and enter
&nbsp;
C:\&gt; net use * /delete
C:\&gt; net use y: \nasipaddress	estaccount /user:testaccount testpassword
C:\&gt; net use z: \nasipaddress\admin /user:admin adminpasswordSystem error 1219 has occurred.
&nbsp;
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
&nbsp;
The credential manager is not involved - user/password are explicitly provided in the above commands. &nbsp;If you have an open connection to the NAS that uses username X, then Windows won't let you open a second connection to the NAS that uses username Y.&nbsp;
&nbsp;
And Windows doesn't free the connection right away when you exit the file explorer window either. &nbsp;So when user X finishes, user Y often ends up with X's connection logon&nbsp;unless X logs out.
&nbsp;
So I think you will need to give up on the single shared logon on the Windows PC to get what you want.

addicted2code · Answer

Understood, thank you. &nbsp;Regardless of trying to use multiple logins or one through a single Windows login; the original issue itself of even trying to access the share still doesn't work (regardless of a stored&nbsp;session or not). &nbsp;But only on Windows 10. &nbsp;Any thoughts on what I can look into for that?

BrianL2 · Answer

Hi addicted2code,

&nbsp;

Was the Win10 PC on the same workgroup name? After executing the netuse command in CMD, you have to wait at least a minute or two before attempting to access the restricted ReadyNAS shares using one of the users. Also rebooting the said PC will help.

&nbsp;

Kind regards,

&nbsp;

BrianL
 NETGEAR Community Team

Forum Discussion

Windows 10 Permission Restriction

9 Replies

Related Content

Windows permission issues. windows / linux share

Permissions Windows 10 RTM

RESTRICTION HORAIRE

Restrict DHCP?

RAX36S Guest Network port restrictions

NETGEAR Academy

ProSupport for Business