Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I get the following error.

An Active Directory Domain Controller for This Domain Could Not be Contacted

and...

I have working Internet. I have an Active Directory domain controller set up on the same subnet, but I thought I would set this up before without having an Active Directory domain controller.

What things should be checked?

share|improve this question
    
can you ping the domain controller from the new subnet, using the fully qualified domain name? have you opened relevant firewall ports on the ASA to allow the new subnet to talk to the old one.. ? Lepide –  Lepide Feb 29 '12 at 12:03
add comment

6 Answers

up vote 6 down vote accepted

It sounds like DNS resolution. If it's on the same subnet then it cannot be the firewall.

Can you ping this machine by both hostname and fully qualified domain name in both directions?

Well, if they are both using the same DNS server and that server is responding to the queries that is a good sign that the problem is not so severe.

If the machine cannot ping and you mentioned they are on the same subnet, check for an IP addreess conflict as well as check that there are no typos in the subnet, gateway, netmask, etc...

share|improve this answer
    
I can ping the IP of the DC. The FQDN can't be pinged on DC. They both share the same DNS server address 10.10.100.1. From the DC to the other machine, I can't ping the IP address. –  Noah Clark Aug 17 '09 at 15:53
    
Here is what I did: 1. Checked over manual settings. Didn't notice anything odd. 2. Set both machines to DHCP. 3. Rebooted. The non-DC machine has local only connection. 4. The only difference is the IP address between the two machines. One is 10.10.100.2 and the other is 10.10.100.3 –  Noah Clark Aug 17 '09 at 16:28
    
The non-DC machine now is online. I opened up IE and it popped online. I get the error when I go into the details: The error was: "DNS name does not exist." (error code 0x0000232B RCODE_NAME_ERROR) –  Noah Clark Aug 17 '09 at 16:38
    
see if you can manually add an a-record for the entries under the DNS zone. –  Nick O'Neil Aug 17 '09 at 17:32
    
Shouldn't I be able to add two windows 2008 machines to a domain without a AD DC? –  Noah Clark Aug 17 '09 at 18:07
show 1 more comment

I found this to be the problem I had:

"If the server is a domain controller, do you also use it for DNS because the DNS server IP address points to the router? Change it to the DC/DNS server. Active Directory relies on DNS, and you should run DNS on the server, not on the router. To get Internet access, configure the FORWARDER to the ISP's DNS server under the DNS server properties in the DNS management console."

From: A Domain Controller for the Domain XXX Could Not be Contacted

My lab desktop NIC was getting its DNS information from the router. I left the router to handle DHCP, but I manually entered the DNS IP address of my domain controller (which is also my DNS server). Since the domain controller has a forward to my router, I can still get Internet access.

With this done, the lab desktop was added to the domain without a problem.

share|improve this answer
add comment

Check that the time on the client is correct. Sound silly but this can stop the client for joing up with the domian.

share|improve this answer
add comment

I had the same problem.

PaulLcn is right about some comments he made regarding "If the server is a domain controller, do you also use it for DNS because the DNS server IP address points to the router? Change it to the DC/DNS server.Active directory relies on DNS".

However this what I did. On my domain controller (DC) its role is AD/DNS.

  1. On my DC I went into the IP address properties and manually configured the DNS settings. My 'Preferred DNS is 192.168.1.6'. This is the IP address of my DC. The 'Alternate DNS is 192.168.1.1'. This is the IP address of my default gateway (my cable router).

  2. On my laptop I went into the IP properties and manually configured the DNS settings. My 'Preferred DNS is 192.168.1.6'. This is the IP address of my DC. The 'Alternate DNS is 192.168.1.1'. This is the IP address of my default gateway (my cable router). Then I attempted to add my laptop to my domain and it worked with the right crodentials.

I was still able to access the Internet on my laptop and my DC. I did, however, go into DNS Manager to create my Lookup/Reverse Zones, this is for training purposes ONLY. But I didn't need to create a 'Conditional Forwarders' to access the Internet.

share|improve this answer
add comment
  • Check the obvious stuff first like netmasks/etc.
  • Flush the dns cache on both machines using ipconfig /flushdns.
  • Confirm that the DC has an FQDN set in it's system properties.
  • Check can the DC resolve it's own name to IP using nslookup; if not add a forward zone entry for it.
  • Check can the DC resolve it's own IP to name using nslookup; if not add a reverse zone entry for it.
share|improve this answer
add comment

Thanks I had a similar issue. I performed a ipconfig /flushdns on my client machine and was able to join the domain no problem.

share|improve this answer
    
Shouldn't this be an edit to the accepted answer? –  bmike Dec 5 '12 at 15:13
add comment

protected by MDMarra Nov 19 '12 at 15:21

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.