Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » Re:Suddenly can not add computers to the Domain after server crash
Re:Suddenly can not add computers to the Domain after server crash [message #393618] Wed, 17 February 2010 11:54
tr777ple tr777ple  is currently offline tr777ple tr777ple  United States
Messages: 2
Registered: February 2010
Junior Member
Make sure that this port is opened. This should hopefully fix your issue...at least it did mine.


Port Number: 389
TCP / UDP: UDP
Delivery: No
Protocol / Name: ldap
Port Description: Lightweight Directory Access Protocol. LDAP server's port, an adaptation of x.500 dir std. Through it, LDAP clients access central dir to retrieve, add, and modify info. Examples: Database for PKI systems. - Address book for mail & personnel progs. - Internet Directory Service that tracks users of collaborative apps (chat, video, audio, etc). Would track who is on-line, their IP, and data about user. Used by Win2000 Active Directory. SSL version at TCP 636. Security Concerns: Valuable source of user info used in attacks; excellent target for DOS attack.



YeahBut wrote:

Suddenly can not add computers to the Domain after server crash
13-May-07

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?

Previous Posts In This Thread:

On Sunday, May 13, 2007 7:15 PM
YeahBut wrote:

Suddenly can not add computers to the Domain after server crash
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?

On Sunday, May 13, 2007 8:08 PM
YeahBut wrote:

I should probably add that the servers are Windows 2003 Enterprise R2,and this
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.

wrote:

On Sunday, May 13, 2007 8:55 PM
RyanHanisc wrote:

Hi there,This looks like a DNS problem as you'll run into this if the PDCe
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:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Join Lists with LINQ - SharePoint 2010
http://www.eggheadcafe.com/tutorials/aspnet/b0c1cd0d-fe82-44 4e-a16e-7d3fb7d38eca/join-lists-with-linq--sh.aspx
Previous Topic:Entreprise trusted root authorithy certificates
Next Topic:NT 4 and Windows 2008 Upgrade - HELP!!
Goto Forum:
  


Current Time: Wed Jan 17 05:37:16 MST 2018

Total time taken to generate the page: 0.01998 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software