The Views Expressed Below Do not in any way reflect Internal Doctorine or Official Statements of Netgear Inc. These are just my notes - Use at your own Risk.
THIS ARTCILE APPLIES TO READYNAS 4.2.x INTEL UNITS and 4.1.x SPARC UNITS
The Domain Controller (DC) should also be the DNS. If not adjust accordingly.
You need to know the domain name and the netbios name of the domain.
For example here its:
Domain Name: netgear.com
Netbios Name: NETGEAR
* To check Netbios name of anything go to "cmd" and type "nbtstat -a 192.168.1.10" where 192.168.1.10 is the IP of a pretend DC controller. If on
1) Make sure Clock on the NAS points to the DC and same timezone as the DC
2) Make sure the IP of the NAS is static and not DHCP
3) Without 2 this wont work, Make sure DNS is pointing to the DC with the DCs IP and have the correct DOMAIN name there (this should be identical to the DOMAIN name used in step 5)
with that said make sure the DC is also a DNS server
4) Security Mode Tab -> Domain Check -> Dropdown to ADS (Active Directory), The other option is Domain and its for old Win2K server.
5) On those settings - Set the DOMAIN name (this should be identical to the DOMAIN name used in step 3), the NETBIOS name of the domain, and the IP of the DC(instead of having it automatically look for it). Also put the admin username and password there of the domain to join it appropriately.
6) Hit Apply to join
If have troubles (try these steps and repead from step 4):
*Try Reenabling CIFS
*Make sure on latest firmware
*Try manually adding the READYNAS to the DNS server in its forward and reverse lookups
*OS Reinstall might help, but usually last restort
*Look at domain_join log to see whats wrong. This log only appears when the joining fails.