• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2439
  • Last Modified:

Active Directory not syncing between two domain controllers

I have an issue with Active Directory.  I have two domain controllers, both running Server2012R2.  They were added to the domain, but it problems before they were added.  I had to manually remove a domain controller, and now have been getting the following errors showing up in the logs.  I need help Please, if anyone knows a direction to start.

Error-1:
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "0000208D: NameErr: DSID-03100238, problem 2001 (NO_OBJECT), data 0, best match of:
      'CN=SUSDC,CN=Servers,CN=SUS,CN=Sites,CN=Configuration,DC=XXXTOR,DC=local'". The event data contains the error.

Error-2:
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
 
Directory partition:
CN=Configuration,DC=XXXTOR,DC=local
 
There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.
 
User Action
Perform one of the following actions:
- Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.
- Add a Connection object to a directory service that contains the directory partition in this site from a directory service that contains the same directory partition in another site.
 

Error-3:
The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.
 
Sites:
CN=SNO,CN=Sites,CN=Configuration,DC=XXXTOR,DC=local
 
 
 Error-4:
 
 During the past 4.17 hours there have been 338 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites.  The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is 20000000 bytes.  The current maximum size is 20000000 bytes.  To set a different maximum size, create the above registry value and set the desired maximum size in bytes.
0
scormier1
Asked:
scormier1
  • 5
  • 4
1 Solution
 
Netman66Commented:
It seems your SNO site is not reachable according to AD.  

You may also have that bad DC still hanging around in AD too.

Make sure you can reach your SNO site - check in AD Sites and Services to be certain you have the right subnet associated with that site.

As for cleaning up AD, when deleting the computer account in AD it should be automatic.  However, have a read and see what got missed.

http://technet.microsoft.com/en-us//library/cc816907(v=ws.10).aspx
0
 
scormier1Author Commented:
I think I am gaining on it, but can't seem to identify why I am getting this error from the DNS service.

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.
0
 
Netman66Commented:
How many servers are running DNS?  Do you know what one had the first DNS service installed?

Is this a single forest and domain?
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
scormier1Author Commented:
Two DNS servers one at each site, the original is now gone due to hardware failure, but this is a single forest.  I am about to add another domain controller for a third site, but need to iron out the problems prior to creation.
0
 
Netman66Commented:
Can you run the following?

dcdiag /v > c:\dcdiag.txt

and post it?  If you are concerned about privacy, email me the file at my alias here at gmail.
0
 
scormier1Author Commented:
Please send email address.
0
 
Netman66Commented:
My username at gmail.
0
 
scormier1Author Commented:
I've requested that this question be deleted for the following reason:

None of the answers were correct.
0
 
scormier1Author Commented:
This solution was just part of the actual answer, but netman66 provided the guideline needed to get things fixed.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now