Solved

Domain Controller Could not be Contacted

Posted on 2007-03-26
2
1,062 Views
Last Modified: 2012-06-21
I was having problems not being able to connect to my domain so I removed my pc from the doamin by telling it to use a workgroup instead. My though was that after a reboot I would rejoin the domain. but when I try to join I get the following error.

An Active Directory Domain Controller for the domain mydomain could not be contacted. Ensure that the domain name is tyhped correctly. If the name is correct, click Details for troubleshooting Information.

the details are as follows...

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The domain name mydomain might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain mydomain:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

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

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.0.1

- One or more of the following zones do not include delegation to its child zone:

mydomain
. (the root zone)

For information about correcting this problem, click Help.

I have replaced my domain name in the above text with "mydomain" and changed the DNS servers ip to 192.168.0.1 but you get the point. can I just create the SRV record for _ldap._tcp.dc._msdcs.mydomain and if so how. If not what do I do here.
0
Comment
Question by:dustinwk
[X]
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
2 Comments
 
LVL 12

Accepted Solution

by:
ShazbotOK earned 500 total points
ID: 18796161
Can this problem be duplicated on other PC's? (if yes you may have a corrupted WINS metadata entry on your WINS server)

Can that workstation ping the IP of the DC?

What is the HOST name returned when you run "NBTSTAT -a 192.168.0.1"? is that a matched netbios name to your DC?

If no try running "IPCONFIG /FLUSHDNS" if still failing you may want to check the local PC's HOST file (c:\windows\system32\drivers\etc\HOSTS) which you can open in notepad and verify that a bad entry has not been inserted into that file.

Lets start with that...
0
 

Author Comment

by:dustinwk
ID: 18796198
Ug! OK its working now I told it to join my domain again but this time instead of just DOMAIN i used DOMAIN.local and it worked. I dont know why this is cause I never have to do that and im pretty sure i didnt do it that way on this pc the first time. but its working now so thanks for the fast response. by the way this is windows vista and its been giving me hell since day one!
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

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

This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

734 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