Domain controllers Not Syncronizing

  • Thread starter Thread starter Joel
  • Start date Start date
J

Joel

One of my domain controllers was getting an error in the
even log that talked of a JRNL_WRAP error, and suggested
running a not authoritive recovery by editing the
registry. I ran the recovery, and now my 2 domain
controllers do not sync, I do not get any File Replication
error messages, but when I make a change in AD Users and
Computers on one server the changes do not show up when I
run AD Users and computers on the other server.
 
Hi Joel

The journal wrap has occurred most likely because your DC's haven't been
replicating for some time. This indicates a problem with FRS replication.
Putting it in perspective, FRS replication depends on AD replication which
depends on name resolution and network connectivity.

What you've done is to tell one of the DC's that the information it has in
SYSVOL is no longer valid, to throw it away and to source the SYSVOL data
from another DC. The issue with this is that you haven't addressed to root
cause which caused it to fail in the first place. The fact that AD
replication is not working suggests a problem with name resolution or
network connectivity between the two DC's.

This may not be trivial to resolve given the brief history you've provided.
I'd suggest logging a case with Microsoft to get assistance. They're likely
to gather a decent amount of logging to build a picture of what's transpired
and you'll probably have to decide which of the two DC's has a good valid
copy of the AD/SYSVOL.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top