(warning: long post below)
OK, back at work and here's what I've found so far:
1. IPv6 doesn't seem to be the problem in my case since none of the
roots and targets (windows 2003 SP1/R2) have IPv6 enabled and disabling
it on Vista client doesn't seem to have any effect.
2. Oddily enough the problem seems to affect one particular DFS folder
while several others with same servers as targets do not show this
behaviour.
So I copied dfsutil from XP SP2 Support Tools to Vista Business RTM
client and following is a sequence of commands I was using to
troubleshoot the problem (names changed):
====================================
C:\>dfsutil /pktflush
EntryPath=[*]
Done processing this command.
C:\>dir /b \\domain.com\shared
PublicSoftware
Backup
C:\>dfsutil /pktinfo
--mup.sys--
1 entries...
Entry: \domain.com\shared
ShortEntry: \domain.com\shared
Expires in 292 seconds
UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
0:[\localserver-01\shared] State:0x110 ( ACTIVE )
1:[\localserver-02\shared] State:0x00
2:[\remoteserver-01\shared] State:0x100 ( )
Done processing this command.
C:\>dir /b \\domain.com\shared\PublicSoftware
Office
Tools
C:\>dir /b \\domain.com\shared\Backup
Backup1
Backup2
C:\>dfsutil /pktinfo
--mup.sys--
3 entries...
Entry: \localserver-01\shared\PublicSoftware
ShortEntry: \localserver-01\shared\PublicSoftware
Expires in 1788 seconds
UseCount: 0 Type:0x1 ( DFS )
0:[\localfs-01\PublicSoftware] State:0x110 ( ACTIVE )
1:[\localfs-02\PublicSoftware] State:0x00
2:[\remotefs-01\PublicSoftware] State:0x100 ( )
Entry: \localserver-01\shared\Backup
ShortEntry: \localserver-01\shared\Backup
Expires in 1797 seconds
UseCount: 0 Type:0x1 ( DFS )
0:[\localfs-02\Backup] State:0x110 ( ACTIVE )
1:[\localfs-01\Backup] State:0x00
2:[\remotefs-01\Backup] State:0x100 ( )
Entry: \domain.com\shared
ShortEntry: \domain.com\shared
Expires in 273 seconds
UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
0:[\localserver-01\shared] State:0x110 ( ACTIVE )
1:[\localserver-02\shared] State:0x00
2:[\remoteserver-01\shared] State:0x100 ( )
Done processing this command.
====================================
So far so good. Correct listing order, correct targets are selected.
However, when I try to open \\domain.com\shared\PublicSoftware in
Windows Explorer instead of dir'ing it from command line, it opens
slowly as if accessing the share over WAN link and right after it I get
following output from dfsutil:
====================================
C:\>dfsutil /pktinfo
--mup.sys--
3 entries...
Entry: \localserver-01\shared\PublicSoftware
ShortEntry: \localserver-01\shared\PublicSoftware
Expires in 1770 seconds
UseCount: 2 Type:0x1 ( DFS )
0:[\localfs-01\PublicSoftware] State:0x100 ( )
1:[\localfs-02\PublicSoftware] State:0x00
2:[\remotefs-01\PublicSoftware] State:0x110 ( ACTIVE )
Entry: \localserver-01\shared\Backup
ShortEntry: \localserver-01\shared\Backup
Expires in 1779 seconds
UseCount: 0 Type:0x1 ( DFS )
0:[\localfs-02\Backup] State:0x110 ( ACTIVE )
1:[\localfs-01\Backup] State:0x00
2:[\remotefs-01\Backup] State:0x100 ( )
Entry: \domain.com\shared
ShortEntry: \domain.com\shared
Expires in 254 seconds
UseCount: 0 Type:0x81 ( REFERRAL_SVC DFS )
0:[\localserver-01\shared] State:0x110 ( ACTIVE )
1:[\localserver-02\shared] State:0x00
2:[\remoteserver-01\shared] State:0x100 ( )
Done processing this command.
C:\>
====================================
On the other hand, opening \\domain.com\shared\Backup in Explorer does
work as expected (local target is active). So, this is either Windows
Explorer problem or something I've missed while checking DFS/share
settings for those folders.
Go figure...
Note also that on the XP SP2 client dfsutil shows different state codes
for targets and it shows DFS folder entries as
"\domain.com\shared\backup" as opposed to
"\localserver-01\shared\backup" in output above.
--
Alexander Suhovey
-----Original Message-----
From: Alexander Suhovey [mailto:
[email protected]]
Posted At: Wednesday, December 13, 2006 12:13 AM
Posted To: microsoft.public.windows.vista.general
Conversation: DFS Clients
Subject: Re: DFS Clients
Hey,
I was out of NG for some time and boy so many answers. Thank you for
suggestions, Jill. I didn't check this yet but IPv6 really
sounds like it is
the cause. I'll check that out and reply with results later
this week (will
be busy at Platform 2007 in Moscow for the next two days).
--
Alexander Suhovey
Jill Zoeller said:
We're pretty sure it's an IPv6 issue. Here's the comment from one of the
developers:
If they have IPv6 enabled on their Windows 2003 root targets, that is not
supported. A Vista client would trigger this for the first time since
Vista automatically registers an IPv6 interface. If the root target also
has IPv6 enabled, IPv6 will be used for communication between the two. At
DFS this won't work since it assumes an IPv4 address format. Result:
mis-sorted referrals.
Easiest way to diagnose this would be to "ipconfig /all" on their roots.
If they claim an IPv6 address, this is it.
