Windows 10 client isn't listing share advertisements from a samba 4.11 server

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

Quote:

[global] path = /srv/smb writeable = yes security = user netbios name = konishiki wins support = yes local master = yes preferred master = yes client min protocol = SMB2 client max protocol = SMB3 sync always = yes socket options = TCP_NODELAY passdb backend = tdbsam workgroup = WORKGROUP log level = 2 unix password sync = no vfs objects = acl_xattr map acl inherit = yes wins support = yes username map = /etc/samba/smbusers admin users = hank, hankwin hcohe [homes] inherit acls = Yes browseable = no writable = yes path = /home comment = Home Directories [hankwin] path = /srv/smb/hankwin/ read only = no [hank] path = /srv/smb/hank read only = no create mask = 777

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:
Quote:

[root@konishiki samba]# smbclient -L localhost -U% Sharename Type Comment --------- ---- ------- hankwin Disk hank Disk IPC$ IPC IPC Service (Samba 4.11.2) SMB1 disabled -- no workgroup available

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:

Quote:

C:\Users\hcohe>net view Server Name Remark ------------------------------------------------------------------------------- \\AKAONINOKO The command completed successfully.

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