Discussion:
Making sure Clients are connecting to local servers
(too old to reply)
EdwardQ
2008-07-14 21:31:03 UTC
Permalink
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.

The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)

I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?

THnaks..

Ed.
Paul Whitfield
2008-07-15 03:40:00 UTC
Permalink
Hi Ed,
Have you tested your DFS only with Vista clients? Try testing with a WinXP
or Win2003 (acting as a client) machine. Does it work for them? If so, then
you are probably having the same problem as me. I have just posted my problem
under the title "Vista will not connect to closest DFS target" in the
microsoft.public.windows.server.dfs_frs discussion group.

Regards
Paul Whitfield
Post by EdwardQ
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.
The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)
I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?
THnaks..
Ed.
EdwardQ
2008-07-15 12:56:07 UTC
Permalink
I don't have any Vista clients. I been testing with XP2 and Win 2003 sp2
Post by Paul Whitfield
Hi Ed,
Have you tested your DFS only with Vista clients? Try testing with a WinXP
or Win2003 (acting as a client) machine. Does it work for them? If so, then
you are probably having the same problem as me. I have just posted my problem
under the title "Vista will not connect to closest DFS target" in the
microsoft.public.windows.server.dfs_frs discussion group.
Regards
Paul Whitfield
Post by EdwardQ
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.
The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)
I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?
THnaks..
Ed.
Paul Whitfield
2008-07-15 04:03:00 UTC
Permalink
Hi Ed,
I had another thought. I have read that the DFS Closest Site (Lowest Cost)
selection only works if you use FQDN names for the targets. If you don't use
FQDNs, the machines are not able to resolve the IP correctly in DNS and
therefore cannot use the IP to caculate the Lowest Cost.

Try this setup:
(assuming your NetBIOS domain name is mahar and the FQDN domain name is
mahar.local)
Domain root DFS: \\mahar.local\DFS
Folder within this DFS: Software (so the full path is
\\mahar.local\DFS\Software)
Targets for the folder Software: \\branchAD.mahar.local\SoftwareFiles and
\\NAS.mahar.local\Software

You also need your AD Sites set up properly with costs on the site links to
do DFS costing.

I have also read that you need to configure a Query Policy in AD Sites for
this to work properly. Expand every tree in AD Sites until you get to each of
the "NTDS Settings" nodes. Right click on "NTDS Settings" and select
Properties. Click on the pulldown in Query Policy and select Default Query
Policy and click OK. Repeat for every "NTDS Settings" node in AD Sites. You
also need at least one Global Catalog in each site.

Hope this helps
Paul Whitfield
Post by EdwardQ
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.
The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)
I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?
THnaks..
Ed.
EdwardQ
2008-07-15 13:22:01 UTC
Permalink
I should have stated that.. I am using the FQDN. \\mahar.local\mytest

I have set the "NTDS Settings" nodes to Default Query Policy and have a
gobal catalog at the branch.

