• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 359
  • Last Modified:

Windows Server 2008 R2 DFS does not replicate to one of the members

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:
\\mydomain\sharedfolder

each of the namespace servers points to the path:
\\Server1DFSR\SharedFolder
\\Server2DFSR\SharedFolder
\\Server3DFSR\SharedFolder

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.
\\mydomain\sharedfolder
\\Server1DFSR\SharedFolder
\\Server2DFSR\SharedFolder
\\Server3DFSR\SharedFolder

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.
0
AJKBOC
Asked:
AJKBOC
  • 3
2 Solutions
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

Do you see replication errors in the event viewer? If yes, what are they?
0
 
Manjunath SulladTechnical ConsultantCommented:
Add exception for RPC (port 135)

Refer : http://support.microsoft.com/kb/832017#method9

Refer below MS article to troubleshoot DFS replication :

http://support.microsoft.com/kb/272279

Please check below link and for more information.

http://community.spiceworks.com/topic/252067-dfs-replication-not-replicating-changes-from-one-member-but-receives-changes
0
 
AJKBOCAuthor Commented:
@Patricksr1972, no there are no errors that refer to Server3DFSR. I have removed the server from namespace servers and the replication group.


@Manjunath Sullad, I will look into your suggestions and let you know.
0
 
AJKBOCAuthor Commented:
We have tried the suggested solutions on the links but the problem was not resolved.

What we have done is to remove the problematic server from the namespace servers, from the replication group, removed the dfs role and remote it from the domain. We then created a new server and added it to the domain, installed the dfs role, added it to the namespace servers and then to the replication group.

Everything seems to be working normally until now.

Thank you for your suggestions.
0
 
AJKBOCAuthor Commented:
Pointed to the right direction.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now