Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
DFS Replication Group refuses new member

Unanswered DFS Replication Group refuses new member

  • Saturday, August 25, 2012 11:02 AM
     
     
    Sign In to Vote
    0

    with the message "The member is running a client operating system".

    But - the member is a domain controller running Windows Server 2008 R2, being one of the namespace servers for that DFS and was member of a previous replication group for this DFS folder, which I deleted yesterday to consolidate DFS after removing the last Server 2003 R2 sharing that DFS folder. Both the wizard and the manual action to add a new member to the replication group reject that server.

    The server has been rebooted already, without improvement.

    Error from the event log of the server: "The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information. "

    So what can I do besides starting script based replication again?

    Best greetings from Germany
    Olaf

     

All Replies

  • Monday, August 27, 2012 6:17 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Olaf,

    Please have a look on this article:

    An event ID 6002 that references Distributed File System replication is logged several times a day on a Windows Server 2003 R2-based computer

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

    The hotfix is for Windows 2003 R2 so it cannot be applied to your servers, but please check the Workaround steps to see if it could help.

    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.

     
  • Monday, August 27, 2012 8:20 AM
     
     
    Sign In to Vote
    0

    Thanks,

    I deleted the mentioned entry, but this solved not the issue of not being able to add the machine to the replication group.

    Since there have been a few more messages in the event log, telling about domain trust issues, I checked the network configuration and found two issues:

    The disconnected network adapter had priority in Adapters and Bindings, and TC/IPv6 was unchecked by the local administrator.

    So I disabled the not connected network adapter, moved the active adapter to the top position and enabled IPv6 protocol. Restarted AD domain services and DFS services and after that the error message no longer appeared. However, I had still to remove the machine from the folder targets and add it again, since another error blocked adding the folder to the replication group.

    Best greetings from Germany
    Olaf