Vista - DFS Clients

MSDN Final Release

Weird problem. I have two Vista test clients. When they connect to a DFS
replica, it does not always pick the one in the same subnet or closest one?
All our XP clients connect to the proper DFS Share. The DFS servers are
2003 Std Editions with only two sets in the replica. Any ideas?

I can connect directly to the server share without any issues.

Thanks,
Brian

Hi Brian,

A good place to ask DFS questions is the
microsoft.public.windows.server.dfs_frs newsgroup (for future reference).

DFS clients don't necessarily "choose" which target to connect to. They
connect to the first target in the referral, or, if that target isn't
available, they try the next one and so on. Are your Vista clients using IP
addresses that map to a proper site? DFS uses the client's IP address to
determine the site the client is in and then will order the targets in the
referral appropriately.

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

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.


"Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
> MSDN Final Release
>
> Weird problem. I have two Vista test clients. When they connect to a DFS
> replica, it does not always pick the one in the same subnet or closest
> one? All our XP clients connect to the proper DFS Share. The DFS servers
> are 2003 Std Editions with only two sets in the replica. Any ideas?
>
> I can connect directly to the server share without any issues.
>
> Thanks,
> Brian
>

Thanks Jill, thought I'd post here as it seems to only be a Vista issue and
not a server or XP client issue.

The clients receive their IP info from DHCP. DHCP and Wins are properly
configured and the clients receive info from the correct site. For example,
192.168.20.x is in Texas but always looks to the DFS referral in another
state and subnet. No other clients in Texas connect to the other referral?

Thanks,
Brian


"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
> Hi Brian,
>
> A good place to ask DFS questions is the
> microsoft.public.windows.server.dfs_frs newsgroup (for future reference).
>
> DFS clients don't necessarily "choose" which target to connect to. They
> connect to the first target in the referral, or, if that target isn't
> available, they try the next one and so on. Are your Vista clients using
> IP addresses that map to a proper site? DFS uses the client's IP address
> to determine the site the client is in and then will order the targets in
> the referral appropriately.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Want to learn more about Windows Server file and storage technologies?
> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>> MSDN Final Release
>>
>> Weird problem. I have two Vista test clients. When they connect to a
>> DFS replica, it does not always pick the one in the same subnet or
>> closest one? All our XP clients connect to the proper DFS Share. The DFS
>> servers are 2003 Std Editions with only two sets in the replica. Any
>> ideas?
>>
>> I can connect directly to the server share without any issues.
>>
>> Thanks,
>> Brian
>>
>
>

I don't think that the changes in Vista would cause clients to go out of
site when the server is the one handing out referrals. I'll check with a
developer just to make sure, but in the meantime, you might want to check
our techref guide's section on why clients go to unexpected targets. The URL
is
http://technet2.microsoft.com/Window....mspx?mfr=true
and you'll need to search for "Situations in Which Clients Access Unexpected
Targets"


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

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.


"Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
> and not a server or XP client issue.
>
> The clients receive their IP info from DHCP. DHCP and Wins are properly
> configured and the clients receive info from the correct site. For
> example, 192.168.20.x is in Texas but always looks to the DFS referral in
> another state and subnet. No other clients in Texas connect to the other
> referral?
>
> Thanks,
> Brian
>
>
> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>> Hi Brian,
>>
>> A good place to ask DFS questions is the
>> microsoft.public.windows.server.dfs_frs newsgroup (for future reference).
>>
>> DFS clients don't necessarily "choose" which target to connect to. They
>> connect to the first target in the referral, or, if that target isn't
>> available, they try the next one and so on. Are your Vista clients using
>> IP addresses that map to a proper site? DFS uses the client's IP address
>> to determine the site the client is in and then will order the targets in
>> the referral appropriately.
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Want to learn more about Windows Server file and storage technologies?
>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>
>>
>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>> MSDN Final Release
>>>
>>> Weird problem. I have two Vista test clients. When they connect to a
>>> DFS replica, it does not always pick the one in the same subnet or
>>> closest one? All our XP clients connect to the proper DFS Share. The
>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>> Any ideas?
>>>
>>> I can connect directly to the server share without any issues.
>>>
>>> Thanks,
>>> Brian
>>>
>>
>>
>

