I am trying to setup a SAMBA server using 3.5.0rc2 to test SMB2.
Without using SMB2, my windows 7 was able to browse the public share listed on the server anonymously. However, when SMB2 is enabled, a network error message is always shown when I try to browse the samba server from Win 7.
I have looked at the trace. It seemed to me that Win 7 had troubles accessing wkssvc, srvsvc, etc. Win 7 sent a create request for wksvc and then a close request immediately even a positive create response was returned. It only works if I types the whole share path. For example:
\\my-samba-smb2server <- NOT WORK
\\my-samba-smb2server\share <- WORK
I also want to setup a shared printer using SMB2. However, it never worked.
Created attachment 5248 [details]
Samba server FAILED
Created attachment 5249 [details]
Win 7 shares, success
This bug is still alive at Samba 3.5.0.
max protocol = smb2
writeable = yes
browseable = no
Accessing from Windows 7 (i386) with: "start \\samba350" or other same
operation always failed, but "start \\samba350\someshare" will success
(of course with proper credential info.).
Jeremy, can you have a look, is that still the case ?
Can't reproduce this in master - so will be fixed for 3.6.0.
smb2 wasn't stable supported yet. This is no issue these days for sure.