NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Creating a folder with restricted access
Hello everyone from a relative NetGear newbie. I have an RN104, which is fitted with 4 x 3Tb WD RED drives, configured as one large RAID5 volume. It has firmware version 6.4.2. The device is...
Many thanks everyone for your help!
Clearly the issue lies at the Windows client end, rather than the RN104.
By using the 'Stored Usernames and Passwords' list in Windows 10 (C:\Windows\System32\rundll32.exe keymgr.dll, KRShowKeyMgr), I've managed to set the correct level of access on the 'Restricted' share I'd set up on NELLY.
I think this issue is now resolved.
Thanks again :smileyhappy:
James
Hi jpm102,
First, I hope you an external backup of your data, "10 years of recording", that's definitely worth having a backup on a USB HDD :)
About the permissions, there are two approaches, you can either set the permissions on separate shares, or set permissions on seperate folders inside the same share.
The first one is definitely easier, and I'd use the second one only if you have a genuine reason to not the use the first one.
For share permissions ("Network Access"): http://kb.netgear.com/app/answers/detail/a_id/26453
For sub-folder permissions: http://kb.netgear.com/app/answers/detail/a_id/26051
If you set up your permissions on the share, you shouldn't use the file access permissions ("File Access") unless you know what you're doing, you'll surely end up with permissions issues.
So I'd advise you to have two shares, one for normal content, with Everyone/Anonymous access, another share for restricted content, only accessible for your user, and to use the "Reset permission" button under "File Access" to make you don't have wrong permissions set on the files. You already filter the access in Samba (Network access), no need to filter on the file level (unless you know what you're doing).
(I wish they'd remove that "File Access" tab from the GUI of the ReadyNAS. For most people, it's confusing. And it's not really useful, you can set advanced permission from the explorer anyway)
Hi jak0lantash,
Many thanks for your help. I do have the Media Center recordings backed-up on a couple of USB drives.
I'm still not having any success with this. This is what I've done:
Created a new user called Superuser and set their password to password
Created a brand new share called Restricted
Opened the settings window for the new share
Clicked the Network Access tab
I unticked READ/WRITE access for the Everyone user group
I ticked READ/WRITE access for Superuser. The only other user with any other access is the default Admin user, who also has read/write access
Clicked OK
I haven't opened the File Permissions tab at all.
When I open \\NELLY in Windows file explorer in Windows 10, the Restricted share appears. Clicking it brings up a window asking me to enter my network credentials. I enter Superuser and the password, but I just get an error message telling me that \\NELLY\Restricted is not accessible. You might not have permission to use this network resource...
It also states that: Multiple connections to a server or shared resource by the same user, using 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
I've also tried using nelly\Superuser as the username, which causes the domain to change to NELLY, but I still can't get access.
I'm still baffled... Any ideas?
Thanks,
James
Hi jpm102,
In addition to jak0lantash's suggestion, you may want to try this as well.
1. Reset the permission of the 'NELLY' share.
2. Run CMD (command prompt) and enter the command (net use /delete \\Nelly\NELLY) *without the parentheses
3. Access again the 'NELLY' share and it should prompt for a user credential.
4. Enter the 'Parents' login and your good to go.
Hope this helps!
Kind regards,
BrianL
NETGEAR Community Team
jpm102 wrote:Multiple connections to a server or shared resource by the same user, using 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
That's the problem! It's because Windows has really poor management of samba sessions.
Can you try to add your Superuser credentials into Manage Network Password, log out and log back in?
jpm102 wrote:
It also states that: Multiple connections to a server or shared resource by the same user, using 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
This is a windows policy (nothing that Netgear can do about it). But there is a trick that will work.
Windows treats the NAS name and the NAS IP address as two different machines, so you can use different credentials for them.
So you could continue to access the nas using \\nasname for the open shares - but use \\nasipaddress to access the locked-down parent share. You will want to be careful not to allow Windows to remember the parent password. Even then the kids might still be able to access the parent share (for instance if you forget to close the window when you are done, or if Windows somehow keeps the session open after you close the window).
One approach is to set up two different user accounts on the PC, and switch to the parent account when you want to access the parent share (or any other local files you want to prevent the kids from accessing). That has the advantage of ensuring that you don't accidently leave the parent share open. It also lets you add the parent share credentials ot the NAS (again using the IP address) in the windows credential manager - using the Windows parent account password to manage access.
StephenB wrote:
Windows somehow keeps the session open after you close the windowAs far as I know, closing the Explorer doesn't close the Samba session.
If the same PC is used, it's better to have two different user accounts on the PC (and more logical).
Alternatively, you can close all Explorer windows et destroy the samba session with a net use command (net use //blablabla /delete /y)
jak0lantash wrote:
Alternatively, you can close all Explorer windows et destroy the samba session with a net use command (net use //blablabla /delete /y)
Sure- a batch file that does net use * /delete would remove any sessions. But its easy to forget to run it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
