If the NTFRS 13509 event also appears in Event Viewer, no user action is required. Typically, NTFRS 13509 is logged within four hours of NTFRS 13508.
If NTFRS 13509 is not logged in Event Viewer, do one or all of the following:
- Examine NTFRS 13508 in the File Replication service log in Event Viewer to determine which computer FRS could not communicate with.
- Determine whether the remote computer is working correctly, and verify that FRS is running on it. To verify that the service is running on the computer logging NTFRS 13508 at the command prompt type:
If running this command fails, from the computer logging NTFRS 13508, check network connectivity by pinging the
If pinging the remote domain controller name fails, then troubleshoot the problem as a DNS or TCP/IP issue. If pinging the remote domain controller name succeeds, confirm that FRS is started on the remote domain controller.
- Determine whether FRS has ever been able to communicate with the remote computer by looking for NTFRS 13509 in the File Replication Service log in Event Viewer and reviewing recent changes to networking, firewalls, DNS configuration, and Active Directory infrastructure for a correlation.
- Determine whether there is anything between the two computers that is capable of blocking RPC traffic, such as a firewall or router.
- Confirm that Active Directory replication is working.
For more information about troubleshooting FRS problems, see Monitoring and Troubleshooting the File Replication Service at the Microsoft Windows Server 2003 Technology Center.