I had samba working as a standalone server on a Centos 8 server and a windows 10 client.
Then I upgraded to samba 4.11 and everything broke down.

Here's the smb.conf file

On the server side, [konishiki was the biggest sumo wrestler in history so I use his name for my big file server] smbclient gives me the following report:
Seems to me that what I want is for SMB1 to be disabled. That's the big improvement in samba 4.0 but why is no workgroup available?

On the client side (akaoninoko is my client) net view gives this:

Obviously, akaoninoko doesn't see the shares from konishiki.
Name resolution is working and I can ping between all hosts without any problems.
I have run netshark on both interfaces and confirmed that browsing messages are being passed around and konishiki has won the election to be local master but the windows 10 client doesn't seem to have gotten the message. (pcap available on request).

Other things I have tried:
I uninstalled SMB1 support on the client but that led to a worse condition where the net view command generated a system error.
[sorry I would like to show the error message but I would need to uninstall SMB1 support again and reboot which takes a lot of time.]

Any suggestions would be greatly appreciated.

Hank

Welcome to LinuxQuestions.

Just as a side note:

path = /srv/smb
admin users = hank, hankwin hcohe
vfs objects = acl_xattr
map acl inherit = yesmap acl inherit = yes
writeable = yes
sync always = yes

These parameters are all defined for a share and do not belong in the global section. You can run testparm to check your smb.conf file. Without SMB1 enabled on the server there is no NETBIOS browsing from Windows 10 but you should be able to directly connect to a share via the file browser by manually entering the share i.e.

\\konishiki\hankwin

1 members found this post helpful.

With SMBv1 disabled by default (for well known security reasons), NetBIOS browsing/discovery is history. However, Windows 10 can discover hosts via the WS-Discovery protocol if desired, and for Linux Samba servers this can be implemented using wsdd or the newer wsdd2 (written in C)...

https://github.com/Andy2244/wsdd2

Not all distros have packages available yet, but not hard to build yourself if required. FWIW, I'm using it with openSUSE Leap 15.2 (and KDE repos enabled). The Dolphin file manager (version 20.04.0+) now has the ability to discover Windows hosts using the WS-Discovery protocol (as well as Linux Samba hosts via Avahi).

This is also on the cards for Gnome Files (Nautilus)...
https://gitlab.gnome.org/GNOME/gvfs/-/issues/506

1 members found this post helpful.

An online search turned up this wsdd package for Centos 8...
https://centos.pkgs.org/8/epel-x86_6...oarch.rpm.html
No wsdd2 package as of yet (but this is still a viable option IMHO).

1 members found this post helpful.

MichaelK,
Thanks for the tips.
It makes sense that these parameters should be associated with individual shares however testparm never reported any errors.
Is that a bug?

Regards
Hank C.

Ferrari,
Thanks for this. I installed wsdd from the epel repo and was able to mount the shares explicitly.
net view on windows still does not list the konishiki server but it did appear in the file explorer net server list after I mounted the share.
That looks like a bug for Microsoft.

As expected.

I'm not sure how net view should work in networks where NetBIOS is disabled. What I do know is that it does list shares when a hostname is used explicitly
That is much like the samba command 'smbclient' in a SMB2/SMB3 environment, whereby an explicit hostname is needed eg

FWIW, a couple of Microsoft threads confirming that "net view" relied on the Computer Browser service for discovery, which in turn relied on SMBv1 protocol (now disabled in Linux and Windows servers by default)...
https://social.technet.microsoft.com...tpronetworking
https://www.tenforums.com/network-sh...t-present.html