NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Accessing shares with multiple users
Hey all, I am at my wits' end. I have had my RN 516 for a long time and never had any problems accessing shares that I noted; however, in going over some long pending maintenance tasks, I realized t...
Success!!!!!!
The final piece of the puzzle was in Windows Features, of all things. Once I enabled SMB 1.0 / CIFS File Sharing Support, everything worked. Why I was able to access shares without this enabled, who knows, but I definitely have proper permission-based accees!
Thank you rn_enthusiast and StephenB for your help!
To anyone else reading this thread: I am marking this post with the missing Windows Feature as the solution, but please read rn_enthusiast 's post above, as that took care of one of the other issues (involving a mapped drive) as well.
Hi reseune
You should use the Network permissions (i.e share permissions) rather than file permissions to configure this. There is nothing wrong with file permissions but it is FAR easier to control and setup Share permissions when it comes to the ReadyNAS, mainly because the file permissions UI is bad.
Reset permissions on the share to wipe all file based permissions and then work with Network (share) permissions instead. What you are trying to accomplish is absolutely possible and should be straight forward... but not from the same PC. Keep this in mind. Windows does not allow you to access the same network resource with multiple different usernames, from the same PC/user. I assume this isn't your intended use case either, but it can really mess with you when testing it and Windows can be stubborn when it comes to caching these things.
Windows credentials manager (in the PC's control panel) are a good way to manage this but they can be super annoying if they cache the wrong thing. I actually use Windows credentials manager to force my PC to always use a certain set of credentials for the NAS. My wife's PC is setup the same way, but for her user.
I would suggest you do as follows:
1. Reset file permissions on the share, from the NAS.
2. Configure your network/share permissions as you want them, on the NAS.
3. Delete all cached shares on your PC. Click on the start menu and search for "cmd". It will suggest the command prompt for you, open this up. In the command prompt box, type: net use * /d
4. Nuke everything under the Windows Credentials manager, in the control panel on the PC (Control Panel > User Accounts > Credential Manager > Windows Credentials).
5. Reboot the PC.
6. Map a new network drive in Windows, for a NAS share, using the credentials of the user you have setup for yourself, on the NAS. Does that work?
Remember, Windows does not allow you to use multiple username for the same shared network resource. In that instance, you will see an error prompt along the lines of: "Multiple connections to a server or shared resource by the same user, using more than one username, is not allowed.".
One NAS user per one PC, in your household.
Success!!!!!!
The final piece of the puzzle was in Windows Features, of all things. Once I enabled SMB 1.0 / CIFS File Sharing Support, everything worked. Why I was able to access shares without this enabled, who knows, but I definitely have proper permission-based accees!
Thank you rn_enthusiast and StephenB for your help!
To anyone else reading this thread: I am marking this post with the missing Windows Feature as the solution, but please read rn_enthusiast 's post above, as that took care of one of the other issues (involving a mapped drive) as well.
reseune wrote:
Why I was able to access shares without this enabled, who knows,
It probably is worth figuring out.
Most likely is that you've enabled another sharing protocol on the NAS that the PC was able to use - and that sharing protocol had more permissive access controls.
For instance, NFS might have been enabled on the PC (also in "turn windows features on or off"), and also enabled on the NAS shares.
StephenB wrote:
reseune wrote:Why I was able to access shares without this enabled, who knows,
It probably is worth figuring out.
Most likely is that you've enabled another sharing protocol on the NAS that the PC was able to use - and that sharing protocol had more permissive access controls.
For instance, NFS might have been enabled on the PC (also in "turn windows features on or off"), and also enabled on the NAS shares.
All of my shares are SMB, most only SMB. One share (the Home folder) is also NFS. Two media shares are also DLNA. The rest were only SMB with different permissions, some single user, some Admin only, some for Everyone, and one Anonymous.
Before I switched SMB 1.0/CIFS File Sharing Support on, all of my devices had Services for NFS and SMB Direct enabled. As I mentioned above, enabling SMB 1.0/CIFS File Sharing Support resolved my issue.
reseune wrote:
Before I switched SMB 1.0/CIFS File Sharing Support on, all of my devices had Services for NFS and SMB Direct enabled. As I mentioned above, enabling SMB 1.0/CIFS File Sharing Support resolved my issue.
I might be misunderstanding your posts, but it sounded to me like folks who didn't have permission to access the shares (or files) were able to access them anyway if SMB 1.0 wasn't enabled.
If I'm understanding that correctly, then it would be a big security flaw, since people could circumvent the access controls by simply turning the protocol off.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
