tiger20005

Thanks cluberti but I have tried that as well In network config I have placed the public IP of Server A to be the main and only DNS server available but for some reason it still won't see it. I may have a larger problem than I think is going on and maybe that is a strict DNS issue. The servers at location A and B seem to communicate fine and I am also able to do replication to each other as well. I did the same type setup (child in current existing Domain-or something close to that wording) for C and it has been a pain since! I may need to call a specialist in for this one

We are running T1 lines via the local carrier (MCI at Location C and Verizon at location B and C). I can ping via DNS and IP to any server I want at this point and get a reply but for some reason the darn thing won't get a clue that it is suppose to be a server (AD is clueless right now). This leaves me able to log on to the new domain but not add any clients (due to the issue with AD). I seem to have any form of communication I need to get to the other servers except the fact that AD won't communicate with them. There are no firewall constraints as I opened them up at this point (for testing). There are no obvious signs why this is not working to me! When I take this server to site B or A I hook it up to the network and server A is like hi I see you and allows AD to open right up and let's you add computers and users. I maybe have an issue in DNS under Manage your server but I can't seem to figure it out. All the IP's that are on server A and B are in the correct configuration on C.

Sorry if I worded it wrong but what we have is a single domain and the first DC was setup at Location A while the other 2 sites (B and C) were setup at a later date (we transitioned from one domain name to another with the new servers). When I transitioned Server B I have had no problems getting it to communicate with Location A. In location C I do not have an issue with that server pinging A or B via the Public IP addresses or by DNS. I can also remote connect to A and B (which again is only bc I can communicate via IP no problems). The problem I have now is why Server C will not open AD unless I go manually tell it to connect to DC and use the name of itself. I can also connect to DC at the other locations A and B that way too. I want to be able to open AD without it spitting back that the Domain cannot be located. Locations A and B work exactly the way they are suppose to, it;s just this third one has been stubborn. I check the settings in Manage Your Server under DNS and all entries are there and correct (to my knowledge) and not liek they are blank. I even try to use the Location A's Public IP under DNS of this Loaction C server in order to communicate but it does not do so. If I physically take this Location C server down to Location A and plug into network everything is fine. This is all the same domain on all 3 and B and C are children to the parent A. Thank you to those who are helping, you don't knwo how much this is appreciated!!

When I promoted the DC I had it at Location A (only because for some reason I could never get it to reach location A from Location C). The promo went great and it pulled up the accounts, etc. When I take it back to location C it will not allow AD to pull up unless I do a Connect to DC and type in the name of the location C's server name. This then will pull up AD but I cannot connect join any PC;s to the new domain it runs. I even point the PC's DNS to the Location C internal IP (and the PC's I try to change over can ping the DC in Location C by DNS and IP). I have pointed the DC in Location C DNS to the public IP of the Location A server but still no luck. This was never a problem with Location B and I did it all the same way! I checked all settings under AD/DNS and they seem to be correct in all 3 locations.

Active Directory: The specified domain either does not exist or could not be contacted. Hi guys! I am having issues with AD on one of my domain controllers. When I attempt to open AD it gives me the following message: “Naming Information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online.” My setup: I support 3 separate locations and have a Domain Controller at each location. Location A has the first DC that was setup and then Location B has a second one that works great but when I setup Location C this is what I get (error message). I am able to ping all of the other DC’s from each one of them. We run an external DNS server via MCI (local carrier). Has anyone had a similar issue with a DC running AD that could give suggestions? Thanks in advance…