Its still using the Main Branch target at the remote branch. How do I see
how the setting are for the referance from the branch location?
Post by Paul Whitfield
Hi Ed,
I had another thought. I have read that the DFS Closest Site (Lowest Cost)
selection only works if you use FQDN names for the targets. If you don't use
FQDNs, the machines are not able to resolve the IP correctly in DNS and
therefore cannot use the IP to caculate the Lowest Cost.
(assuming your NetBIOS domain name is mahar and the FQDN domain name is
mahar.local)
Domain root DFS: \\mahar.local\DFS
Folder within this DFS: Software (so the full path is
\\mahar.local\DFS\Software)
Targets for the folder Software: \\branchAD.mahar.local\SoftwareFiles and
\\NAS.mahar.local\Software
You also need your AD Sites set up properly with costs on the site links to
do DFS costing.
I have also read that you need to configure a Query Policy in AD Sites for
this to work properly. Expand every tree in AD Sites until you get to each of
the "NTDS Settings" nodes. Right click on "NTDS Settings" and select
Properties. Click on the pulldown in Query Policy and select Default Query
Policy and click OK. Repeat for every "NTDS Settings" node in AD Sites. You
also need at least one Global Catalog in each site.
Hope this helps
Paul Whitfield
Post by EdwardQ
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.
The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)
I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?
THnaks..
Ed.
DaveMills
2008-07-15 21:50:33 UTC
Permalink
Post by EdwardQ
I should have stated that.. I am using the FQDN. \\mahar.local\mytest
I have set the "NTDS Settings" nodes to Default Query Policy and have a
gobal catalog at the branch.
Its still using the Main Branch target at the remote branch. How do I see
how the setting are for the referance from the branch location?
Have you set up all the IP subnets in AD Site and services.
Post by EdwardQ
Post by Paul Whitfield
Hi Ed,
I had another thought. I have read that the DFS Closest Site (Lowest Cost)
selection only works if you use FQDN names for the targets. If you don't use
FQDNs, the machines are not able to resolve the IP correctly in DNS and
therefore cannot use the IP to caculate the Lowest Cost.
(assuming your NetBIOS domain name is mahar and the FQDN domain name is
mahar.local)
Domain root DFS: \\mahar.local\DFS
Folder within this DFS: Software (so the full path is
\\mahar.local\DFS\Software)
Targets for the folder Software: \\branchAD.mahar.local\SoftwareFiles and
\\NAS.mahar.local\Software
You also need your AD Sites set up properly with costs on the site links to
do DFS costing.
I have also read that you need to configure a Query Policy in AD Sites for
this to work properly. Expand every tree in AD Sites until you get to each of
the "NTDS Settings" nodes. Right click on "NTDS Settings" and select
Properties. Click on the pulldown in Query Policy and select Default Query
Policy and click OK. Repeat for every "NTDS Settings" node in AD Sites. You
also need at least one Global Catalog in each site.
Hope this helps
Paul Whitfield
Post by EdwardQ
I have just installed DFS on our network. I have the Domain Namespace
"\\mahar\mytest". I have 2 locations Main AD is win 2003 R2, Branch AD is
Win 2003 SP2. I have preped the on the main AD.
The test folders are set up on \\branchAD\SoftwareFiles and NAS server (Win
Storage 2003 R2) \\NAS\Software. (No replication)
I have set the Namespace to use lowest Cost. When I test it from the
Branch locaton, It uses the Nas server. How do I get the Branch to use its
local server? How do I make sure that the remote branch doest use the Main
branch unless it fails over?
THnaks..
Ed.
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
Paul Whitfield
2008-07-16 05:30:38 UTC
Permalink
The best way I have found to see what is happening with the DFS referrals is
to use a packet capture tool like Wireshark (http://www.wireshark.org/).
Install Wireshark onto a client machine, make sure you clear your DFS
referral cache with "dfsutil /pktflush", start the capture, browse to the DFS
path, and stop the capture after a couple of seconds. Then look for the line
"Trans2 Response, GET_DFS_REFERRAL" in the top pane on the right and click on
it. Scroll to the bottom of the middle pane and click on the line "Unknown
Data:" (unfortunately Wireshark does not seem to be able to decode the DFS
referral like it can with other protocols). Clicking on "Unknown Data:" will
highlight a section of the raw data in the bottom pane. Look at the ASCII
half of the highlighted data on the right. I think it is in unicode, so it
appears as though it has spaces between the letters, but if you ignore the
spaces, it will show something like:
\ServerB\DFS\test
\ServerB\DFS\test
\ServerB.domain.local\DFStest
\ServerA.domain.local\DFStest

In my example above, I have a domain root DFS with 2 root targets
\\ServerA\DFS and \\ServerB\DFS. I have within that a DFS Link (Folder)
called "test" (full path \\domain.local\DFS\test) that has 2 targets
\\ServerA.domain.local\DFStest and \\ServerB.domain.local\DFStest. Since the
client is in SiteB (same site as ServerB) it should get a referral for
ServerB first, and ServerA as a secondary alternate.

This example is showing the DFS path twice for some reason, and then each of
the referrals for the targets in the DFS Link (Folder)
\\domain.local\DFS\test. ServerB is listed first, and ServerA as an alternate.

Note that the DFS path is listed as \ServerB\DFS\test instead of
\\domain.local\DFS\test. This is because I had earlier requested a DFS
referral for the path \\domain.local\DFS and got the response \ServerB\DFS.
Now that I am trying to get to \\domain.local\DFS\test, my actual DFS
referral request is sent as \ServerB\DFS\test and I get the response above.

Also note that even though the path I am browsing to starts with a double
backslash "\\" it seems that the underlying Windows only uses a leading
single backslash "\".

Have you checked that the client is detecting that it is in the right site?
Do a gpresult and look for the "Site Name:" in the top section of the
response.
Post by EdwardQ
I should have stated that.. I am using the FQDN. \\mahar.local\mytest
I have set the "NTDS Settings" nodes to Default Query Policy and have a
gobal catalog at the branch.
Its still using the Main Branch target at the remote branch. How do I see
how the setting are for the referance from the branch location?
Continue reading on narkive:
Loading...