Below is the error that I discovered by running the diagnostic report for my replication group. I just setup DFS today and the initial replication seemed to be going well until I noticed that the folder size on the destination server stopped growing. For the RPC error, I actually went into both servers' firewalls and allowed SVCHOST.exe and Locator.EXE to have exceptions in the firewall and I still get these errors. Disabling the firewall on both servers of course resolves the RPC related error. What exactly do I need to allow through the firewall in order for this error to stop occurring when my firewall is enabled? Also, what do I need to do in order to get the initial replication going again? With the firewalls disabled, the error did go away, but the replication appears to be not resuming. I've already gone into the DFS replication node various times to do the "Replicate Now" option, but it does not seem to be working. There's no error when I do the replicate now. It goes through as if everything is ok. I've also adjusted my staging quota to 16GB. I also noticed that when I open DFS Managment on the secondary server, it does not reflect the staging quota that I set from the primary server. It still has both values set to 4GB. When I login to the primary server, both show 16GB Communication errors are preventing replication with FILESRV01. Affected replicated folders: All replicated folders on this server. Description: DFS Replication cannot replicate with partner SERVERNAME01 due to a communication error. The DFS Replication service used partner DNS name SERVERNAME01.domain.local, IP address 182.20.1.2, and WINS address SERVERNAME01 but failed with error ID: 9032 (The connection is shutting down). Event ID: 5002 Last occurred: Thursday, August 25, 2011 at 3:42:50 PM (GMT-5:00) Suggested action: Check for network connectivity problems, for troubleshooting RPC issues see RPC KB 839880 and for additional troubleshooting information, see The Microsoft Web Site.

Hi, For question 1, please refer to this article to open related Application protocol: http://support.microsoft.com/kb/832017 For question 2, please test to restart DFS Replication service to see if replication will restart. If not, try the steps below to reset the primary server DFSRADMIN Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<member you want to be primary> /IsPrimary:True 4Force AD Replication with: REPADMIN /syncall /Aed Force DFSR to poll AD on all servers with: DFSRDIAG POLLAD /mem:<servers> One more article you can try: http://support.microsoft.com/kb/961879TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.