Thanks. Please let me know if you hear anything. I'll review the technet.

Brian

"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>I don't think that the changes in Vista would cause clients to go out of
>site when the server is the one handing out referrals. I'll check with a
>developer just to make sure, but in the meantime, you might want to check
>our techref guide's section on why clients go to unexpected targets. The
>URL is
>http://technet2.microsoft.com/Window....mspx?mfr=true
>and you'll need to search for "Situations in Which Clients Access
>Unexpected Targets"
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Want to learn more about Windows Server file and storage technologies?
> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
>> and not a server or XP client issue.
>>
>> The clients receive their IP info from DHCP. DHCP and Wins are properly
>> configured and the clients receive info from the correct site. For
>> example, 192.168.20.x is in Texas but always looks to the DFS referral in
>> another state and subnet. No other clients in Texas connect to the other
>> referral?
>>
>> Thanks,
>> Brian
>>
>>
>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>> Hi Brian,
>>>
>>> A good place to ask DFS questions is the
>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>> reference).
>>>
>>> DFS clients don't necessarily "choose" which target to connect to. They
>>> connect to the first target in the referral, or, if that target isn't
>>> available, they try the next one and so on. Are your Vista clients using
>>> IP addresses that map to a proper site? DFS uses the client's IP address
>>> to determine the site the client is in and then will order the targets
>>> in the referral appropriately.
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> Want to learn more about Windows Server file and storage technologies?
>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>
>>>
>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>> MSDN Final Release
>>>>
>>>> Weird problem. I have two Vista test clients. When they connect to a
>>>> DFS replica, it does not always pick the one in the same subnet or
>>>> closest one? All our XP clients connect to the proper DFS Share. The
>>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>>> Any ideas?
>>>>
>>>> I can connect directly to the server share without any issues.
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>
>>>
>>
>
>

Just to confirm an issue - I see same problem in my AD environment (Windows
2003 forrest) where XP SP2 clients always choose a working DFS target in
same subnet (site) while Vista ones pick up HQ's targets.

I've noticed it when I started adding VIsta hosts to the domain and after
rebopoot they experienced long boot delays while software installation
policies were applied.

Even setting correct target as active manually in Windows Explorer while
browsing DFS share from Vista doesn't seem to solve this problem since it
doen't seem to have any eefect, meaning, new target settings do not persist.

--
Alexander Suhovey

"Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
news:AAFD6459-3B9E-4E54-AE59-152FF03AB29F@microsoft.com...
> Thanks. Please let me know if you hear anything. I'll review the
> technet.
>
> Brian
>
> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
> news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>>I don't think that the changes in Vista would cause clients to go out of
>>site when the server is the one handing out referrals. I'll check with a
>>developer just to make sure, but in the meantime, you might want to check
>>our techref guide's section on why clients go to unexpected targets. The
>>URL is
>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>and you'll need to search for "Situations in Which Clients Access
>>Unexpected Targets"
>>
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> Want to learn more about Windows Server file and storage technologies?
>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>
>>
>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>>> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
>>> and not a server or XP client issue.
>>>
>>> The clients receive their IP info from DHCP. DHCP and Wins are properly
>>> configured and the clients receive info from the correct site. For
>>> example, 192.168.20.x is in Texas but always looks to the DFS referral
>>> in another state and subnet. No other clients in Texas connect to the
>>> other referral?
>>>
>>> Thanks,
>>> Brian
>>>
>>>
>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>>> Hi Brian,
>>>>
>>>> A good place to ask DFS questions is the
>>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>>> reference).
>>>>
>>>> DFS clients don't necessarily "choose" which target to connect to. They
>>>> connect to the first target in the referral, or, if that target isn't
>>>> available, they try the next one and so on. Are your Vista clients
>>>> using IP addresses that map to a proper site? DFS uses the client's IP
>>>> address to determine the site the client is in and then will order the
>>>> targets in the referral appropriately.
>>>>
>>>> --
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>> Want to learn more about Windows Server file and storage technologies?
>>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>>
>>>>
>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>>> MSDN Final Release
>>>>>
>>>>> Weird problem. I have two Vista test clients. When they connect to a
>>>>> DFS replica, it does not always pick the one in the same subnet or
>>>>> closest one? All our XP clients connect to the proper DFS Share. The
>>>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>>>> Any ideas?
>>>>>
>>>>> I can connect directly to the server share without any issues.
>>>>>
>>>>> Thanks,
>>>>> Brian
>>>>>
>>>>
>>>>
>>>
>>
>>
>

