NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Samba share access permissions not making sense
I just noticed that access permissions for SMB shares on my ReadyNAS102 don't seem to be working. When I set up my RN102 sereval years ago I was a bit lazy and just set up all my shares as read/w...
Digsy wrote:
The CCTV share is the only share that I want to require a username and password for, but when specify this username in Network Access and I supply credentials for it when I try to connect, it doesn't work unless I use the command line.Windows won't accept my username and password as valid, but the command line will.
Obviously this is a Windows issue.
If you entered the credential in the Windows Credential Manager, then you shouldn't be needing to enter the username at all. If you also entered the password there, you shouldn't be needing to enter that either.
Are you entering \\nas-ip-address\sharename in the file explorer address bar to access the share?
One thing to keep in mind - Windows only allows one set of credentials per machine at a time. And if you first access the NAS w/o a credential, Windows will still use one - it defaults to using the Windows Login. You can clear that using the net use * /delete /y command. So perhaps just try that command, and then see if the file explorer will take your credential.
All my other shares are set to allow anonymous access, so I do not need to provide credentials to access them. I can map these shares or connect directly by typing the pathname into Explorer just fine.
The CCTV share is the only share that I want to require a username and password for, but when specify this username in Network Access and I supply credentials for it when I try to connect, it doesn't work unless I use the command line.Windows won't accept my username and password as valid, but the command line will.
Digsy wrote:
The CCTV share is the only share that I want to require a username and password for, but when specify this username in Network Access and I supply credentials for it when I try to connect, it doesn't work unless I use the command line.Windows won't accept my username and password as valid, but the command line will.
Obviously this is a Windows issue.
If you entered the credential in the Windows Credential Manager, then you shouldn't be needing to enter the username at all. If you also entered the password there, you shouldn't be needing to enter that either.
Are you entering \\nas-ip-address\sharename in the file explorer address bar to access the share?
One thing to keep in mind - Windows only allows one set of credentials per machine at a time. And if you first access the NAS w/o a credential, Windows will still use one - it defaults to using the Windows Login. You can clear that using the net use * /delete /y command. So perhaps just try that command, and then see if the file explorer will take your credential.
StephenB wrote:One thing to keep in mind - Windows only allows one set of credentials per machine at a time. And if you first access the NAS w/o a credential, Windows will still use one - it defaults to using the Windows Login. You can clear that using the net use * /delete /y command. So perhaps just try that command, and then see if the file explorer will take your credential.
Well, that'll be it, then!
I always have two shares mapped to my PC at boot up, so although anonymous, they will be using my Windows login credentials, and this will be stopping me from making a second ad hoc connection to my CCTV share.
If I unmap both shares then I can connect to my CCTV share using my CCTV master account withouth any issues.
This also explains why FTP and HTTP access works, because for the former it is the cameras making the connection, and for the latter it is my web browser - so neither associated to WIndows.
Thanks for bearing with me on this. Much appreciated. :)
Digsy wrote:
I always have two shares mapped to my PC at boot up, so although anonymous, they will be using my Windows login credentials, and this will be stopping me from making a second ad hoc connection to my CCTV share.
If I unmap both shares then I can connect to my CCTV share using my CCTV master account withouth any issues.
Great.
There is a potential workaround here. Windows treats the IP address and the hostname as two different machines. So if you are mapping the drives at bootup with the hostname, then you can still use the CCTV credential if you use the IP address. Or the other way around (use the IP address for ordinary access, and the hostname for the CCTV share).
Digsy wrote:I always have two shares mapped to my PC at boot up, so although anonymous, they will be using my Windows login credentials, and this will be stopping me from making a second ad hoc connection to my CCTV share.
Not at all - you can add more users to allow the access to the same shared folder. Unless I'm very wrong, having both authenticated and non-authenticated ("guest") access to the very same shared folder is possible.
Better or more professional approach is grouping users with the similar access rights into a group, and grant the access rights based on the group - not on the base of users. This does avoid all ACLs need to be rewritten on every change - what can be a tedious and slow job on large amounts of folders and files.
Be aware that newer Windows 10 builds do no longer allow using non-authenticated access - unless you are going to tweak it - because it's considered a security risk.
To allow non-authenticated access _and_ access to Windows systems already holding valid credentials already in use for more secured folders, add the read+write access for the implicit group "users". However I fear the ReadyNAS Web UI does not let us configure this correct set-up (working on generic SAMBA servers, on QNAP, on Synology, ...). That would be much better than workarounds using IP instead of the name.
schumaku wrote:
Digsy wrote:
I always have two shares mapped to my PC at boot up, so although anonymous, they will be using my Windows login credentials, and this will be stopping me from making a second ad hoc connection to my CCTV share.
Unless I'm very wrong, having both authenticated and non-authenticated ("guest") access to the very same shared folder is possible.
With Windows, you can only access the NAS IP-address or hostname with one set of credentials at a time.
Since he wasn't using the CCTV credential when he mapped the shares at bootup, that credential couldn't be used when he tried to access the CCTV share.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
