Server names in correctly showing up as DFS namespaces

Discussion in 'File Systems' started by Takuwind, Feb 9, 2010.

  1. Takuwind

    Takuwind Guest

    I have a single domain with 2000, 2003 R2, and 2008 servers. The 2008 server
    has been given all FSMO roles. I have 3 offices, with 2 DCs in the main
    office (2008, 2000). The remote offices both have a 2003 R2 DC. DFS was
    working great until I brought the 2008 online.

    Since I brought the first 2008 server online, I have been having problems
    with my DFS Namespaces. When I run dfsutil /pktinfo, I get a list containing
    the domain name and the namespace, as would be expected. However, also in
    this list I have been seeing entries with the server name followed by one of
    the namespaces. It looks something like this:

    ------------------------------------------------------------------------------
    C:\>dfsutil /pktinfo
    --mup.sys--
    xx entries...

    Entry: \domain.com\support
    ShortEntry: \domain.com\support
    Expires in 0 seconds
    UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
    0:[\Server1\Support] State:0x110 ( ACTIVE )
    1:[\Server2\Support] State:0x100 ( )
    2:[\Server3\Support] State:0x100 ( )

    Entry: \Server1\support
    ShortEntry: \Server1\support
    Expires in 0 seconds
    UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
    0:[\Server1\Support] State:0x100 ( )
    1:[\Server2\Support] State:0x110 ( ACTIVE )
    2:[\Server3\Support] State:0x100 ( )

    Done processing this command.

    C:\>
    ------------------------------------------------------------------------------

    So essentially what happens on a client is:
    1. You go to a drive that is mapped to \\domain.com\support
    2. The client looks at its list of referrals and decides that
    \\domain.com\support = \\Server1\Support - all good so far.
    3. The client then decides that \\Server1\Support = \\Server2\Support,
    which is in a remote office
    4. The user at the desktop complains that the drive is really slow.

    I have also confirmed this behavior using this command on the server:

    ------------------------------------------------------------------------------
    C:\>dfsutil diag viewdfspath \\Server3\support

    The DFS Path <\\Server3\support> resolves to -> <\\Server1\Support>

    Done processing this command.

    C:\>
    ------------------------------------------------------------------------------

    To answer one question before it comes up, I have never created a
    stand-alone dfs path. All dfs paths have been domain paths. As far as I
    understand it, there should NEVER be a server listed directly as an entry in
    the PKT.

    I am at a complete loss over what is causing this. Can someone please help
    me!

    Thanks!
     
    Takuwind, Feb 9, 2010
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.