update … I got it working.
after hrs of searching forums and whitepapers and all bugged eyed out.
I was able to connect by IP …
so then I tried connecting by FQDN instead of NETBIOS name and that works.
Does not explain why Desktop 1 can connect by NETBIOS name and the other 2 can’t. All desktops are in the same Windows 2008 Window AD domain & I built them myself identically.
Desktop 1 –> Windows 10 Pro x64 –> vmware workstation pro 14
Desktop 2 –> Window 7 Ultimate x64 –> Vmware workstation pro 12 (Version 14 and 15 would not install on my i7 processors)
Desktop 3 –> Windows 10 Pro x64 –> Vmware workstation pro 12 (Version 14 and 15 would not install on my i7 processors)
But it is working now. Now my last question is why can’t I see and manage all the other VMs on the other host servers ? I can only the see the VMs I set to share. Is that by design ? If I read the manual correctly they way it was worded was “list and manage VMs on the remote server” no indication that it must be a shared VM.
Keeping in mind that when I am at work I can use workstation pro 14 & 15 on my work notebook (windows 10 pro) to connect to VMware vCenter & ESXi infrastructure …
I can see all the VMs in the datacenter, stopstart them, open console to VMs and manage them.
Why can’t I do this with workstation pro servers remotely connected to ?