File Replication Service.

[Fasahat]

Dear Friends.
I have a windows 2000 Network with 3 domain Controllers
namely DC1,DC2 and DC3. DC1 is my Root Domain
Controller.DC2 and DC3 are my Backup Domain Controllers.I
transferred the DC1 MASTER Roles e.g RID,PDC
Emmulator,Operations Master, to DC2 and DC1 is still on
the Network.All the Domain Controllers have DNS Running as
Active Directory Integrated.I am getting an error in the
event log in DC2 regarding the File Replication Service.

Event ID=13508
The File Replication Service is having trouble enabling
replication from DC3 to DC2 for C:\WINNT\SYSVOL\domain
using DNS name DC2.

Reasons:
1.FRS cannot correctly resolve the DNS name DC3 fromDC2.
2.FRS is not running on DC2.

I will really appericate your help
Cheers
Fasahat.

 

[Ace Fekay [MVP]]

Responses inline below...

In

Dear Friends.
I have a windows 2000 Network with 3 domain Controllers
namely DC1,DC2 and DC3. DC1 is my Root Domain
Controller.DC2 and DC3 are my Backup Domain Controllers.

No such thing as Backup Domain Controllers in AD. They are just replica
domain controllers. There is no "Primary" so to speak. It is now a mutli
master design with AD.

I transferred the DC1 MASTER Roles e.g RID,PDC
Emmulator,Operations Master, to DC2 and DC1 is still on
the Network.All the Domain Controllers have DNS Running as
Active Directory Integrated.I am getting an error in the
event log in DC2 regarding the File Replication Service.

Any reason why you needed to transfer the FSMO Roles (Flexible Single Master
Operations) ?

Event ID=13508
The File Replication Service is having trouble enabling
replication from DC3 to DC2 for C:\WINNT\SYSVOL\domain
using DNS name DC2.

Reasons:
1.FRS cannot correctly resolve the DNS name DC3 fromDC2.
2.FRS is not running on DC2.

I will really appericate your help
Cheers
Fasahat.

This error can be due to a couple things, mainly its normally due to not
using ONLY your own DNS servers. Basically the error is telling you what the
problem is, that DC2 cannot resolve DC3's name in DNS. If you have your
ISP's as a DNS address in any of your mahines' IP properties (DCs or
clients), this will cause this error and numerous other errors. Only point
to your DNS servers ONLY and use a forwarder for efficient Internet
resolution.

If you can confirm this, or remove your ISP addresses, and you're zones are
AD Integrated, then make sure as well that replication is occuring so to
insure that the zone is available on all DCs.

Look in your zone and make sure that all 3 DCs are properly registering. If
they are not, then the problem is deeper, and can be due to an incorrect
Primary DNS Suffix on each machine, Primary DNS Suffix does not match AD's
name or the zone name in DNS, incorrect DNS addresses, zone is not allowing
updates, DHCP Client service is disabled, etc.

If you like for us to better assist you, post an unedited ipconfig /all from
all 3 domain controllers please. Also, please tell us the exact name of your
AD DNS domain name so we can correlate and check your configuration.

Hope that helps.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================