Hi All,
First let me explain our network setup
Datacentre - 192.168.1.0/24
Branch 1 - 192.168.2.0/24
Branch 2 - 192.168.3.0/24
Branch 3 - 192.168.4.0/24
Branch 4 - 192.168.5.0/24
Branch 5 - 192.168.6.0/24
Branch 6 - 192.168.7.0/24
Branch 7 - 192.168.8.0/24
Branch 8 - 192.168.9.0/24
Branch 9 - 192.168.10.0/24
Branch 10 - 192.168.11.0/24
Branch 11 - 192.168.12.0/24
Branch 12 - 192.168.13.0/24
Branch 13 - 192.168.14.0/24
Branch 14 - 192.168.15.0/24
Main Site - 192.168.16.0/23 (due to larger number of client devices at site)
At each "site" including the Datacentre there are 2 x DCs which are also acting as file Servers / DFS. These are on 192.168.x.1 / 192.168.x.2
We have a DFS Namespace of \\domain.local\data with every DC being a Name Space Server. All Name Space Server have been set with the option "Override referral ordering" with the 1st DC at each site set to "First among targets of equal cost"
and the 2nd DC at each site set to "Last among targets of equal cost"
The same settings apply to Name Space Folders like \\domain.local\data\Finance etc, "Override referral ordering" is enabled with the 1st DC set to "First among targets of equal cost" and the 2nd DC at each site set to "Last among
targets of equal cost"
The Branch Sites only have routing to the Datacentre and the Main Site and cannot communicate with each other.
In Active Directory Sites and Services all sites have been added, and the corresponding subnets.
Active Directory Site Links with Costs
Datacentre-Branch1 (Cost 100)
Datacentre-Branch2 (Cost 100)
Datacentre-Branch3 (Cost 100)
Datacentre-Branch4 (Cost 100)
Datacentre-Branch5 (Cost 100)
Datacentre-Branch6 (Cost 100)
Datacentre-Branch7 (Cost 100)
Datacentre-Branch8 (Cost 100)
Datacentre-Branch9 (Cost 100)
Datacentre-Branch10 (Cost 100)
Datacentre-Branch11 (Cost 100)
Datacentre-Branch12 (Cost 100)
Datacentre-Branch13 (Cost 100)
Datacentre-Branch14 (Cost 100)
Datacentre-MainSite (Cost 50)
MainSite-Branch1 (Cost 60)
MainSite-Branch2 (Cost 60)
MainSite-Branch3 (Cost 60)
MainSite-Branch4 (Cost 60)
MainSite-Branch5 (Cost 60)
MainSite-Branch6 (Cost 60)
MainSite-Branch7 (Cost 60)
MainSite-Branch8 (Cost 60)
MainSite-Branch9 (Cost 60)
MainSite-Branch10 (Cost 60)
MainSite-Branch11 (Cost 60)
MainSite-Branch12 (Cost 60)
MainSite-Branch13 (Cost 60)
Mainsite-Branch14 (Cost 60)
On a PC or Server in any site, if you run the command NLTEST /dsgetsite you get the correct site name returned
The problem we are having is if you access \\domain.local\data\shared.data or any other "Folder" (they are all setup the same way) as some sites it takes a few seconds to open.
On the client PCs we have run the following command dfsutil /pktinfo and get the following results
Entry: \BRANCH14-AD01.domain.local\data\Shared.Data
ShortEntry: \BRANCH14-AD01.domain.local\data\Shared.Data
Expires in 1793 seconds
UseCount: 2 Type:0x8001 ( DFS FAILBACK_ENABLED )
0:[\BRANCH14-ad01\shared.data$] AccessStatus: 0 ( ACTIVE TARGETSET )
1:[\BRANCH14-ad02\shared.data$] ( TARGETSET )
2:[\MAIN-AD01\Shared.Data$] ( TARGETSET )
3:[\MAIN-AD02\Shared.Data$] ( TARGETSET )
4:[\BRANCH1-ad01\shared.data$] ( TARGETSET )
5:[\BRANCH1-ad02\shared.data$] ( TARGETSET )
6:[\BRANCH2-ad01\shared.data$] ( TARGETSET )
7:[\BRANCH2-ad02\shared.data$] ( TARGETSET )
8:[\BRANCH3-ad01\shared.data$] ( TARGETSET )
9:[\BRANCH4-ad01\shared.data$]
10:[\BRANCH5-ad01\shared.data$]
11:[\BRANCH6-ad01\shared.data$]
12:[\BRANCH7-AD01\Shared.Data$]
13:[\BRANCH8-ad01\shared.data$]
14:[\BRANCH9-ad01\shared.data$]
15:[\BRANCH10-AD01\Shared.Data$]
16:[\BRANCH11-ad01\shared.data$]
17:[\BRANCH13-AD01\Shared.Data$]
18:[\BRANCH12-ad01\shared.data$]
19:[\BRANCH11-AD02\Shared.Data$] ( TARGETSET )
20:[\BRANCH5-ad02\shared.data$] ( TARGETSET )
21:[\BRANCH13-AD02\Shared.Data$]
22:[\BRANCH4-ad02\shared.data$]
23:[\BRANCH3-ad02\shared.data$]
24:[\BRANCH8-ad02\shared.data$]
25:[\BRANCH6-ad02\shared.data$]
26:[\BRANCH7-AD02\Shared.Data$]
27:[\BRANCH9-ad02\shared.data$]
28:[\BRANCH10-AD02\Shared.Data$]
29:[\BRANCH12-ad02\shared.data$]
As you can see it has picked the "correct" ACTIVE DFS Target, but is has TARGETSET next to the wrong servers, most of which it does not even have routing to.
After doing a lot of research online I have tried the following:
> Disabled IPv6 on All Servers + Clients using the registry key
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
"DisabledComponents"=dword:000000ff
> Rebooted clients and run the command dfsutil /pktflush
These have had no effect. I then went to run the command on the 1st DC at BRANCH14 and got the exact same results using dfsutil /pktinfo. It picked the correct Server as "ACTIVE" but then randomly has Target set with other servers which it has
no routing to.
Sorry for the long post :) Has anyone got any ideas ?
Cheers, Scott