NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NAS logs says window user connects successfully, but windows says they dont have permission
We have a ReadyNAS 4220, which we have synced our accounts from our AD server to. We have a user that can't access the shared folders on the NAS. We can connect to the root of the NAS on her account ...
HappyBovine wrote:
We have a ReadyNAS 4220, which we have synced our accounts from our AD server to. We have a user that can't access the shared folders on the NAS. We can connect to the root of the NAS on her account with no issue, but trying to access the shared folders results in a windows error saying "windows cannot access \\[nas name]\[folder name]. I have assigned this user to have RW permission to this folder on the NAS.
Just to clarify
- can the user access their home folder?
- are there any shared folders they can access?
StephenBthis user can connect to the root folder on the NAS, but any of the folders under that give a permission error. However we only gave her access to one of these folders, so this is expected behaviour for all the other folders.
Her home directory is not on this NAS, as this is only a secondary storage location on our network, only used by some users.
HappyBovine wrote:
StephenBthis user can connect to the root folder on the NAS, but any of the folders under that give a permission error. However we only gave her access to one of these folders, so this is expected behaviour for all the other folders.
Did you try resetting the file permissions on that share? That will recursively re-apply the permission settings to every file/folder in the share.
StephenB I just tried that now, and we are still getting the same error.
AD access is not something I've done, but it looks to me like something is wrong on the computer end, not the NAS. I see no reason "desktop.ini" should be involved. Have you compared the messages for this user to another that has proper access?
ReadyNAS (and other Linux based systems) sometimes have issues with credential passed from a Windows host in a non-AD configuration. It often comes up when the NAS user name is the same as in Windows but the password is not. I would think that issue wouldn't happen in AD, but it could be related.
You may get more information, or even a solution, if you use a command prompt and NET USE to connect to the NAS share. You may need to issue a NET USE * /DELETE first to clear out the previous failed attempt. That'll also de-activate any other mapped drives on other servers the user may have, so you'll have to set them up again.
On my own PC's I have a batch file that maps all my shares using NET USE because I was running into the issue I mentioned above. That could be a non-elegant solution here, too.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
