NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Active Directory issues after 6.5 upgrade
So after the the 6.5 update on our ReadyNAS 516 we are experiencing some weird issues with active directory permission to the NAS. Some users can get right on while other users it just keeps prompti...
Hi,
Try to load the latest RC Beta Firmware 6.5.1 and see if it resolves your AD issues. If you're hesitant, continue to work with our support team.
Kind regards,
BrianL
NETGEAR
It seems I'm facing similar problems, but I have no user able to enter into the shared drives and continuously ask for credentials.
Doing some test, I've locally (ssh session in the ReadyNAS 314) simulated the connection by using smbclient and I was able to log in with no problem using remote AD authentication (password Ok, Session Ok) and enter into the shared folder BUT unable to do any action like 'ls', as it raises "NT_STATUS_ACCESS_DENIED". I've raised the log level but no significative message that can give me any clue of "who" is denying me access to list or do any action with the folder. In any case I've tried changing permissions to 777 and so, but the same result. It should be something related to smbd, nmbd or winbind...may be.
Now I'm doing a full backup in a secondary storage USB disk and I will try to restore config backup I did when upgrading to 6.5.
So we have two domain controllers. One is Microsoft Server 2012 and the other is a 2003 server. No matter which I point to I still get the same issues. So I decided to test something.
We have a Samba4 test domain controller on an Ubuntu server. I pointed the NAS authentication to that active directory and there were no issues. The computers that were on that test domain were all able to connect to the NAS with no problems. But as soon as I connect back to either of the Microsoft domain controllers the problems return.
Hi fwdnetad,
Were the groups and users properly imported or remained after the Firmware update? Also, send me a PM together with the device ads log and systemd-journal log.
Kind regards,
BrianL
NETGEAR Community TeamI will send that PM to you tomorrow when I get back in the office.
I tried enabling the "do not cache accounts locally" option and I was then able to access the shared with any user. Though using this method the permissions on the folders are messed up. If I look at the security tab in the folder properties all the usernames now read "32982 (Unix User\32982)". Of course the number is differnet with each user.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
