Resolve issues where MKS sockets are too many times for VMware Pro to start up
Online so-called to start the VMware AUTHD service, reset sock, update LSP, only a reliable, is the remote connection error solution, the original vmware-authd.exe by the firewall banned access to the network, can be removed.
Virtual Machine Firewall windows
The remote connection to VMware Workstation prompted an error: Presumably the VMware unable connect MKS login incorrect.
Google a lot of solution, but are not very reliable, and finally from http://www.tediosity.com/vmware-unable-to-connect-to-the-mks/see explanation:
Unable to connect to the Mks:login (Username/password) incorrect
Open/etc/vmware/config with a text editor.
Add this:vmauthd.server.alwaysProxy = "TRUE"
Check your firewall config/network setup.
This error was caused by your vSphere client not able to communicate with the ESX/ESXI host directly.
All "Unable to connect to the MKS:" Errors is network issues. Do is fooled by the mention of certificate issues ...
With all the network issues, the proposal is a proxy. Check it again. The port of the MKS error is 902, the server's firewall opens to 902 access rights to find the problem solved, or the direct connection should be faster.
Further check the discovery is Vmware-authd.exe monitoring 902 and 912, simply put this exe into the firewall's Allow list.