Bug 7078 - Unable to browse share by \\ip-address\ using SMB2
Summary: Unable to browse share by \\ip-address\ using SMB2
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: SMB2 (show other bugs)
Version: 3.5.0rc2
Hardware: x64 Windows 7
: P3 major
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 11:38 UTC by Daniel Ng
Modified: 2018-03-21 23:24 UTC (History)
1 user (show)

See Also:

Attachments
Samba server FAILED (15.32 KB, application/octet-stream)
2010-01-29 11:40 UTC, Daniel Ng 		no flags Details
Win 7 shares, success (8.43 KB, application/octet-stream)
2010-01-29 11:40 UTC, Daniel Ng 		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 Daniel Ng 2010-01-29 11:38:46 UTC 
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.
Comment 1 Daniel Ng 2010-01-29 11:40:16 UTC 
Created attachment 5248 [details]
Samba server FAILED
Comment 2 Daniel Ng 2010-01-29 11:40:43 UTC 
Created attachment 5249 [details]
Win 7 shares, success
Comment 3 TAKAHASHI Motonobu 2010-03-06 09:08:19 UTC 
This bug is still alive at Samba 3.5.0.

My smb.conf:
-----
[global]
  max protocol = smb2

[homes]
  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.).
Comment 4 Guenther Deschner 2010-05-27 04:33:40 UTC 
Jeremy, can you have a look, is that still the case ?
Comment 5 Jeremy Allison 2010-05-27 11:47:43 UTC 
Can't reproduce this in master - so will be fixed for 3.6.0.
Jeremy.
Comment 6 Karolin Seeger 2010-06-11 04:21:23 UTC 
Change component
Comment 7 Björn Jacke 2018-03-21 23:24:17 UTC 
smb2 wasn't stable supported yet. This is no issue these days for sure.