Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > File Systems > Server names in correctly showing up as DFS namespaces

Reply
Thread Tools Display Modes

Server names in correctly showing up as DFS namespaces

 
 
Takuwind
Guest
Posts: n/a

 
      02-09-2010
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!


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: DC with "Windows cannot obtain the domain controller name for your computer network" Danny Sanders Active Directory 0 01-21-2010 02:26 PM
2nd Domain in a 2 domain forest cannot be contacted David Alge DNS Server 30 01-21-2010 05:26 AM
I also have an error 646 in Windows update. Please help. Jose Windows Update 12 01-09-2010 01:00 PM
The local domain controller could not connect with - 2008 boe Active Directory 9 11-22-2009 01:05 AM
85010014 error - resolved - ActiveSync Exchange Server Ryan Hardin ActiveSync 1 02-10-2006 04:07 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59