none
DFS-N Inconsistencies

    Question

  • We have a couple of Namespaces in our domain which aren’t consistently accessible across our four sites.

    Our sites are

    • London (HQ)
    • Hong Kong
    • New York
    • DR

    The Namespaces are

    What happens is that from any PC in any site the contents of the namespaces can be seen from some member servers but not from others (the Explorer window just shows the text ‘This folder is empty’).

    Also, two servers (LN-FS01 and LN-DC10) can’t even be selected to switch to as active servers. In both cases clicking the ‘Set Active’ button produces no errors but upon checking the GUI again a different server has been selected as the Active server.

    Actual host names have been changed to predict the guilty

    And if I try to just open the share name on each server…


    What have we done to try to resolve this?

    • Restarted servers
    • Restarted the DFS service
    • Removed a member server, left it like that overnight, re-added it.

    It’s a somewhat bizarre situation. We can’t find any errors in the logs and of course the DFS GIU only provides diagnostics reports for DFS-R, not for DFS-N.

    Can anyone offer any ideas on what to do about this?


    • Edited by JPJ-UK Thursday, July 03, 2014 12:11 PM Added a blank line to separate last list from next paragraph
    Thursday, July 03, 2014 12:09 PM

Answers

  • Jose Barreto has a blog entry about using dfsdiag to diagnose DFS-N problems.

    I Would say that the last three methods are the most interesting for you.

    dfsdiag /TestDFSConfig
    dfsdiag /TestDFSIntegrity
    dfsdiag /TestReferral



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Even if you are not the author of a thread you can always help others by voting as Helpful. This can be beneficial to other community members reading the thread.


    Oscar Virot

    • Marked as answer by JPJ-UK Tuesday, July 08, 2014 1:33 PM
    Friday, July 04, 2014 1:57 PM

All replies

  • Hi.

    So if I understand you correctly you have two namespaces, called install and install2.

    These have 6 namespace servers each. But only 2 of the servers in install and 1 server in the install2 namespace has any links.

    I would consider the following rebuilding from scratch:

    • Dumping the configuration to file
    • Removing the root from each server
    • Making sure the AD is clean from the namespace
    • Rebuilding it
    • Restoring the configuration

    Well for a while users can't access items in the namespace, but after they should. I wrote an article about rebuilding to change DFS mode, but its the same.



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Even if you are not the author of a thread you can always help others by voting as Helpful. This can be beneficial to other community members reading the thread.


    Oscar Virot


    • Edited by Oscar Virot Thursday, July 03, 2014 6:28 PM
    Thursday, July 03, 2014 6:07 PM
  • Well I just thought of another question. Once I discussed using domainbased DFS to create a share that was domain based. ie \\domain\share where the data was directly. You are talking about real DFS with links in them right?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Even if you are not the author of a thread you can always help others by voting as Helpful. This can be beneficial to other community members reading the thread.


    Oscar Virot

    Thursday, July 03, 2014 6:09 PM
  • Thanks, Oscar.

    Just one correction though, two servers in each namespace are showing the links (rather than two in one, and one in the other).

    It is a domain based DFS Namespace, yes. The Namespaces in question have both been fully visible in the four sites before.

    Friday, July 04, 2014 9:17 AM
  • Jose Barreto has a blog entry about using dfsdiag to diagnose DFS-N problems.

    I Would say that the last three methods are the most interesting for you.

    dfsdiag /TestDFSConfig
    dfsdiag /TestDFSIntegrity
    dfsdiag /TestReferral



    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Even if you are not the author of a thread you can always help others by voting as Helpful. This can be beneficial to other community members reading the thread.


    Oscar Virot

    • Marked as answer by JPJ-UK Tuesday, July 08, 2014 1:33 PM
    Friday, July 04, 2014 1:57 PM
  • I recreated the Install namespace from scratch on Friday and it's working fine now. I think it was probably poor configuration on my part since the namespace was meant to show files that were replicated but there was little correlation between the replication partners and the namespace member servers. This time there is total correlation. i.e. the replication partners are also the member servers of the namespace.

    The Install2 namespace still exists though, and was set up as an alternative for a different (now also gone) issue with the Install namespace anyway, so I'll be using that as a guinea pig for a learning experience.

    The dfsdiag command is interesting though. Odd that it's never come up in any of my searches to resolve this issue...only dfsutil.

    Monday, July 07, 2014 9:59 AM