Replication failing - SYSVOL data doesn't match between servers



Hi. We have a Win2k Adv Server network with some servers, 2 DCs. We had a
motherboard failure in our main DC and the secondary DC took over as
expected. On replacing the failed hardware and restarting the main DC
everything started working again as expected and appeared to be for the last
few days.

I have since made changes to Group Policy and added and removed some users.
I noticed today that Ntfrs is reporting JRNL_WRAP_ERRORs with Event ID 13568
on one server and it looks as though replication is not taking place. If I
restart one server the the other starts to display the JRNL_WRAP_ERROR.
I've been through all the basic testing with DCDiag, NetDiag, Gpotool as
well as confrming DNS settings and attempting to initiate replication
between the servers via Active Directory. The general server settings seems
correct but on checking the SYSVOL I have found the servers contain
different group policies, one contains all the latest policies and seems
upto date, but the second DC has a lot of the old policied and a couple of
the new ones but with incorrect time stamps.

I really need to get this problem resolved. I've searched online and so far
the only document which I haven't tried is using the BurFlags registry key
to reinitialise file replication. On reading the document though it doesn't
seem the most optimistic or 'safe' way to resolve the problem.

Can anyone advise what other options I should consider ? e.g. should I
demote the server back to a member server and then promote it back to a DC
to allow replication to restart ?

Thanks for any help,
Stuart.bw


.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding 64-bit R2 DC to existing domain
    ... Server 2003 standard edition 32-bit domain controllers. ... The schema master did not complete a replication cycle ..." ... server1 failed test KnowsOfRoleHolders ... ForestDnsZones failed test CrossRefValidation ...
    (microsoft.public.windows.server.setup)