FRS/Sysvol replication errors

  • Thread starter Thread starter Bill Rowland
  • Start date Start date
B

Bill Rowland

I have replication issue which has me lost. three DC's, two in parent domain
and both replicate without error when forced in Sites and Services. However
continue to have error ID 13508. I have verified NSLOOKUP resolves names,
PING name and IP passes test, DCDIAG and NETDIAG /fix returns no errors. Run
DCDIAG /e and both DC's fail connectivity test:
Doing initial non skippeable tests

Testing server: Default-First-Site-Name\BURKHART1
Starting test: Connectivity
* Active Directory LDAP Services Check
The host Check the DNS server, DHCP, server name, etc
......................... BURKHART1 failed test Connectivity

Testing server: Default-First-Site-Name\BURKHART2
Starting test: Connectivity
* Active Directory LDAP Services Check
The host Check the DNS server, DHCP, server name, etc
......................... BURKHART2 failed test Connectivity

Testing server: Default-First-Site-Name\BURKHART821
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BURKHART821 passed test Connectivity
In Sites and Services I see that under NTDS for Burkhart1 has the GUID for
burkhart2 and all others have the system setup name of <automatically
generated>.

If I remember correctly, I can delete the GUID and run the DCDIAG /fix which
should installed burkhart2 as <automatically generated>. However as this
area is very touchy and I am unable to locate these steps to be tested, I
wanted to ensure this is correct.

Thank you in advanced
 
In
Bill Rowland said:
I have replication issue which has me lost. three DC's, two in
parent domain and both replicate without error when forced in Sites
and Services. However continue to have error ID 13508. I have
verified NSLOOKUP resolves names, PING name and IP passes test,
DCDIAG and NETDIAG /fix returns no errors. Run DCDIAG /e and both
DC's fail connectivity test:
Doing initial non skippeable tests

Testing server: Default-First-Site-Name\BURKHART1
Starting test: Connectivity
* Active Directory LDAP Services Check
The host Check the DNS server, DHCP, server name, etc
......................... BURKHART1 failed test Connectivity

Testing server: Default-First-Site-Name\BURKHART2
Starting test: Connectivity
* Active Directory LDAP Services Check
The host Check the DNS server, DHCP, server name, etc
......................... BURKHART2 failed test Connectivity

Testing server: Default-First-Site-Name\BURKHART821
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BURKHART821 passed test Connectivity
In Sites and Services I see that under NTDS for Burkhart1 has the
GUID for burkhart2 and all others have the system setup name of
<automatically generated>.

If I remember correctly, I can delete the GUID and run the DCDIAG
/fix which should installed burkhart2 as <automatically generated>.
However as this area is very touchy and I am unable to locate these
steps to be tested, I wanted to ensure this is correct.

Thank you in advanced
Click to expand...

You can delete the GUID and re-run the KCC by right-clicking NTDS settings,
choose "Check Topology." If all is working, that will re-gen the auto
connections.

DCdiag won't fix sometning like this but if you post the results, it will
help give us more specific info to diagnose it. Also run netdiag /v /fix and
post that as well.

Are your DCs only pointing to your internal DNS servers or possibly an ISP's
as well? (ISP's will cause numerous problems with AD).

Is the AD DNS name a single label name ("domain" vs the required minimum of
"domain.com")?

Zone replication scope conlict possibly? This is when on one DC, the zone is
set to say the middle button (DomainDnsZones) and on another DC, it is set
to the top button (ForestDnsZones) or the bottom button (Win2000 compatible
DomainNC partition). THis will cause issues. Check all zones. Also use ADSI
Edit to check if there are any conflicts in the three partitions I
mentioned. They would start with a "CNF..." or "In Progress...."

Do the SRV records exist in the AD zone? Enable zone transfer on the zone
and see if this resolves:
nslookup
ls -t srv domain.com
Click to expand...

See if these help. Carefully read each response/comment to see if any of it
sepecifically applies to your scenario:
http://www.eventid.net/display.asp?eventid=13508&eventno=6585&source=FRS&phase=1
http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1

Please post an ipconfig /all of the two DCs please. That will help us give a
good diagnostic start.


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
 
Back
Top