I haven't seen this, but I think I have a direct suggestion.
With VMs, I gather you mean VMs in a NAT network. Indeed, they should find each other and the Host should find them. I also assume that you "ping hostname". I also think that if you would "ping ip-address", it would work ... which is a workaround, but not so nice.
If the above is true, then I think Windows 10 internal DNS-functionality is unstable. You can overcome this by editing "hosts" file to include name-ip - resolution ("C:\Windows\System32\drivers\etc" is the folder). A reboot is required after that change (for ping not, but for many other functionality, it IS required). The editing needs to happen on the Host. If VMs need to see each other (in the same NAT networking), then in addition you need to edit "hosts" -file on each VM.
When VMs are copies, this kind of problem will arise - just saying, this isn't your case based on the description.
So, if the above solves it, this isn't a VMware specific thing, but a Windows 10 problem and the solution is generic networking functionality when operating in a NAT network.
