Hi,
I have probably the same problem:
- Host: Ubuntu 20.04
- 2 networks: eno1, eno2
- 1 bond network: bond0 (LACP)
- VMWare Workstation Pro 15.5.5 build-16285975
- several VMs running as Shared VMs on port 443
When I connect from different PC as Connect to Server, I get "A connection to the server could not be established".
Then I ssh -X to linux and start vmware from command line. This vmware also doesn't see any Shared VMs as well.
Then I have to restart vmware-workstation-server service:
drodiger@mainserver:~$ sudo service vmware-workstation-server stop
drodiger@mainserver:~$ sudo service vmware-workstation-server start
drodiger@mainserver:~$ sudo service vmware-workstation-server status
lip 04 08:08:18 mainserver systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
lip 04 08:08:18 mainserver systemd[1]: vmware-workstation-server.service: Found left-over process 40419 (vmware-vmx) in control group while starting unit. Ignoring.
lip 04 08:08:18 mainserver systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
lip 04 08:08:18 mainserver systemd[1]: vmware-workstation-server.service: Found left-over process 47045 (vmware-vmx) in control group while starting unit. Ignoring.
lip 04 08:08:18 mainserver systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
lip 04 08:08:18 mainserver systemd[1]: vmware-workstation-server.service: Found left-over process 49075 (vmware-vmx) in control group while starting unit. Ignoring.
lip 04 08:08:18 mainserver systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
And vmware started from the server (ssh -X) see the VMs running again.
But if I click on Connect from different PC with VMware Workstation (Connect to Server), it fails again, so whole vmware-workstation-server becomes unresponsive.
I also changed Bridged network configuration, not to use bond0, and only uses eno1/eno2 networks, but same issue.
Version before didn't had this problem.