NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN214 Active Directory problems when the Domain Controller reboots
My Domain Controller will periodically reboot after pulling down Windows updates. When that happens the Readynas 214 will no longer allow AD authenticated users to log in. I have to reboot the RN21...
We use DNS to find your DCs... so if you have only 1 DNS server on DC2 and DC2 goes down, we will not be able to resolve the Domain... Set the NAS DNS to all available DNS servers for this to take place.
We require the NTP server to be set (which we set automatically), the NetBIOS name from the domain (example: NETGEAR), the Realm name (NETGEAR.COM), and a user account with domain join privileges to join the network.
ReadyNAS (via Samba) will randomly select the best DC for usage. If it selects DC1 and operates, and then DC1 goes down, it will jump to DC2 and stay there until DC2 goes down, at which point it will attempt to find a new one.
Fields like Directory Server Address are not recommended because they will prevent your ReadyNAS from hopping to the next available DC (essentially hard-coding your NAS to only talk to 1 DC). Don't use this.
Except this isn't working.
The readynas has both of my DNS servers for my two DC's configured in it.
the FQDN domain is cryptoknight.home
the Netbios is CRYPTOKNIGHT0
I fill those in, plus the administrator account CRYPTOKNIGHT0\administrator or just administrator in case it uses the NETBIOS name with the admin account name and the password.
And I get back an error message when I hit apply
Failed to disable/enable user
the ReadyNAS has registered itself in my AD, as it shows up with a computer account in the Computers OU, but I have no clue what user it's trying to enable/disable.
Glad I found this post.
I have the same issue with 3x ReadyNAS units in three seperate locations. 2x RN102 and 1x RN104, all running version 6.9.5
Each unit is configured to the Domain Controller in that physical location. If that domain controller is rebooted, the ReadyNAS unit will forever prompt for credentials until it is rebooted. It will not select another domain controller.
I've even tried changing the domain controller that the ReadyNAS points to, to just my FQDN of my domain and this just does the same.
At one time this used to work perfectly fine, but this functionality no longer works correctly in the recent months.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
