NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OOM-9
Jan 07, 2012NETGEAR Expert
Domain Join Issue - Information
I have found some helpful information for people that have issues joining the domain. The points to check when configuring the ReadyNAS to join the domain, and an additional option with logs to see wh...
smokinokie
Jun 13, 2013Star
After fighting with this for the past two days, I finally have my answer.
I have a ReadyNas316, yours may differ but I hope this works for you as well.
1. Update your firmware. The new 6.0.7 version has to be downloaded and applied manually at the time of this writing. I'm not sure what units this will work on.
2. Make sure your DNS and Time are configured correctly. Make sure Time has synced with the NTP server. You can't be more than a minute out of time with your domain controller. The DNS server you need to point to is your internal DNS server. Make sure DNS resolves both ways. You can ping the domain controller by it's FQDN. ping server.company.local where company.local is your domain. The domain controller can ping the NAS by it's FQDN. If this doesn't work, you won't be able to join the domain.
3.The following settings were used to join to my domain.
Netbios name- if your domain is company.local, your netbios name is company.
FQDN- If your domain is company.local, you will enter company.local
Organicational Unit- Leave blank. After the join, the domain controller placed the NAS in the \Computers organizatinal unit, I then moved it to where I wanted it
Administrator name- I found this to be case sensitive. Administrator vs. administrator
Directory Server Address- This is the IP address of your main domain controller.
I hope this helps. I was on the verge of sending my box back for a refund if I couldn't get this to work.
I have a ReadyNas316, yours may differ but I hope this works for you as well.
1. Update your firmware. The new 6.0.7 version has to be downloaded and applied manually at the time of this writing. I'm not sure what units this will work on.
2. Make sure your DNS and Time are configured correctly. Make sure Time has synced with the NTP server. You can't be more than a minute out of time with your domain controller. The DNS server you need to point to is your internal DNS server. Make sure DNS resolves both ways. You can ping the domain controller by it's FQDN. ping server.company.local where company.local is your domain. The domain controller can ping the NAS by it's FQDN. If this doesn't work, you won't be able to join the domain.
3.The following settings were used to join to my domain.
Netbios name- if your domain is company.local, your netbios name is company.
FQDN- If your domain is company.local, you will enter company.local
Organicational Unit- Leave blank. After the join, the domain controller placed the NAS in the \Computers organizatinal unit, I then moved it to where I wanted it
Administrator name- I found this to be case sensitive. Administrator vs. administrator
Directory Server Address- This is the IP address of your main domain controller.
I hope this helps. I was on the verge of sending my box back for a refund if I couldn't get this to work.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!