NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Not all domain accounts being refreshed (ReadyNAS 312, firmware 6.9.1)
Hi Everyone,
My actual model is the RN312 but I couldn't find it on that stupid pull down list!
I know there have been previous posts about problems with AD refreshing before but they don...
Thanks for your reply!
I have two NAS's a ReadyNAS 312 and a 102. My live NAS is the 312 running 6.9.1 and the 102 on 6.9.4 and both NAS's do not import the full collection of AD accounts and no, no weird characters in any AD names.
Another thing; on neither of NAS's does the 'refresh ADS accounts' work. It's greyed out.
I trying this fix on my 102 at the moment:-
- Set Authentication back to "local" not '"AD"
- Reboot device
- Once the device is restarted, SSH to it and :
systemctl stop winbind systemctl stop smb net cache flush rm -f /var/lib/samba/*.tdb rm -rf /var/cache/samba/* systemctl start smb systemctl start winbind
- Reboot the device
- Once the device is restarted, in the Web Admin page, set Authentication to ADS again (with the standard options, i.e. "do not cache ADS accounts" NOT ticked
- Restart the device
Although I'm struggling with the smb and winbind commands as they do not work. Possilby slightly different flavour of Linux so I'm experimenting...
Lot of water went down the Niagara falls since the 6.9.1 release almost one year ago on 22-NOV-2017. While I'm not aware of any ADS related entris in the release notes since, there were a bunchof security issues addressed since.
Trouble is that a very small number of ReadyNAS (same for Q and S brand) are integrated with an AD as a standalone server - ways below the critical mass to discover all potential issues. Any special chars used in the AD user names for example?
Thanks for your reply!
I have two NAS's a ReadyNAS 312 and a 102. My live NAS is the 312 running 6.9.1 and the 102 on 6.9.4 and both NAS's do not import the full collection of AD accounts and no, no weird characters in any AD names.
Another thing; on neither of NAS's does the 'refresh ADS accounts' work. It's greyed out.
I trying this fix on my 102 at the moment:-
- Set Authentication back to "local" not '"AD"
- Reboot device
- Once the device is restarted, SSH to it and :
systemctl stop winbind systemctl stop smb net cache flush rm -f /var/lib/samba/*.tdb rm -rf /var/cache/samba/* systemctl start smb systemctl start winbind
- Reboot the device
- Once the device is restarted, in the Web Admin page, set Authentication to ADS again (with the standard options, i.e. "do not cache ADS accounts" NOT ticked
- Restart the device
Although I'm struggling with the smb and winbind commands as they do not work. Possilby slightly different flavour of Linux so I'm experimenting...
Ok, so ran the commands from the previous fix. (Commands were completely fine I just hadn't su'd into Root. Duh!)
And after refreshing a couple of times all looks good. ALL Active Directory user accounts now imported.
I've just got to strap on a pair and do it to my live server. I note however that since you have to change the authentication to 'Local' obviously you have to re-assign the AD accounts back onto the shares.
I hope that has helped anybody else with the same issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
