We have a DFS replicating between 3 servers. One of the servers is not synchronizing at all. We have tried removing and re-adding the server to the DFS replication group but the problem was not resolved. We have also tried removing the server from the namespace servers and adding it back again but still the problem persists.
Some info about the case:
For the example below, we will name the server that does not replicate as "Server3DFSR" and its DFS shared folder as "SharedFolder".
The network path of the shared folders of the specific DFS namespace and replication group is:
each of the namespace servers points to the path:
All three servers are in a replication group
When you browse to the DFS shared folder you get the folder structure replicating. i.e. browsing to each path will show the same content which should mean that everything is replicating correctly.
The following strange thing is happening:
When you browse to the network path \\Server3DFSR\SharedFolder you can browse the content of the DFS replication group i.e. it shows the same content as \\mydomain\sharedfolder. If you connect on Server3DFS and check the list of its shared folders, this specific path is not listed. It's like it is pointing in a not existed share of the Server3DFSR server. Even if you remove Server3DFSR from the replication group and the namespace servers group, this path is still accessible through the network.
If you recreate the namespace and add Server3DFS to the replication group, the shared folder is created on the server, but when you connect locally on the server the real path is empty.
What do you think the problem is and what do you recommend we should do to resolve the issue. We would like to have all three servers in the group replicating properly.