FreeBSD 12 Samba 4.8.12 Samba is not showing up on my Win 10 PRO machine. I can access the shares if I use the machines hostname or IP, though. How can I determine what version of ?smb? is being used? I have set ?client max protocol = SMB3? in the config file; however, I am not sure if it is being used. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20191014/2db1806b/attachment.sig>
On 14/10/2019 13:27, Gerard Seibert via samba wrote:> FreeBSD 12 > Samba 4.8.12 > > Samba is not showing up on my Win 10 PRO machine. I can access the > shares if I use the machines hostname or IP, though. How can I > determine what version of ?smb? is being used? I have set ?client max > protocol = SMB3? in the config file; however, I am not sure if it is > being used. >Hmm, so you set 'client max protocol' to SMB3 which means SMB3_11 and this is the default, so you haven't really set anything ;-) Your problem is the lack of SMBv1, you must have this for network browsing, Samba stopped using SMBv1 when 4.5.0 was released and Windows has also turned it off on Win10, though you can still turn it back on again on both. Windows will negotiate the highest protocol possible. Rowland
Hi Gerard, Le 10/14/2019 ? 02:27 PM, Gerard Seibert via samba a ?crit :> Samba is not showing up on my Win 10 PRO machine.I can access the > shares if I use the machines hostname or IP, though.Depending on what protocol you use, it may be normal, as network browsing (through netbios or llmnr) is not a required functionality. You don't give enough information about you network to tell if it is normal or not in your case.> How can I > determine what version of ?smb? is being used?Using smbstatus, you can see which smb protocol is used by each client connection. > I have set ?client max> protocol = SMB3? in the config file; however, I am not sure if it is > being used.If you wand to be sure client machine are using smb3, you have to set server min protocol = SMB3 Cheers, Denis -- Denis Cardon Tranquil IT 12 avenue Jules Verne (Bat. A) 44230 Saint S?bastien sur Loire (FRANCE) tel : +33 (0) 240 975 755 http://www.tranquil.it Tranquil IT recrute! https://www.tranquil.it/nous-rejoindre/ Samba install wiki for Frenchies : https://dev.tranquil.it WAPT, software deployment made easy : https://wapt.fr
On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated:>On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client max >> protocol = SMB3? in the config file; however, I am not sure if it is >> being used. >> >Hmm, so you set 'client max protocol' to SMB3 which means SMB3_11 and >this is the default, so you haven't really set anything ;-) > >Your problem is the lack of SMBv1, you must have this for network >browsing, Samba stopped using SMBv1 when 4.5.0 was released and >Windows has also turned it off on Win10, though you can still turn it >back on again on both.So, if I am undertanding you correctly, Samba shares will never show automatically in Win 10's "Network" unless I manually enter the URL or share name. Is that correct?> >Windows will negotiate the highest protocol possible. > >Rowland-- Gerard