DFSR - 2003 R2. EventID 5012

[Itsme]

I am using 3 Windows 2003 servers in the test environment - A,B and C. If a DFS replication group is created on A or B, then it replicates to all other servers quickly showing up in DFS management and all the file replication starts quickly. But if a DFS replication group is created on C, then it will take approximately 2 hours for it to appear on A and B and will also show the below event id:


The DFS Replication service failed to communicate with partner TestC for replication group Test. The partner did not recognize the connection or the replication group configuration.

Partner DNS Address: TestC.domain.local

Optional data if available:
Partner WINS Address: TestC
Partner IP Address: 192.168.100.2

The service will retry the connection periodically.

Additional Information:
Error: 9026 (The connection is invalid)
Connection ID: 920C3D6C-489C-49FB-A590-9638011B3407
Replication Group ID: CAE30C5F-A2F0-42E3-B2FF-7688E72AE563

Any ideas?

[Zachary]

Have you tried to check the DNS settings on that DC and also check AD replication as well.

[Itsme]

I have now changed the server DNS settings to use the same DNS server that the other 2 working boxes are using. I have cleared the cache and created another replication partner, which yielded the same event issue. I also checked the AD replication using replmon and it is working fine without any issues.

[ndesgros]

I have the same problem, but it seems to be confined to only 1 folder on 1 server of my DFS replication...

No matter what I do, it does not replicate and it gives me the same error.

I had the same problem previously and the only way I found to work around the problem was to make the replication under a new folder with a different name...

Would the problem be located somewhere in the registry? can it be a reesultant of a "crash" of the replication? I'm still looking for that, but I know for a fact that the problem lies with the name of the folder..

If I found something soon I will let you know.