Lost Ability To Resolve UNC Path On Windows 10 Host to VMWare Guest

Question

This is a bit involved: I have a Windows 10 Enterprise 64-bit host and guest (VMWare 15, also running Windows 10 Enterprise 64-bit).

Until recently, I was able to resolve \\HOST from the guest and I was able to resolve \\GUEST from the host. The host is able to ping the guest IP4 successfully. When host pings guest with -a, it is able to see the correct guest computer name; when guest pings the host with -a, it is able to see the correct host computer name.

All of my virtual machines are affected. Two of them haven't been used in several months and we previously browseable using the UNC path from the host. Now even those virtual machines cannot be browsed using the shortcut that contains the UNC path. Because I know that nothing in those virtual machines or how they've been configured has changed, I suspect that the problem is with the host--especially because all VMWare guest machines cannot browse the host using its UNC path.

Both host and guest are Windows networks set to private. Each is a member of a Workgroup called WORKGROUP; Advanced Sharing has network discovery ON (with auto setup of connected devices); each has file and printer sharing turned on; each has Allow Windows to manage homegroup connections selected.

I am using the same virtual (bridged) VM network adapter for all guest virtual machines, if that matters; specifically, I'm using VMNet0.

I have no internet connectivity issues on host or guest and can surf/resolve web addresses, no problem. I also disabled firewall and antivirus tools on this system to aid in troubleshooting.

I am able to browse host from guest using the IP address: \\192.168.1.101\C, for example, works. Also, I am able to browse to a laptop that's configured on the same network with fixed IP 192.168.3.102: I can browse to it using \\laptopname\c--no problem; also, I can browse the desktop machine (that runs the virtual machines) from the laptop using the desktop's UNC name.

The UNC host names were resolving properly but something changed in the past week and I don't know what that could be. Any help would be appreciated.