This bug was created at Jeremy Allison's request on the samba mailing
http://lists.samba.org/archive/samba/2006-August/123801.html for my
Brief description: I get BAD SIG errors shortly after an XP client
begins to browse its home share on a Samba 3.0.23a PDC.
Steps to reproduce: log in as a domain user and browse around my home
share with Explorer. No need to open any files, just walk through
some directories and hover over some files (to get the tool tip with
more information about it).
- I've tested this with two XP SP2 clients, both running under VMware
Workstation on a FC5/i386 host. Both clients got the error.
- I get no bad signature errors when using smbclient, and log files
seem to indicate that smbclient was using signing.
- Samba seems to work fine with the same XP client when "server
signing = no".
Fedora Core 5
kernel-smp-2.6.17-1.2157_FC5 (dual core Intel system, e1000 NIC)
Fedora Directory Server 1.0.2
Windows XP SP2, up-to-date with Windows Update
Running on VMware Workstation 5.5.1 19175, bridged networking
VMware host is FC5, kernel-2.6.17-1.2157_FC5, forcedeth NIC
Complete level 10 log and tcpdump output to follow.
Created attachment 2083 [details]
log level 10 at time when bad signatures happen
PAD is domain, verin is Samba PDC, ordeith is XP SP2 client. This log starts when I click on the mapped home share drive in Explorer, and ends shortly after XP says the Samba PDC has gone offline. (6MB attachment had to be compressed so Bugzilla would accept it.)
Created attachment 2084 [details]
Created attachment 2085 [details]
Here's the patch. I reproduced it and fixed it here. Will be in 3.0.23b.
Patch fixes it here - please re-open if you can reproduce.