I am managing a couple of Linux (Debian) servers for a local student tenants' association. We have one Linux server as PDC, one Linux domain member server, one Windows XP domain member workstation, and a number of clients connecting to the servers without being members of the domain. Two days ago, we suddenly noticed that the XP workstation couldn't connect to any shares on the PDC. It could, however, authenticate users against the PDC. I got the same behaviour when I tested from my W2k box. The error message is "An unexpected network error ocurred.". Changing server signing from Auto to No works around the problem. Connecting with smbclient works fine with or without SMB signing. Connecting to the member server works with server signing = Auto - at least connecting to guest shares. However, changing to security = USER, i.e. making the member server a standalone server results in the same error as above. Strangely enough, I haven't upgraded Samba the last month. This problem seems to have suddenly started after I installed a new custom 2.4.22 kernel with XFS and IPsec support. Booting the old kernel didn't help, though. In summary, two servers and two different clients exhibit the same problem, which is why I hope that at least someone can reproduce this. The servers are running Debian GNU/Linux 2.4.22 with Samba 3.0.1-3 (Debian binary packages). smb.conf and level 10 logs to be attached shortly, followed by tcpdump output if needed.
Created attachment 385 [details] Working smb.conf (with SMB signing turned off) from the PDC Please disregard the comments in Swedish...
Created attachment 386 [details] Relevant level 10 log from the PDC showing the failed connection I find the pieces of the log that look like this particularly suspect: [2004/02/07 15:45:03, 3] param/loadparm.c:lp_add_home(2323) adding home's share [magnus] for user 'magnus' at 'xëÿ¿-xçÿ¿ÿ' [2004/02/07 15:45:03, 3] libsmb/smb_signing.c:srv_set_signing(999) srv_set_signing: turning on SMB signing: signing negotiated = Yes, mandatory_signing = No. [2004/02/07 15:45:03, 5] libsmb/smb_signing.c:srv_check_incoming_message(728) srv_check_incoming_message: BAD SIG: seq 0 wanted SMB signature of [2004/02/07 15:45:03, 5] lib/util.c:dump_data(1830) [000] 87 C4 DB C4 F9 89 3C F5 ......<. [2004/02/07 15:45:03, 5] libsmb/smb_signing.c:srv_check_incoming_message(732) srv_check_incoming_message: BAD SIG: seq 0 got SMB signature of [2004/02/07 15:45:03, 5] lib/util.c:dump_data(1830) [000] 42 53 52 53 50 59 4C 20 BSRSPYL [2004/02/07 15:45:03, 5] libsmb/smb_signing.c:srv_check_incoming_message(759) srv_check_incoming_message: signing negotiated but not required and client isn't sending correct signatures. Turning off.
Created attachment 387 [details] Level 10 log showing OK connection without SMB signing
The problem seems to have been fixed in version 3.0.2.
Thanks for the update. Closing.
Oh, I think I'll have to counter-update on this. It works with W2k, but there still seems to be problem when WinXP is the client. I haven't had time to investigate further, though. I guess I'll reopen it or file a new bug when I have tested some more. Has _anyone_ tried to reproduce the problem?
please try the patch andrew posted in bug 1138. Thanks.
Patch seems to work fine. Thank you very much. Maybe you can mark either of this and 1138 as a duplicate of the other.
Thanks again for the feedback. We'll get the patch checked in before the official 3.0.3 release. *** This bug has been marked as a duplicate of 1138 ***
database cleanup