In general DFS Replication (DFSR) normally uses the remote procedure call (RPC) dynamic Endpoint Mapper (TCP 135 and RPC dynamic range depending of Windows OS version) between replication partners, which is maybe a problem for you ( FW rules to be checked ). You can configure DFSR to use a static port (15722 in the example below)  instead of a dynamic one by using the dfsrdiag command with the staticRPC /port:<port number> switch, then restart DFSR. For example:

dfsrdiag staticRPC /port:15722

Note: to reset to default value “0”, do, dfsrdiag staticRPC /port:0

net stop dfsr & net start dfsr

You can verify the change by typing the command below and looking at the RpcPortAssignment value, which if it shows a value of 0 means it’s using dynamic ports (anything other than 0 is the static port configured):

dfsrdiag  DumpMachineCFG

To really double-check that the static port is being used, you can inspect the port listener. First, find the process ID of dfsrs.exe:

tasklist | findstr dfsrs.exe

It might return something like this, for example:

C:\>tasklist /svc | findstr dfsrs.exe

dfsrs.exe 1772 DFSR

Now search a netstat -ano for the process ID, which will find the port being listened on. In this case, below, it shows port 15722, which was the static port configured:

C:\>netstat -ano | findstr 1772

TCP 0.0.0.0:15722 0.0.0.0:0 LISTENING 1772 TCP 192.168.1.10:5722 192.168.1.12:63377 ESTABLISHED 1772