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.
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.
- SMB was always enabled on the NAS. SMB direct was enabled on the Windows machines. SMB 1.0 was *not* enabled on the Windows machines before I stumbled on it as a solution.
For shares on the NAS that were accessible by Anonymous (my use case #1 in the OP), they were always functioning as I expected (that is, accessible without a user needing credentials). I don't think I reported any incidents where access to shares occurred where the user didn't have access rights. My problem was always the reverse; an ability for a credentialed user to access a shared that the user should have had permission to access.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
