locked
DFS namespace permissions RRS feed

  • Question

  • Hello,

    Recently a user accessed the DFS namespace and created a folder within the namespace.  She followed up by copying files to this namespace.  It came to our attention because the next day she was unable to find the folder when she used the propper namespace mapping.  Upon investigation here's what we found:

    The setup:

    3 servers hosting the namespace

    \\server1\namespace\

    \\server2\namespace\

    \\server3\namespace\

    all pointing to:

    \\windows\namespace\

    user was able to make a folder within the namespace (i.e. \\windows\namespace\department space\user created folder\

    She copied files there, but we can't find where the files actually went.  But we did find that 1 of the 3 dfs servers has the permissions allowing users to create folders within the dfs namespace, but the other 2 do not.  Now, if you navigate directly to that particular server (i.e. \\server2\namespace\department space\ ) what we now see is the folder, but renamed with additional characters ahead of the folder name.  In checking permissions, all 3 servers have identical permissions set.  I even tried changing the permissions to be more restrictive on the one server, and users were unable to access the namespace at all.  Obviously there is someplace where the permissions are being set, but on the dfsroot folder and the DFS management console, permissions are identical, but with 2 different responses.

    This is Server 2008 R2 for all 3 servers.

    Thank you,

    Thad

    Wednesday, December 10, 2014 2:26 PM

Answers

  • Hi Thad,

    Do you mean that you create a DFS namespace called \\windows\namespace\ and there are three folder targets in the namespace \\server1\namespace\, \\server2\namespace\ and \\server3\namespace\?

    If my understanding is correct, do you configure DFS replication on the namespace? Please give the user full control permissions on the three folder targets to check thie results.

    Best Regards,

    Mandy 

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Mandy Ye Monday, December 15, 2014 8:40 AM
    • Marked as answer by Mandy Ye Monday, December 22, 2014 10:03 AM
    Friday, December 12, 2014 6:06 AM

All replies

  • Hi Thad,

    Do you mean that you create a DFS namespace called \\windows\namespace\ and there are three folder targets in the namespace \\server1\namespace\, \\server2\namespace\ and \\server3\namespace\?

    If my understanding is correct, do you configure DFS replication on the namespace? Please give the user full control permissions on the three folder targets to check thie results.

    Best Regards,

    Mandy 

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Mandy Ye Monday, December 15, 2014 8:40 AM
    • Marked as answer by Mandy Ye Monday, December 22, 2014 10:03 AM
    Friday, December 12, 2014 6:06 AM
  • Sorry, got caught up in the holidays and several projects here. 

    So we don't want regular end users to make folders within the namespace.  As those folders aren't on the fileserver.  But I have played with permissions for the accounts that SHOULD have access, and any changes to the "{broken" namespace server results in the most noticeable issues.  Restricting permissions seems to work, but it breaks the ability to have new folders appear for a use that is connecting via that server.  But there's nothing explicitly allowing end users to write to that folder.  On all 3 servers I have done the same changes, with similar results, but going to the recommended settings is the only way it works on these servers properly, but that 1 server still allows users to make folders.

    Monday, February 23, 2015 4:03 PM