I had a similar problem about a year ago at a client (inherited it actually). 
Previous guy had tried to fix it (I saw his save files and what-not) and let it 
go. By the time I got there the tombstones had expired. The whole thing got 
very nasty.

In this particular case I would first address the connectivity problems (5721, 
5732, 5805, 1645) to get that stable, THEN go after the repl issue.

From: Coleman, Hunter 
Sent: Thursday, August 01, 2013 9:21 AM
To: [email protected] 
Subject: RE: [NTSysADM] DCs not in-sync

The 1988 event ID points to lingering objects in one of your DCs. See 
http://technet.microsoft.com/en-us/library/cc949134(v=WS.10).aspx

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Thozama Nonxuba
Sent: Thursday, August 1, 2013 7:26 AM
To: [email protected]
Subject: Re: [NTSysADM] DCs not in-sync

 

I can see the following errors:

On 2012DC1 

Netlogon errors 5721 listing 2008R2DC1

 

On 2008R2DC1 -System Log

NETLOGON error 5723 , 5805

Microsoft-Windows-Kerberos-Key-Distribution-Center - Warning 29

 

-Directory Service Log Errors 

1988  Replication

1645 DS RPC Client

 

On 2008R2DC2

System Log Error about the service: The WinHTTP Web Proxy Auto-Discovery 
Service service depends on the DHCP Client service which failed to start 
because of the following error: 

I don't think the above error is relevant

 

 

2008R2DC2 and 2012DC1  sync with no problems . 



 

On Thu, Aug 1, 2013 at 2:20 PM, Rick Berry <[email protected]> wrote:

Are there any specific Event IDs that you’re seeing related to replication or 
errors in the Event Logs?  If one of your 2008 DCs is sitting in the same room 
as the other and they’re not talking, you should have some errors listed in the 
logs.  First one I’d look at is under Applications and Services -> Directory 
Service.

 

Dcdiag also would provide additional clues.

 

 

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Thozama Nonxuba
Sent: Thursday, August 01, 2013 7:24 AM
To: [email protected]
Subject: [NTSysADM] DCs not in-sync

 

Hi

I have 3 DC's. 2x2008R2 and 2012. The 2012 is at our remote office. One of the 
2008R2 DC's will not sync with the others no matter what I do. I have tried 
repadmin and other commands. It's the oldest of the 3 DC's so my exchange 2003 
goes there first before the others.

It's starting to be a big hassle when creating any AD objects.as this DC12008R2 
is not playing nice with the other kids. What else can I try to bring DC12008R2 
in line?

 

TIA

 

Reply via email to