Steps to reproduce : - in smb.conf, set 'security = share' - enable SMB2 : 'max protocol = smb2' - define a share with guest access ( 'guest ok = yes', 'browseable = yes') (see below for a full smb.conf) - with a Window 7 client, try to browse your server ( \\samba_ip_address in the explorer) -> it fails to connect. Same thing when trying directly the share (\\samba_ip_address\share_name ) - try the same access from an XP machine -> it works fine - final test : comment out 'max protocol' line in smb.conf, relaunch samba -> Windows 7 can connect now ! Example of smb.conf : ------------------------------------- global] workgroup = WIZZ server string = Prod1bis File Server %v log file = /var/log/samba/log.%m max log size = 5000 max protocol = smb2 log level = 10 security = share encrypt passwords = yes dns proxy = no guest account = root load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes getwd cache = yes [partage] comment = Partage browseable = yes writable = yes path = /space/partage guest ok = yes -------------------------------------
Created attachment 5935 [details] sample case : log.nmb
Created attachment 5936 [details] sample case : log.smbd (1st part)
Created attachment 5937 [details] sample case : log.smbd (2nd part)
Created attachment 5938 [details] sample case : log of Windows 7 client
Created attachment 5939 [details] sample case : log of Windows 7 client (same one)
Created attachment 5940 [details] sample case : smb.conf
Created attachment 5943 [details] Fix I've applied to master and v3-6-test This fakes up "security = share" for SMB2 by mapping it to "security=user", "map to guest = Bad User". It's enough not to break people's old setups. Jeremy.
Closing this as fixed. No review feedback on the patch. Jeremy.