FRS 13508 (without 13509) on 2003 DC

i have thoroughly searched issue on web , technet, , i'm drawing blank after 8-10 hours of troubleshooting.   here's environment i'm working with:

i have single forest single domain.  there 3 dcs in domain, dc1, dc2, , dc4.  dc1 , dc2 gcs; dc4 not.  all 3 dns servers.  dc4 infrastructure owner; dc1 holds other fsmo roles.  domain functional level windows server 2003.  dc1 windows server 2003 sp2 server.  dc2 , dc4 2003 r2 sp2.

dc1 , dc2 able replicate sysvol each other without issues.  dc1 , dc2 both list error 13508 dc4, no error 13509.  dc4 lists no actual replication errors, though list frs 13512, don't think relevant or actual problem.

all dcs , clients able resolve dcs both hostname , fqdn.  all dcs , clients able browse sysvol shares on dcs without error.  dcdiag on dcs reports passes except on frs event, of course.  repadmin /showrepl lists no errors replicating on dcs.  however, 13509 never appears on dc1 , dc2, , sysvol replication not occur.  i can manually (explorer, robocopy, xcopy) copy sysvol between dcs.  if create new gpo or logon script or place executable or msi in netlogon, not replicate.  

all 3 dcs report no errors in chkdsk or sfc.  all 3 dcs have current windows updates installed.  all 3 dcs on same subnet, same switch.

i'm not sure head next.  i've spent lot of time troubleshooting typically pretty clear-cut issue.  the ideas have @ present make dc4 gc or move infrastructure master different server.  i demote it, though rather avoid that.

 

thanks in advance assistance.

edit: key piece of information should add these servers have reported chkdsk errors in past.  all 3 fixed chkdsk c: /r.  they never reported journal wrap errors, @ least not recollection, think drive issues possible cause of issue.  they have since been resolved, though.

i able resolve issue using information found in artitcle:

http://support.microsoft.com/kb/312862

the article extremely detailed, not quite explicit , clear in instructions expect mskb.  however, able determine dc4's ntfrssuscriptions object had been deleted.  i able recreate in adsiedit.  restarting frs on dc4 subsequently showed 13553, 13554, , 13516, , replicated sysvol dc2 , dc1.

while everyone's advice good, turns out total absence of these events , in turn, missing registry keys, indicates definitively ntfrssubscriptions domain system volume missing or corrupt.

Windows Server  >  Directory Services