Re: Suddenly can not add computers to the Domain after server cras
- From: Ryan Hanisco <RyanHanisco@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 13 May 2007 17:55:00 -0700
Hi there,
This looks like a DNS problem as you'll run into this if the PDCe role
cannot be found. I would go through your DNS to pull all of the records
pointing to the removed DC. From there you should do a DCDIAG to look for
problems -- you may have to do a metadata cleanup to clear out records in the
AD pointing to the old DC.
You shoudl also stop and restart the netlogon service to re-register the srv
records for the servers. AT this point, pinging the domain by FQDN from the
workstation shoudl resolve the address of the PDCe.
From there you should be golden.--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
"YeahBut" wrote:
.
I should probably add that the servers are Windows 2003 Enterprise R2,
and this affects ANY client attemtping to join the domain, not just a
single client.
On Sun, 13 May 2007 19:15:16 -0400, YeahBut <YeahBut@xxxxxxxxxxx>
wrote:
Small network. Two domain controllers. Used to be 3, but one was
suddenly taken offline and the Operations Masters Roles had to be
seized by another DC.
Now I can't add any new machines to the domain. The error I get when
trying to join a new machine to the domain is:
-------------------------------------------------------------------------------------------
A Domain Controller for the domain mydomain.com could not be
contacted. DNS was successfully queried for the service location (SRV)
resource record used to locate a domain controller for domain
mydomain.com:
The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.com
The following domain controllers were identified by the query:
appserv.mydomain.com (Note: Operations Master)
server4.mydomain.com
Common causes of this error include:
- Host (A) records that map the name of the domain controller to its
IP addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the
network or are not running.
For information about correcting this problem, click Help.
---------------------------------------------------------------------------------------
The domain controllers are identified correctly. Both servers are DNS
servers, and the DNS entries for each are correct. I can ping both
servers by FQDN from the PC that is getting the error, so it's not a
name resolution issue. It's not a connectivity issue, as I can ping
everything by name or IP.
Any ideas? It must have something to do with the server that was taken
offline suddenly, but I did seize the roles to another DC. Any ideas?
- References:
- Prev by Date: Re: Problem
- Next by Date: DCDiag - The Security Account Manager failed a KDC request
- Previous by thread: Re: Suddenly can not add computers to the Domain after server crash
- Next by thread: DCDiag - The Security Account Manager failed a KDC request
- Index(es):
Relevant Pages
|
