[Samba] Wierd interaction between Samba and HTTP?

[Jeff Coffler]

Hi,

O/S: Fedora Core 6

When running samba-3.0.24-1 (downloaded from Samba WWW site), all is 
well.  But when updating Samba via 'yum update' to samba-3.0.24-5.fc6, 
things get bad.  Things are equally bad when I try the next BETA release 
of Samba.

When things don't work, I try to mount a share from Windows, like:

    net use z: \\<host>\jeff

and it fails.  When it fails, I get the following in my *HTTP* log:

192.168.1.97 - - [15/May/2007:17:20:34 -0700] "OPTIONS / HTTP/1.1" 200 - 
"-" "Microsoft-WebDAV-MiniRedir/5.1.2600"
192.168.1.97 - - [15/May/2007:17:20:34 -0700] "PROPFIND /jeff HTTP/1.1" 
405 300 "-" "Microsoft-WebDAV-MiniRedir/5.1.2600"
192.168.1.97 - - [15/May/2007:17:22:32 -0700] "OPTIONS / HTTP/1.1" 200 - 
"-" "Microsoft-WebDAV-MiniRedir/5.1.2600"
192.168.1.97 - - [15/May/2007:17:22:32 -0700] "PROPFIND /jeff HTTP/1.1" 
405 300 "-" "Microsoft-WebDAV-MiniRedir/5.1.2600"

This problem goes away when I run samba-3.0.24-1.  So, somehow, some 
change in Samba is causing a Windows mount request to somehow get 
redirected to http ...

I did some googling, and found a suggestion that I turn off service 
webclient on the Windows side.  Doing this makes all mounts fail all the 
time.

What was changed in more recent builds of Samba that affects this?  What 
do I need to do so that I can reliably mount Samba shares from Windows 
(which are unrelated to HTTP)?

Thanks for any help,

    -- Jeff