On 9/27/19 10:39 AM, Rowland penny via samba wrote:> On 27/09/2019 16:19, Christopher Cox via samba wrote: >> With the removal of SMB1 (by default) and everywhere (e.g. Windows), I >> noticed that when I open up a computer (\\computer-name) I can see the >> shares that I have access to... that is, from a Windows Explorer (in >> my case Win10).? Is there any way to get something like this working >> using smbclient without SMB1? >> >> All this is without (AFAIK) enabling the Function Discovery stuff. How >> does Windows do it? >> >> It was easy with SMB1, how does Windows (and MacOS for that matter) >> discover shares that are available without explicitly specifying the >> share name that are available for a host?? And of course, is there >> anyway that "protocol" could be handled somehow in smbclient? >> >> >> > For Windows clients, see here: > > https://github.com/christgau/wsddI understand the "Function Discovery" side and wsdd (which is fine for local same network discovery somewhat similar to Network Neighborhood). I'm saying that even without that if I browse to just a computer in Windows Explorer, I get to see the shares that I have access to. I'd like that sort of feature in smbclient (if possible). smbclient's "way" has relied on NT1/SMB1 stuff. Just wondering if anyone know how to make this work the Windows way.
On 27/09/2019 18:33, Christopher Cox via samba wrote:> > I understand the "Function Discovery" side and wsdd (which is fine for > local same network discovery somewhat similar to Network > Neighborhood). I'm saying that even without that if I browse to just a > computer in Windows Explorer, I get to see the shares that I have > access to.? I'd like that sort of feature in smbclient (if possible). > > smbclient's "way" has relied on NT1/SMB1 stuff.? Just wondering if > anyone know how to make this work the Windows way. >That's not what you asked ;-) There is extensive work being done on SMBv2/3, I am sure that something like wsdd will get folded into the mix, but it won't be for some time. Getting the core components working similar to the way SMBv1 works will be the emphasis and some form of network browsing will probably come later. Rowland
On 9/27/19 12:48 PM, Rowland penny via samba wrote:> On 27/09/2019 18:33, Christopher Cox via samba wrote: >> >> I understand the "Function Discovery" side and wsdd (which is fine for >> local same network discovery somewhat similar to Network >> Neighborhood). I'm saying that even without that if I browse to just a >> computer in Windows Explorer, I get to see the shares that I have >> access to.? I'd like that sort of feature in smbclient (if possible). >> >> smbclient's "way" has relied on NT1/SMB1 stuff.? Just wondering if >> anyone know how to make this work the Windows way. >> > That's not what you asked ;-)Hmmm... I thought I was clear, but maybe not.> > There is extensive work being done on SMBv2/3, I am sure that something > like wsdd will get folded into the mix, but it won't be for some time. > Getting the core components working similar to the way SMBv1 works will > be the emphasis and some form of network browsing will probably come later.Again, wsdd (WS-DISCOVERY), which is not enabled (and perhaps not really encouraged by Microsoft) by default on Windows, it's not needed for what I'm talking about. Browse to \\computer-name see shares I have access to. Can't do this with smbclient. Prior method of using NT1/SMB1 isn't right for today. Windows (and MacOS) manage to show browseable shares without SMB1. I'd just love to see this somehow in smbclient.