Because it took us forever to figure out how to get these setting right and we found the documentation confusing here is how we got our ReadyNas 3130 running OS 6.2.4 to talk to our AD. The main issue was with getting the Container OU format so that we wouldn't constantly get errors that the OU doesn't exist.
We had to convert OU=Servers,OU=Company,DC=domain,DC=internal to something the ReadyNAS could understand. We started out with leaving this field blank and the connection worked. However it created the ReadyNAS AD object in OU=Computers,DC=domain,DC=internal. It's a good starting point though to ensure all other fields are correct and there are no password problems etc and the object can be moved afterwards.
Access Type: Active Directory NetBIOS Domain Name: DOMAIN DNS Realm Name (FQDN): domain.internal Container OU:Company/Servers <-- doesn't require any DC strings - just the path from the root to where the Netgear AD object is located. Include Truested Domains: No (in our case) Administrator Name: DomainAdmin (case sensitive) Administrator Password: DomainPassword (case sensitive) Directory Server Address: 192.168.1.xxx or dc.domain.internal Do not cache ADS accounts locally: No (in our case)
Yes I did and no it didn't because it doesn't actually say what format the Container OU string needs to be. Doesn't say if it needs to start or end with a / or anything like that. So I hope my post will help others who have struggled with the lack of detail in the KB article.
