Failed Replication after tombstone lifetime period passed!!

[tabassum]

We have a single forest, single domain Windows 2000 AD architecture,
and two sites.

We have Server1 (root of the forest) in Site A. This Server has all
the Roles except Infrastructure master.

Server1 also has MS Echange 2000 installed on it.

Server 2 in Site B is a domain controller and has Exchange 2000 on it.

Everything was working fine, when the time on the Server1 in Site A
got changed from May 10th to Feb 10th and machine got a restart. After
a restart our administrator again changed the time back to May 10th

After that we have numerous error messages in event logs.

Server1, in Site A only reports error in ’File Replication Service’
(journal_wrap_error) and W32 Time Service in System Log.

Server2 in Site B however has tons of error messages. The DNS in
working fine. The Directory Service shows 1311 error. System log shows
MrxSMB error 3034 (The target principal name is incorrect). The File
Replication Service is reporting several warnings.

DCdiag and netDiag on Server1 in Site A passed all test, while Server2
failed the DCdiag test.

The replmon utility reports the error_replica_sync_Access is denied
error.

Please help me out in this regard.

Which server would need a re-install or i could prevent it.

anticipating a favourable response.

Regards,
Tabassum

 

[Jimmy Andersson [MVP]]

First I would take a look at this article; http://tinyurl.com/8pg2l. Then I
would use repadmin, sonar etc...
But can you give a reason why the time was changed?
If you change time it can cause lingering objects wich in turn will cause
replication issues depending if you use Strict or Loose replication. If that
has happened there are some stuff you can do about it, but start with the
article and see if it can help you resolve all/most of the issues.

Regards,
/Jimmy