Bug 9649 - SMB2: Windows 7 session setup fails
Summary: SMB2: Windows 7 session setup fails
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: SMB2 (show other bugs)
Version: 3.6.6
Hardware: x86 Linux
: P5 normal
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-09 20:18 UTC by Ruud (dead mail address)
Modified: 2020-12-15 17:55 UTC (History)
0 users

See Also:

Attachments
log.smbd, smb.conf, smb2.pcapng (5.50 KB, application/gzip)
2013-02-09 20:18 UTC, Ruud (dead mail address) 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ruud (dead mail address) 2013-02-09 20:18:25 UTC 
Created attachment 8539 [details]
log.smbd, smb.conf, smb2.pcapng

Server: Ubuntu Quantal with Samba 3.6.6 (package 2:3.6.6-3ubuntu5)
Client: Windows 7 Professional 64 bit

Attached: smb2err.tar.gz (wireshark capture, smb.conf, level 4 log.smbd)
Samba config contains 'max protocol = SMB2'

The Win7 client sends a SessionSetup Request containing security mode 0x01 (signing enabled, not required).
After successfully authenticating the user, the samba server disconnects with a log entry:
Wrong session key length 0 for SMB2 signing

I tried disabling signing at the client (HKLM\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters\EnableSecuritySignature = 0, and using the group policy editor to disable signing for clients of MS-networks), but that didn't help

Is this a Windows or Samba bug?

Regards,
Ruud
Comment 1 Björn Jacke 2020-12-15 17:55:25 UTC 
sorry for the lack of feedback. This is not a bug in recent, supported version.