Hello,
I am attempting to configure two servers (both Server 2008R2) to use DFSR to synchronize the contents of a shared folder. I have configured the replication group, and files from SiteA have been staged to SiteB. I can create a file on the SiteA server, and it is immediately replicated to SiteB. When I attempt to perform the same test on SiteB (creating a local file), that file is NOT replicated to SiteA.
I started inspecting the DFSR debug logs (on Site B), and I see errors indicating access denied:
20130624 09:04:32.411 1880 MEET 1424 Meet::Install -> WAIT Error processing update. updateName:0263_001.pdf uid:{5D84515E-4D98-46B9-8406-C26ACDDDAD87}-v1276734 gvsn:{5D84515E-4D98-46B9-8406-C26ACDDDAD87}-v1276734 connId:{E2584300-3F22-4A37-B0C0-B0C6A5ACB4AE}
csName:Users csId:{7AE4B920-9643-4418-B33D-1D453C391D5A} code:5 Error:
+[Error:9027(0x2343) Meet::InstallStep meet.cpp:1862 1880 C A failure was reported by the remote partner]
+[Error:9027(0x2343) Meet::Download meet.cpp:2281 1880 C A failure was reported by the remote partner]
+[Error:9027(0x2343) InConnection::RdcGet inconnection.cpp:3046 1880 C A failure was reported by the remote partner]
+[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5346 1880 C A failure was reported by the remote partner]
+[Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1117 1880 C A failure was reported by the remote partner]
+[Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 1880 C A failure was reported by the remote partner]
+[Error:5(0x5) DownstreamTransport::RdcGet downstreamtransport.cpp:5269 1880 W Access is denied.]
RDC is enabled on both ends, all DCs pass replication tests, the environment (including AD) is otherwise healthy.
These same two file servers in SiteA and SiteB also host other replication groups. These other replication groups are performing normally, with bidirectional synchronization occurring. I started thinking that perhaps something was configured incorrectly with the SiteB server being added into the replication group, so I removed the SiteB server from the RG and then re-added it after ensuring it fell off of DFSR's radar and deleting the data in SiteB. This gave me the same result.
Any ideas?