Microsoft, Server, 2003, FRS, REPLMON,

Hi,
I have a domain with three sites, one DC in each site. THe sites are connected through a firewall vpn link. I am experiencing File Replication issues, Event IDs like below
Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            09/10/2008
Time:            19:02:04
User:            N/A
Computer:      STILLORGANDC01
Description:
The File Replication Service is having trouble enabling replication from TALBOT01 to STILLORGANDC01 for c:\windows\sysvol\domain using the DNS name talbot01.talbot.local. FRS will keep retrying.
       Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name talbot01.talbot.local from this computer.
[2] FRS is not running on talbot01.talbot.local.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
I ran replmon and the result are below;
Active Directory Replication Domain Controller Replication Failure Output
Printed at    09/10/2008 17:39:00
Below are the replication failures detected on Domain Controllers for this domain:
Domain Controller Name:                   APPSERV01
              Directory Partition:        DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   APPSERV01
              Directory Partition:        CN=Configuration,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   APPSERV01
              Directory Partition:        CN=Schema,CN=Configuration,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   TALBOT01
              Directory Partition:        DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   TALBOT01
              Directory Partition:        CN=Configuration,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   TALBOT01
              Directory Partition:        CN=Schema,CN=Configuration,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1722
              Failure Reason:             The RPC server is unavailable.
Domain Controller Name:                   TALBOT01
              Directory Partition:        DC=DomainDnsZones,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.
Domain Controller Name:                   TALBOT01
              Directory Partition:        DC=ForestDnsZones,DC=talbot,DC=local
              Replication Partner:        Talbot-Stillorgan\STILLORGANDC01
              Failure Code:                1256
              Failure Reason:             The remote system is not available. For information about network troubleshooting, see Windows Help.

I have looked up other EE entries and googled, but none seem to relate to my issue. Does any one have any suggestion on how to fix / solve this?

Regards
NS.
nostrasystemsAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
nostrasystemsConnect With a Mentor Author Commented:
Looks like EE could not help me this this time. If no more responses I'll close the question by 20/02/09
0
 
dfxdeimosCommented:
The obvious question is when did this start happening? What changed? Are you seeing any other communication problems between sites other than this?
Have you read through this article (http://support.microsoft.com/kb/290762) ?
0
 
nostrasystemsAuthor Commented:
Sorry for delay, - Holidays,

A member server was replaced on the domain, last month, that is the only change. The FPS event logs  errors go back to May 08.

Fergus
0
All Courses

From novice to tech pro — start learning today.