nostrasystems
asked on
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\STILLORG ANDC01
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\STILLORG ANDC01
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\STILLORG ANDC01
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: DC=talbot,DC=local
Replication Partner: Talbot-Stillorgan\STILLORG ANDC01
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\STILLORG ANDC01
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\STILLORG ANDC01
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: DC=DomainDnsZones,DC=talbo t,DC=local
Replication Partner: Talbot-Stillorgan\STILLORG ANDC01
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=talbo t,DC=local
Replication Partner: Talbot-Stillorgan\STILLORG ANDC01
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.
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\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: APPSERV01
Directory Partition: CN=Configuration,DC=talbot
Replication Partner: Talbot-Stillorgan\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: APPSERV01
Directory Partition: CN=Schema,CN=Configuration
Replication Partner: Talbot-Stillorgan\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: DC=talbot,DC=local
Replication Partner: Talbot-Stillorgan\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: CN=Configuration,DC=talbot
Replication Partner: Talbot-Stillorgan\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: CN=Schema,CN=Configuration
Replication Partner: Talbot-Stillorgan\STILLORG
Failure Code: 1722
Failure Reason: The RPC server is unavailable.
Domain Controller Name: TALBOT01
Directory Partition: DC=DomainDnsZones,DC=talbo
Replication Partner: Talbot-Stillorgan\STILLORG
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=talbo
Replication Partner: Talbot-Stillorgan\STILLORG
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.
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you read through this article (http://support.microsoft.c