Same problem I am having. If I hard code in IP address, DNS, & WINS to the
Vista client, all is fine. I have been over and over the servers and all is
fine in the configuration.

Thanks,
Brian

"Alexander Suhovey" <asuhovey@gmail.com> wrote in message
newsAB8F3DB-1672-49EF-AF6D-40B535AE5CCA@microsoft.com...
> Just to confirm an issue - I see same problem in my AD environment
> (Windows 2003 forrest) where XP SP2 clients always choose a working DFS
> target in same subnet (site) while Vista ones pick up HQ's targets.
>
> I've noticed it when I started adding VIsta hosts to the domain and after
> rebopoot they experienced long boot delays while software installation
> policies were applied.
>
> Even setting correct target as active manually in Windows Explorer while
> browsing DFS share from Vista doesn't seem to solve this problem since it
> doen't seem to have any eefect, meaning, new target settings do not
> persist.
>
> --
> Alexander Suhovey
>
> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
> news:AAFD6459-3B9E-4E54-AE59-152FF03AB29F@microsoft.com...
>> Thanks. Please let me know if you hear anything. I'll review the
>> technet.
>>
>> Brian
>>
>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>> news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>>>I don't think that the changes in Vista would cause clients to go out of
>>>site when the server is the one handing out referrals. I'll check with a
>>>developer just to make sure, but in the meantime, you might want to check
>>>our techref guide's section on why clients go to unexpected targets. The
>>>URL is
>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>and you'll need to search for "Situations in Which Clients Access
>>>Unexpected Targets"
>>>
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> Want to learn more about Windows Server file and storage technologies?
>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>
>>>
>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>>>> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
>>>> and not a server or XP client issue.
>>>>
>>>> The clients receive their IP info from DHCP. DHCP and Wins are
>>>> properly configured and the clients receive info from the correct site.
>>>> For example, 192.168.20.x is in Texas but always looks to the DFS
>>>> referral in another state and subnet. No other clients in Texas
>>>> connect to the other referral?
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>>
>>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>>>> Hi Brian,
>>>>>
>>>>> A good place to ask DFS questions is the
>>>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>>>> reference).
>>>>>
>>>>> DFS clients don't necessarily "choose" which target to connect to.
>>>>> They connect to the first target in the referral, or, if that target
>>>>> isn't available, they try the next one and so on. Are your Vista
>>>>> clients using IP addresses that map to a proper site? DFS uses the
>>>>> client's IP address to determine the site the client is in and then
>>>>> will order the targets in the referral appropriately.
>>>>>
>>>>> --
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>> Want to learn more about Windows Server file and storage technologies?
>>>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>>>
>>>>>
>>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>>>> MSDN Final Release
>>>>>>
>>>>>> Weird problem. I have two Vista test clients. When they connect to
>>>>>> a DFS replica, it does not always pick the one in the same subnet or
>>>>>> closest one? All our XP clients connect to the proper DFS Share. The
>>>>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>>>>> Any ideas?
>>>>>>
>>>>>> I can connect directly to the server share without any issues.
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>

