Weird sysvol replication issue

[CHR1S]

I have 3 DC's

 

DC1, DC2 and DC3

 

 

DC2 and DC3 replicate to each other and to DC1 (host master)

 

DC1 receives the other replications but fails to replicate back to either DC2 or DC3.

 

What could cause this?

[CHR1S]

Some further info -

 

All DC's pass dcdiag /test:replications

 

All DC's pass repadmin /showrepl

 

DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log throws up -

Warning:

Missing SRV record at DNS server 10.124.0.1:

_ldap._tcp.gc._msdcs.C.internal

 

Warning:

Missing SRV record at DNS server 10.124.0.2:

_ldap._tcp.gc._msdcs.C.internal

 

These are there in DNS on DC2 and DC3 ... only DC1 shows these errors and even then the record "look" identical across all servers

Edited December 2, 2013 by CHR1S

[CHR1S]

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt shows all DC's writeable with no errors

 

ntfrsutl ds your_dc_name > c:\sysvol.log

ERROR - Cannot bind w/authentication to computer, DC2; 000006d9 (1753)

ERROR - Cannot bind w/o authentication to computer, DC2; 000006d9 (1753)

ERROR - Cannot RPC to computer, DC2; 000006d9 (1753)

Edited December 2, 2013 by CHR1S

[Michael]

Is DNS allowed to replicate in both directions on all servers?

[CHR1S]

Is DNS allowed to replicate in both directions on all servers?

 

Its AD integrated, I am probably assuming its wrongly working.

Whats the best way to check?

[CHR1S]

I have recreated all the NTDS links in AD Sites and Services, they are all auto-generated.

 

Repadmin still shows no replication issues.

[CHR1S]

Ok, I now have full replication of new files!!

 

It did not replicate the existing however. Is that default behaviour?

[Michael]

Just sounds like a blip somewhere. I would keep an eye on it.

[CHR1S]

Its weird, every test passes, nothing unexpected in the logs bar a few failed to replicate violations of open files.

 

Hey ho, thanks for the help