Hi All,
We went from a Domain Controller running on Server 2000 to a new Domain Controller running on new hardware on Server 2008 R2. Everything went well apart from our ReadyNAS which is an old device but still serves its purpose well for us. Ever since the DC change, it can no longer authenticate using Active Directory like it used to before the DC upgrade. The local admin account still works, however it's like it can't "talk" to the new Domain Controller.
Is it possible that because our ReadyNAS is so old it simply can't communicate with the new OS of the DC?
In the ReadyNAS web admin page, under Security, the Security mode is set to "Domain" which is unchanged. Under Authentication, "Inherit users from trusted domains" and "Automatically detect domain server for this network." are both checked, same as before. If I uncheck Automatically detect domain... and manually enter the IP address of the new DC, it fails to do anything. I'm not sure what to put under "Realm" but it is blank, same as before. Under domain the domain is listed correctly, Domain Administrator is set to "Administrator" (same as before) and the password field is blank (same as before).
Looking at error logs on the Domain Controller, there is a bunch of errors which I'll copy/paste below. Anyone have any ideas? Thanks!
Event 5805, NETLOGON: The session setup from the computer NAS-etc.. failed to authenticate. The following error occured: Access is denied.
and
Event 5722, NETLOGON: The session setup from the computer NAS-etc.. failed to authenticate. The name(s) of the account(s) referenced in the security database is NAS-etc.. The following error occurred: The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.
