I noticed that my SMB shares from a Samba server no longer appeared in Windows 10 network browsing (network neighborhood) in Windows file explorer. The reason turned out to be that this functionality has originally been relying on SMBv1 to work -- which seems to have been installed and enabled by default as late as Windows 10 1703 -- but has since moved on to use WS-Discovery. Samba doesn't appear to support the latter.
What are the security implications of a SMBv1 client that only uses the protocol to discover SMB network services, without actually making a connection to a server? This blog post lists several vulnerabilities, but I don't know enough about SMB to determine whether they apply only to an SMBv1 client that is connecting/connected to a server, or if it applies even if it just sits there trying to discover servers without trying to connect.