Cross Posted To: microsoft.public.windows.server.dfs_frs

Has anyone in the server group heard of this:

Have a Win2003 domain with two sites, one in 192.168.20.x and the other in
192.168.100.x with DFS using full mesh. All the clients are XP with the
latest packs installed. DNS, DHCP and Wins.

I have two Vista clients in each site and they receive their IP via DHCP as
well. They are the only machines in the sites that do not always pick the
correct DFS target when configured with DHCP. If I hard wire the IP
information, it seems to resolve the issues. It seems that I am no longer
the only person seeing this.

I have verified that the clients get the correct IP for the site and the
severs are in different sites...

Any ideas?

Thanks,
Brian




"Alexander Suhovey" <asuhovey@gmail.com> wrote in message
newsAB8F3DB-1672-49EF-AF6D-40B535AE5CCA@microsoft.com...
> Just to confirm an issue - I see same problem in my AD environment
> (Windows 2003 forrest) where XP SP2 clients always choose a working DFS
> target in same subnet (site) while Vista ones pick up HQ's targets.
>
> I've noticed it when I started adding VIsta hosts to the domain and after
> rebopoot they experienced long boot delays while software installation
> policies were applied.
>
> Even setting correct target as active manually in Windows Explorer while
> browsing DFS share from Vista doesn't seem to solve this problem since it
> doen't seem to have any eefect, meaning, new target settings do not
> persist.
>
> --
> Alexander Suhovey
>
> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
> news:AAFD6459-3B9E-4E54-AE59-152FF03AB29F@microsoft.com...
>> Thanks. Please let me know if you hear anything. I'll review the
>> technet.
>>
>> Brian
>>
>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>> news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>>>I don't think that the changes in Vista would cause clients to go out of
>>>site when the server is the one handing out referrals. I'll check with a
>>>developer just to make sure, but in the meantime, you might want to check
>>>our techref guide's section on why clients go to unexpected targets. The
>>>URL is
>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>and you'll need to search for "Situations in Which Clients Access
>>>Unexpected Targets"
>>>
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> Want to learn more about Windows Server file and storage technologies?
>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>
>>>
>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>>>> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
>>>> and not a server or XP client issue.
>>>>
>>>> The clients receive their IP info from DHCP. DHCP and Wins are
>>>> properly configured and the clients receive info from the correct site.
>>>> For example, 192.168.20.x is in Texas but always looks to the DFS
>>>> referral in another state and subnet. No other clients in Texas
>>>> connect to the other referral?
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>>
>>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>>>> Hi Brian,
>>>>>
>>>>> A good place to ask DFS questions is the
>>>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>>>> reference).
>>>>>
>>>>> DFS clients don't necessarily "choose" which target to connect to.
>>>>> They connect to the first target in the referral, or, if that target
>>>>> isn't available, they try the next one and so on. Are your Vista
>>>>> clients using IP addresses that map to a proper site? DFS uses the
>>>>> client's IP address to determine the site the client is in and then
>>>>> will order the targets in the referral appropriately.
>>>>>
>>>>> --
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>> Want to learn more about Windows Server file and storage technologies?
>>>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>>>
>>>>>
>>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>>>> MSDN Final Release
>>>>>>
>>>>>> Weird problem. I have two Vista test clients. When they connect to
>>>>>> a DFS replica, it does not always pick the one in the same subnet or
>>>>>> closest one? All our XP clients connect to the proper DFS Share. The
>>>>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>>>>> Any ideas?
>>>>>>
>>>>>> I can connect directly to the server share without any issues.
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>

I'll re-ping the developer I asked earlier.

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

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.


