Dfs issue

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

I have an odd Dfs issue. I have a domain Dfs set up that
spand multiple sites. If I'm on a Windows XP machine and
map to \\domain.com\share, I stay within my site.
However, if I go to a server holding the dfsroot, I'm
pointed to a different site (\\dfsrootserver\share). If
I try the same from a W2K server or Professional, I stay
in my site no matter what method I try to access the
resource. Does anyone know of any issues with XP
machines going to \\dfsrootserver\share?

Thanks.

Jeff
 
Jeff, inline...

In
Jeff said:
I have an odd Dfs issue. I have a domain Dfs set up that
spand multiple sites. If I'm on a Windows XP machine and
map to \\domain.com\share, I stay within my site.
Click to expand...

Supposedley that's what it's supposed to do. Good.
However, if I go to a server holding the dfsroot, I'm
pointed to a different site (\\dfsrootserver\share).
Click to expand...

Is it in the same site as the XP machine above?
Seems also you're connecting to a UNC specifying a specific server root and
not the domain root.
If
I try the same from a W2K server or Professional, I stay
in my site no matter what method I try to access the
resource.
Click to expand...

Just as you mentioned above with XP Pro. So it stays in the same site. I
assume you're mapping to the domain root \\domain.com\share

Does anyone know of any issues with XP
machines going to \\dfsrootserver\share?
Click to expand...

That looks like a specific UNC path to a specific server and not the domain
root. When you specify the domain root share, then it uses AD DFS
functionality to connect you to the closest one. If just a UNC, then it's
just a UNC.
Thanks.

Jeff
Click to expand...

Some links on it for you...

You can try to debug what's going on (should work with XP too)
HOW TO Enable DFS Debugging in Windows 2000 - Q217146 :
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q217146&

I saw another link that stipulates to enable DFS services on an XP Pro
client if it won't connect to the domain root.

Hope that helps.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace,

Thanks for the reply. I should have been more specific
in my question. Lets say I have two sites, site 1 and
site 2, each with Dfs servers (domain dfs). My XP SP1
clients, who are in site 1, connect to the
\\domain.com\share in site 1 - as I expect them to.
However, if I try to access a server holding the dfs root
by going to the UNC, then it will send me to site 2 - not
what I expected.

If I do above from a W2K machine, I always stay in the
same site as the dfs server.

I have a feeling this is a problem with XP and I'm going
to try the debugging that you sent in the article.

Thanks again.

Jeff
 
Jeff, we've recently seen another report of this problem and are
investigating. I'll post again when we understand why this is happening.
 
Thanks Jill.

I'm on the phone with Microsoft PSS and they're thinking
this may be a design flaw but they need to tell me why it
only happens with Microsoft XP clients and not Win2k.

Thanks again.

Jeff
 
In
Jeff said:
Ace,

Thanks for the reply. I should have been more specific
in my question. Lets say I have two sites, site 1 and
site 2, each with Dfs servers (domain dfs). My XP SP1
clients, who are in site 1, connect to the
\\domain.com\share in site 1 - as I expect them to.
Click to expand...
However, if I try to access a server holding the dfs root
by going to the UNC, then it will send me to site 2 - not
what I expected.
Click to expand...

Not sure, but maybe because now it's a NetBIOS resolution and the record
maybe incorrect? WHen you ping it, does it come up with the same IP that the
machine is connecting to?
If I do above from a W2K machine, I always stay in the
same site as the dfs server.
Hmm...


I have a feeling this is a problem with XP and I'm going
to try the debugging that you sent in the article.
Click to expand...

Maybe that article may help. I'm not sure at this point and haven't seen it
yet. If you find something on it, please do post back.

Thanks again.

Jeff
Click to expand...




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jeff said:
Thanks Jill.

I'm on the phone with Microsoft PSS and they're thinking
this may be a design flaw but they need to tell me why it
only happens with Microsoft XP clients and not Win2k.

Thanks again.

Jeff
Click to expand...

I would be curious of what PSS tells you.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jill Zoeller said:
Jeff, we've recently seen another report of this problem and are
investigating. I'll post again when we understand why this is
happening.
Click to expand...

Appreciate it Jill. Looking forward to your response!



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace & Jill,

Here is the official responce from PSS. XP, by design,
may go to a Dfs sever (domain based Dfs) in a remote site
by going to \\servername\root. If you right click on a
folder in that path, look at the Dfs tab and see the
referral list, PSS told me XP will go down that referral
list list until XP finds a server that responds. Thats
BS and I asked them for the document they were reading
from and was told it was an internal microsoft document.

They did offer a slight glimer of home and suggest I
disable the WebClient service on the XP Machines, stating
that service uses NetBios calls, which are all broadcast
based. I tried it but received the same results.

Anyway, I was on the phone with for about 4 - 4.5 hours
ans we were getting nowhere fast. Im thinking about
placing another call to them to reopen the case but it
may be a waste of time. Since \\domain.com\share works
fine, i may forget it about it. I'm curious to see what
you guys come up with.

Jeff
 
Jeff, the development team here is investigating this and have found this to
be "by design" for W2K DFS--I assume this is the version you are using?
What's basically happening is when your client connects a domain-based
namespace by using the server name, the server is sending a purposefully
random list of referrals. I'm not sure why you're seeing different behavior
for different clients but I will bring this up to them.

You are right that connecting via the domain name works fine and in fact
this is the way we recommend clients connect to domain-based namespaces, so
for now please have your clients connect this way. I'll post more when I
know more.
 
In
Jeff said:
Ace & Jill,

Here is the official responce from PSS. XP, by design,
may go to a Dfs sever (domain based Dfs) in a remote site
by going to \\servername\root. If you right click on a
folder in that path, look at the Dfs tab and see the
referral list, PSS told me XP will go down that referral
list list until XP finds a server that responds. Thats
BS and I asked them for the document they were reading
from and was told it was an internal microsoft document.

They did offer a slight glimer of home and suggest I
disable the WebClient service on the XP Machines, stating
that service uses NetBios calls, which are all broadcast
based. I tried it but received the same results.

Anyway, I was on the phone with for about 4 - 4.5 hours
ans we were getting nowhere fast. Im thinking about
placing another call to them to reopen the case but it
may be a waste of time. Since \\domain.com\share works
fine, i may forget it about it. I'm curious to see what
you guys come up with.

Jeff
Click to expand...


I have nothing on it Jeff. However, I do like Jill's response and
suggestion, since DFS is designed to use the domain name and not the
servername anyway.

However, I am still curious if there's a resolution and will hang in there
for it.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Just to let you know that we have confirmed this problem and I believe they
are working on a hotfix. Unfortunately I don't have an ETA for you but I'll
let you know as soon as I do.



--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ace Fekay [MVP]"
In Jill Zoeller [MSFT] <[email protected]> posted their thoughts, then
I offered mine
Jeff, we've recently seen another report of this problem and are
investigating. I'll post again when we understand why this is
happening.
Click to expand...

Appreciate it Jill. Looking forward to your response!



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
 
In
Jill Zoeller said:
Just to let you know that we have confirmed this problem and I
believe they are working on a hotfix. Unfortunately I don't have an
ETA for you but I'll let you know as soon as I do.
Click to expand...

I appreciate the followup Jill for the poster and myself as well. When it
comes out, hopefully the original poster continues to monitor this thread,
otherwise, I'll send him an email!

I actually cc'd this to him just in case...

Thanks again!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top