samba - Mar 2003 - WinXP DFS problems

Johan says:
> After upgrading from 2.2.5 to 2.2.8, our WinXP clients don't recognize
our 
> DFS-root shares as DFS anymore.
> When viewing the properties of a DFS root share on a WinXP client, we
don't 
> get the "DFS" -tab page.
Luc says:
> I'm having the same problems with DFS and WinXP clients since I
upgraded 
>  to 2.2.8.
>
>
>Can anyone else confirm this problem?

I can confirm this.  Upgrading from 2.2.7a to 2.2.8 breaks Dfs.  I've
upgraded and reverted several times and it's certain.  I've been looking
at logs, source and diffs between 2.2.7a and 2.2.8 all day.  I don't
know what changed between the two versions to break it.  I'm continuing
to look.  

Is msdfs actually working for anybody in 2.2.8?  Has those of you who
have had trouble found any additional clues?

EricH

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 21 Mar 2003, Eric Horst wrote:
> I can confirm this.  Upgrading from 2.2.7a to 2.2.8 breaks Dfs.  I've
> upgraded and reverted several times and it's certain.  I've been
looking
> at logs, source and diffs between 2.2.7a and 2.2.8 all day.  I don't
> know what changed between the two versions to break it.  I'm continuing
> to look.
> 
> Is msdfs actually working for anybody in 2.2.8?  Has those of you who
> have had trouble found any additional clues?
This is fixed in the SAMBA_2_2 cvs code in case you missed the commit 
message.  Only affect WinXP and .NET clients.




cheers, jerry
 ----------------------------------------------------------------------
 Hewlett-Packard            ------------------------- http://www.hp.com
 SAMBA Team                 ---------------------- http://www.samba.org
 GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
 "You can never go home again, Oatman, but I guess you can shop
there."
                            --John Cusack - "Grosse Point Blank"
(1997)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+h4JAIR7qMdg1EfYRAu3lAJ40apktbuGmwahvRErOYrK0xXOtTwCff+UA
4t+T3Trja3D16tj9502ZopU=ZG1G
-----END PGP SIGNATURE-----