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?
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/wsdd Rowland
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.
El 27/9/19 a les 17:19, Christopher Cox via samba ha escrit:> 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? > > >?smbclient -L server' doesn't work for you? Here it lists the shares, then it says: Reconnecting with SMB1 for workgroup listing. smbXcli_negprot_smb1_done: No compatible protocol selected by server. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Unable to connect with SMB1 -- no workgroup available so I guess it isn't using SMB1 to list the shares Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
On 9/27/19 1:20 PM, Luca Olivetti via samba wrote:> El 27/9/19 a les 17:19, Christopher Cox via samba ha escrit: >> 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? >> >> >> > > ?smbclient -L server' doesn't work for you? > > Here it lists the shares, then it says: > > Reconnecting with SMB1 for workgroup listing. > smbXcli_negprot_smb1_done: No compatible protocol selected by server. > protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE > Unable to connect with SMB1 -- no workgroup available > > > so I guess it isn't using SMB1 to list the sharesYeah, our target in this case is SMB shares exposed from a MacOS. It's possible that something is just broken there with regards to not having SMB1.