[Samba] [newbie] Making sense of network discovery

Gilles codecomplete at free.fr
Wed Dec 14 14:06:03 UTC 2022


Windows 10 not seeing Samba servers through "net view" is the occasion 
to understand the issue.

Did I get this right?

Windows' Network Browser (both GUI and CLI?) relied on the Netbios API, 
which, for historical reason, relied itself partially on SMB1; The two 
weren't neatly separated at birth.

When WannaCry 
<https://dougrathbone.com/blog/2020/09/14/making-linux-samba-shares-browsable-to-windows-hosts-after-wannacry> came 
out, Microsoft had to disable SMB1 in a hurry… and broke Network 
Browser, leaving Windows users with no way to browse the network — while 
it was still possible to connect to a remote computer if you knew its name.

Upgrading SMB1 to SMB2/SMB3 didn't solve t the solution since Netbios 
relied partly on SMB1.

What did/does Microsoft offer as an alternative Network Browser that 
didn't rely on SMB? WSD <https://github.com/christgau/wsdd>? Does it 
work for both GUI and CLI (net view)?

To avoid reconfiguring Windows 7/8 hosts, can a Samba server run both 
WINS and wsdd?

Thank you.

PS: Is there an online archive of the list that's easier to search than 
downloading and grepping zip files <https://lists.samba.org/archive/samba/>?

More information about the samba mailing list