Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Microsoft, Server, 2003, FRS, REPLMON,

Posted on 2008-10-09
3
Medium Priority
?
1,160 Views
Last Modified: 2012-05-05
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.
0
Comment
Question by:nostrasystems
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 14

Expert Comment

by:dfxdeimos
ID: 22682753
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
 

Author Comment

by:nostrasystems
ID: 22795053
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
 

Accepted Solution

by:
nostrasystems earned 0 total points
ID: 23648269
Looks like EE could not help me this this time. If no more responses I'll close the question by 20/02/09
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

618 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question