"Alexander Suhovey" <asuhovey@gmail.com> wrote in message
newsAB8F3DB-1672-49EF-AF6D-40B535AE5CCA@microsoft.com...
> Just to confirm an issue - I see same problem in my AD environment
> (Windows 2003 forrest) where XP SP2 clients always choose a working DFS
> target in same subnet (site) while Vista ones pick up HQ's targets.
>
> I've noticed it when I started adding VIsta hosts to the domain and after
> rebopoot they experienced long boot delays while software installation
> policies were applied.
>
> Even setting correct target as active manually in Windows Explorer while
> browsing DFS share from Vista doesn't seem to solve this problem since it
> doen't seem to have any eefect, meaning, new target settings do not
> persist.
>
> --
> Alexander Suhovey
>
> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
> news:AAFD6459-3B9E-4E54-AE59-152FF03AB29F@microsoft.com...
>> Thanks. Please let me know if you hear anything. I'll review the
>> technet.
>>
>> Brian
>>
>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>> news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>>>I don't think that the changes in Vista would cause clients to go out of
>>>site when the server is the one handing out referrals. I'll check with a
>>>developer just to make sure, but in the meantime, you might want to check
>>>our techref guide's section on why clients go to unexpected targets. The
>>>URL is
>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>and you'll need to search for "Situations in Which Clients Access
>>>Unexpected Targets"
>>>
>>>
>>> --
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> Want to learn more about Windows Server file and storage technologies?
>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>
>>>
>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>>>> Thanks Jill, thought I'd post here as it seems to only be a Vista issue
>>>> and not a server or XP client issue.
>>>>
>>>> The clients receive their IP info from DHCP. DHCP and Wins are
>>>> properly configured and the clients receive info from the correct site.
>>>> For example, 192.168.20.x is in Texas but always looks to the DFS
>>>> referral in another state and subnet. No other clients in Texas
>>>> connect to the other referral?
>>>>
>>>> Thanks,
>>>> Brian
>>>>
>>>>
>>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>>>> Hi Brian,
>>>>>
>>>>> A good place to ask DFS questions is the
>>>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>>>> reference).
>>>>>
>>>>> DFS clients don't necessarily "choose" which target to connect to.
>>>>> They connect to the first target in the referral, or, if that target
>>>>> isn't available, they try the next one and so on. Are your Vista
>>>>> clients using IP addresses that map to a proper site? DFS uses the
>>>>> client's IP address to determine the site the client is in and then
>>>>> will order the targets in the referral appropriately.
>>>>>
>>>>> --
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights.
>>>>>
>>>>> Want to learn more about Windows Server file and storage technologies?
>>>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>>>
>>>>>
>>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>>>> MSDN Final Release
>>>>>>
>>>>>> Weird problem. I have two Vista test clients. When they connect to
>>>>>> a DFS replica, it does not always pick the one in the same subnet or
>>>>>> closest one? All our XP clients connect to the proper DFS Share. The
>>>>>> DFS servers are 2003 Std Editions with only two sets in the replica.
>>>>>> Any ideas?
>>>>>>
>>>>>> I can connect directly to the server share without any issues.
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>

Initial responses to my email indicate that this is likely not a DFS issue.
Something else is likely afoot. Remember that it's the *server* that's
handing out referrals based on the target's and the client's site. The
client just picks the first target in the list. Something is causing the
server to sort these targets incorrectly for Vista clients.

I'll let you know if I hear any other responses. In the meantime, I'll point
you all to the following guidance:

http://technet2.microsoft.com/Window....mspx?mfr=true
and you'll need to search for "Situations in Which Clients Access Unexpected
Targets"


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

Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.


