Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

An AD DC controller for the domain could not be contacted.

Posted on 2011-02-17
7
848 Views
Last Modified: 2012-05-11
This is error i get when trying to join the domain with a client.  This just started out of nowhere.

  An AD DC controller for the domain could not be contacted.    DNS was successfully queried for the SRV record.  The follow domain controllers were identified by the query

However no Domain Controllers could  be contacted.
0
Comment
Question by:Jimmy_MCSO
  • 6
7 Comments
 
LVL 10

Expert Comment

by:akhalighi
ID: 34916161
hmm.. any firewalls in the middle ? Is this happening on ONLY one client ? can you try another machine ?
0
 

Author Comment

by:Jimmy_MCSO
ID: 34916225
I shut firewall down, and it is happening on a win7 client and a win 2008 member server I am trying to join.  I also tried joining a win xp client, same results.  I ran netdiag and dcdiag verbose and looked at logs, and all the tests passed
0
 

Author Comment

by:Jimmy_MCSO
ID: 34916259
This is the error:

The query was for the SRV record for _ldap._tcp.dc._msdcs.local

The following domain controllers were identified by the query:
server1.local
data-server.local


However no domain controllers could be contacted.

Common causes of this error include:

- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 

Accepted Solution

by:
Jimmy_MCSO earned 0 total points
ID: 34916431
I found the issue.  It has to do with single label dns domains.  I will work on changing that.  I adopted a domain that was already configured as single label DNS
0
 

Author Comment

by:Jimmy_MCSO
ID: 34916477
It has to do with SingleLabelDNSDomain
0
 

Author Comment

by:Jimmy_MCSO
ID: 34916481
thanks
0
 

Author Closing Comment

by:Jimmy_MCSO
ID: 34949673
Thanks for the assistance.
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preface Having the need * to contact many different companies with different infrastructures * do remote maintenance in their network required us to implement a more flexible routing solution. As RAS, PPTP, L2TP and VPN Client connections are no…
Learn about cloud computing and its benefits for small business owners.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question