Error event id 13508 - can't replicate

K

kwele

I just set up an additional DC on Windows 2003 in a mixed 2000/2003
environment. I continually get the following message in the event
viewer:

The File Replication Service is having trouble enabling replication
from \\dc1.domain.com to dc2 for k:\sys\domain using the DNS name
\\dc1.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name \\dc1.domain.com from
this computer.
[2] FRS is not running on \\dc1.domain.com.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers.


I can ping both ways between dc1 and dc2. The FRS service is running
on both machines.

The K disk is local to dc2.

When I go to AD Sites & Services|Default-First-Site-Name|Servers, I
see 4 servers. One is a Exchange Server and the 2 original DCs and the
new DC (the one not replicating).

When I look at the NTDS Settings for each of the servers, each point
to the other 2.

Any ideas on how I can resolve my issue? TIA
 
P

ptwilliams

Where's the new DC pointing for DNS? Ensure it points to one of the other
DCs, and restart the netlogon service. Allow 15 mins for replication and
restart the ntfrs service. Once replication commences, you can switch it
back to point to itself.

A ping doesn't always prove DNS is not at fault. There's a host of AD
related records (SRV) that are needed for locating a GC, DC, etc.
Restarting netlogon will register these records if they haven't already.

--

Paul Williams
_________________________________________
http://www.msresource.net

Join us in our new forums!
http://forums.msresource.net
_________________________________________
I just set up an additional DC on Windows 2003 in a mixed 2000/2003
environment. I continually get the following message in the event
viewer:

The File Replication Service is having trouble enabling replication
from \\dc1.domain.com to dc2 for k:\sys\domain using the DNS name
\\dc1.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name \\dc1.domain.com from
this computer.
[2] FRS is not running on \\dc1.domain.com.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers.


I can ping both ways between dc1 and dc2. The FRS service is running
on both machines.

The K disk is local to dc2.

When I go to AD Sites & Services|Default-First-Site-Name|Servers, I
see 4 servers. One is a Exchange Server and the 2 original DCs and the
new DC (the one not replicating).

When I look at the NTDS Settings for each of the servers, each point
to the other 2.

Any ideas on how I can resolve my issue? TIA
 
C

Chriss3

May the FRS information not have been replicated finish to your additional
domain controller then you will see such error, How ever verify you can ping
each other by the FQDN, SAMPLE: ping server.domain.com, also use nslookup to
verify.
 
P

ptwilliams

No problem ;-)

DNS errors probably account for about 90% of all AD errors. Missing SRV
records can cause all kinds of problems.

Glad you got it sorted.

--

Paul Williams
_________________________________________
http://www.msresource.net

Join us in our new forums!
http://forums.msresource.net
_________________________________________
ptwilliams,

Thanks so much. That did it!

kwele
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top