I just purchase a western digital worldbook (white light NAS drive) and I keep getting this error message.
Failed to join domain! [ERROR:Join ADS failed]
I’ve looked all over the internet I one seems to have solved this issue. Even trying some of the things I found none of them addresses this issue. Any help from anyone.
I tried what you suggested and still I’am receiving the same error message. I’am about to junk this and move on. This should not be hard to do. I’ve worked directly with our server group and had them try everything I’ve found on the web and still no luck. I had domain admins try to get this NAS to be added to the domain…what else can I try. I see the NAS in active Directory because they added it…any more clues as to what’s taking place. Thanks for all the help.
I recently bought a 4TB WD NAS and I joined the AD without problems.
The strange problem I have now is the following: with the DC and the WD NAS just setting-up as a domain member, all is working fine but, after a NAS reboot, the login script of all users doesen’t run properly.
In my login script I make a check if a user is a member of a specific group, to map proper disk: with this problem the script can only execute the lines valid for all users but not the lines with a AD group check.
In the AD I can see the WD NAS with the Netbios Name as “localhost.localdomain” and it could be the problem.
I tried to put a static entry in DNS and in WINS DB, but the problem persist.
The (crazy) solution I found is to join the doman again from the WD NAS, and the script runs without problem.
At the moment, for this problem, I can’t turn off or reboot the WD NAS.
Please, someone of you tried to reboot the WD NAS after a domain join and get this problem?
Most likely the clock is messed up. I turned off ntp as suggested and set the time manually. Even after setting the clock, the time is still wrong. For me it kept setting off by about 2 hours. I set the time wrong by about 2 hours and the time was then correct. After that I was able to join the domain…
I have the same problem, (windows 2008 enterprise edition)
I installed all windows updates, I update the firmware of the Mybook world.
The domain functional level is 2003 - 2008,
I installed wins,
on the WD I left the netbiosname away or filled in with caps ( I tried all possibilities)
I’m absolutely sure about the domain admin name and password
The ntp service is enabled and in the time server field I filled in the domain name of my domain, the time is now exactly the same for both systems. I also tried with manual time settings.
what can be wrong? I hope anyone has an idea.
maybe the functional level to 2000 - 2003 - 2008 ?
Mine just joined a 2008 R2 domain first go. Functional level 2008. Just tried against 2003, that works fine too.
If the time is more than a couple of minutes different from the domain controller it will fail because of the time limit on the security certificate required for authentication against the AD.
If you have more than one DC, make sure you put in the one which resolves against the domain name, not one of the others.
For example, if you have two DCs. 192.168.10.100 and 192.168.10.200 and a domain called mydomain.local
Ping mydomain.local will return one of the two IP addresses above. In the domain controller IP field, put that address.
Did you have to change any domain policies to allow the NAS to authenticate against the DC?
I’m running a Windows 2008 R2 DC in 2008 mode. I can add the NAS to the domain and I can apply permissions to the shared folders based on AD users and groups but if I try and connect to the NAS from a Windows client or server I get an error stating ‘No process is on the other end of the pipe’. I can map drives using the local NAS accounts no problem.
I have added a static DNS entry for the NAS drive. I don’t have WINS installed on my domain so nothing to add there.