hoping someone can give me an answer to this. Recently i have added a backup server for Active directory onto my network but the problem i am having is now i have the server working, i have installed server 2008 standard and done all the updates havent added active directory or anything but i have been trying to join our domain.
My problem now is that i have set all the IP settings and DNS settings i have pinged the main server and also checked ipconfig /all and checked that the DNS settings are right which they are but when i try to join the domain i get an error that the server cannot check the DNS settings are right on the main server.
I have tried uninstalling the NIC and reinstalling and also tried switching off the firewall but still cannot join the domain. The new server can see the main server under network but its showing a on a workgroup and not the domain. The new server can also access the internet with no problems just seems to be when i try to add it onto my Domain. I have also check under active directory and have created an account for the server and just called it WCB-DC02. Do i need to install the active directory role so that this will replicate from server 1 over to this DC02? i was waiting until the server had connected to the domain before doing this is that right?
"The following error occurred attempting to join the domain
An attempt to resolve the DNS name of a DC in the doamin being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. "
my main server is AD, DHCP, DNS, Print server, AV server, file server and i did have a 2nd server which would replicate active directory but it ran out of storage so i added this new server on and give it the same IP address as the old and also the same name as the old server which is off completley.
hope this helps in solving this problem really dont know what it is ive done wrong because all clients join the domain with no problems when i am doing a rebuild.
No youll need to do it on the exsisting dc - depending on whether your exsisting server is 32 0r 64 bit will depend on whether you can use the 2008 install disk or if you need to download the trial 32bit 2008 disk to get to the 32 bit adprep file.
so this needs to be run on my main server (server 2008 32bit standard) to allow for another server (server 2008 32bit standard) to be included as another domain controller all allow replication of the active directory? could this be the reason the server wont join the domain at the moment
I think this problem may be the fact that you had a second server before you installed the server 08. Did you do a meta clean up of the old server i.e removing all mention of it in sites and services and seizing all roles onto the remaining server. If you have not done this AD will be saying you can't join the domain as server2 name already exist in AD sort of speaking. I don't think you have to run adprep if you are just joining the domain with server 2008, yes if you want to make it a DC.
Last edited by jsnetman; 13th September 2010 at 08:41 PM.
Before even trying to get the newer server onto domain (and premote to a Domain Controller) if you configure as DHCP does it get allocated a correct IP address and ping the Domain Controller etc? If works OK, then manual configure a valid static IP address (a different one from that of the old server WCB-DC02)
Another issue I see is that you have named the new server the same as the old 2nd Domain Controller, and if you didn't correctly demote and remove that server settings still exist for it.
You could name the new server to a different name, say WCB-DC03. Reboot and try and add the server to the domain. Let this process create the computer account. If successful, the server will now be a member server.
You can then adprep to update the schema for Windows 2008 (if not already a windows 2008 domain already!) and to promote to an AD Domain Controller.
Did try to post last night but got locked out, and 15mins lock was still activated after 30mins+!!
that was it exactly i never properly demoted the previous server and yes i have called this one exactly the same and given it the same IP as the other server is no longer available on the network at all. I was reading that if i log onto the main server and delete the old server from active directory with it being server 2008 it should remove all info about the old server which i have done this morning but for some reason still get the same error message when trying to join the new one to the domain.
is there no way that i will be able to give this new serve the same details ie Name and IP address as the old server?
i tried the forcing removal of domain controller first thing this morning hoping that it would clean up any metadata but it still doesnt allow me to add the new server to the domain with the old servers name and ip.
It is a 2008 domain the old server had 2008 on it as well
i have used the adive that MYK-It and yourself have given me and read over the links for removeal of a domain controller the first two links would be great if the old server worked at all as i cannot switch it back on now with no respone i did a force removeal of the old dc rebooted the server checked that i could get an IP address from DHCP and then changed it to a static IP address but when i go to add the server (with no roles) onto the domain i am landed with the same message about DNS i also tried naming the server WCB-DC03 and changing the IP address to a different static value then adding onto the network but still get the same DNS message error
Last edited by Aaron; 14th September 2010 at 10:17 AM.
I have changed the name of the server to WCB-DC03 and given it a different IP address from the previous old server but i am still getting this "An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain." everytime i try to add it to the domain.
All info on previous server has been removed from sites and services and also all info in active directory Domain controllers so there shouldnt be any information on the previous server left (hopefully).