"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:ObrhbSUHHHA.1784@TK2MSFTNGP06.phx.gbl...
> I'll re-ping the developer I asked earlier.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Want to learn more about Windows Server file and storage technologies?
> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>
>
> "Alexander Suhovey" <asuhovey@gmail.com> wrote in message
> newsAB8F3DB-1672-49EF-AF6D-40B535AE5CCA@microsoft.com...
>> Just to confirm an issue - I see same problem in my AD environment
>> (Windows 2003 forrest) where XP SP2 clients always choose a working DFS
>> target in same subnet (site) while Vista ones pick up HQ's targets.
>>
>> I've noticed it when I started adding VIsta hosts to the domain and after
>> rebopoot they experienced long boot delays while software installation
>> policies were applied.
>>
>> Even setting correct target as active manually in Windows Explorer while
>> browsing DFS share from Vista doesn't seem to solve this problem since it
>> doen't seem to have any eefect, meaning, new target settings do not
>> persist.
>>
>> --
>> Alexander Suhovey
>>
>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>> news:AAFD6459-3B9E-4E54-AE59-152FF03AB29F@microsoft.com...
>>> Thanks. Please let me know if you hear anything. I'll review the
>>> technet.
>>>
>>> Brian
>>>
>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>> news:%23CCV15hGHHA.4904@TK2MSFTNGP04.phx.gbl...
>>>>I don't think that the changes in Vista would cause clients to go out of
>>>>site when the server is the one handing out referrals. I'll check with a
>>>>developer just to make sure, but in the meantime, you might want to
>>>>check our techref guide's section on why clients go to unexpected
>>>>targets. The URL is
>>>>http://technet2.microsoft.com/Window....mspx?mfr=true
>>>>and you'll need to search for "Situations in Which Clients Access
>>>>Unexpected Targets"
>>>>
>>>>
>>>> --
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights.
>>>>
>>>> Want to learn more about Windows Server file and storage technologies?
>>>> Visit our team blog at http://blogs.technet.com/filecab/default.aspx.
>>>>
>>>>
>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>> news:8A9AC89B-97C3-4479-8603-A61B88F42096@microsoft.com...
>>>>> Thanks Jill, thought I'd post here as it seems to only be a Vista
>>>>> issue and not a server or XP client issue.
>>>>>
>>>>> The clients receive their IP info from DHCP. DHCP and Wins are
>>>>> properly configured and the clients receive info from the correct
>>>>> site. For example, 192.168.20.x is in Texas but always looks to the
>>>>> DFS referral in another state and subnet. No other clients in Texas
>>>>> connect to the other referral?
>>>>>
>>>>> Thanks,
>>>>> Brian
>>>>>
>>>>>
>>>>> "Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
>>>>> news:uNfw46VGHHA.4652@TK2MSFTNGP04.phx.gbl...
>>>>>> Hi Brian,
>>>>>>
>>>>>> A good place to ask DFS questions is the
>>>>>> microsoft.public.windows.server.dfs_frs newsgroup (for future
>>>>>> reference).
>>>>>>
>>>>>> DFS clients don't necessarily "choose" which target to connect to.
>>>>>> They connect to the first target in the referral, or, if that target
>>>>>> isn't available, they try the next one and so on. Are your Vista
>>>>>> clients using IP addresses that map to a proper site? DFS uses the
>>>>>> client's IP address to determine the site the client is in and then
>>>>>> will order the targets in the referral appropriately.
>>>>>>
>>>>>> --
>>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>>> rights.
>>>>>>
>>>>>> Want to learn more about Windows Server file and storage
>>>>>> technologies? Visit our team blog at
>>>>>> http://blogs.technet.com/filecab/default.aspx.
>>>>>>
>>>>>>
>>>>>> "Brian P. Hammer" <BrianHammer@community.nospam> wrote in message
>>>>>> news:OBgum1VGHHA.1064@TK2MSFTNGP04.phx.gbl...
>>>>>>> MSDN Final Release
>>>>>>>
>>>>>>> Weird problem. I have two Vista test clients. When they connect to
>>>>>>> a DFS replica, it does not always pick the one in the same subnet or
>>>>>>> closest one? All our XP clients connect to the proper DFS Share.
>>>>>>> The DFS servers are 2003 Std Editions with only two sets in the
>>>>>>> replica. Any ideas?
>>>>>>>
>>>>>>> I can connect directly to the server share without any issues.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Brian
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>