DFS Replication encountered an error while communicating with a replication partner during replication. DFS Replication will retry replication.
An unhealthy state of this monitor is caused by communication errors during replication. Communication errors can occur for the following reasons:
To test network connectivity with the affected server, use the following procedure:
Note: For more information about troubleshooting network issues, see
article 325487 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkid=46059).
If a firewall has been configured between replication partners, ensure that it is not blocking RPC communication. DFS Replication depends on RPC for communication. DFS Replication uses the RPC Endpoint Mapper (port 135) and a randomly assigned dynamic port
in the range of 49152 through 65535 for Windows Server 2008 R2 and Windows Server 2008, or in the range of 1025 through 5000 for Windows Server 2003 R2.
You can use the Dfsrdiag command-line tool to specify a static port instead of the dynamic port. For more information about how to specify the RPC Endpoint Mapper, see
article 154596 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=73991). For more information about dynamic port usage in Windows Server 2008, see
article 929851 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=187092).
Install the latest service pack and updates on all members of the replication group.
To manually confirm that replication is healthy, run a propagation test on the affected folder by using DFS Management or the following commands where <ReplicationGroup>
is the name of the replication group and <ReplicatedFolder>
is the name of the replicated folder:
dfsrdiag propagationtest /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml
dfsrdiag propagationreport /rgname:"<ReplicationGroup>" /rfname:"<ReplicatedFolder>" /testfilename:DFS-RTestFile.xml /reportfilename:c:\DFS-R_Report.xml
Why verify if replication is healthy ? It is NOT healthy, because DFSR communication is not possible with that server. The server tries to connect to a replication group which has been deleted.