VMware Communities
lbay
Contributor
Contributor

Unable to connect to the MKS: Too many socket connect attempts; giving up on VMware workstation pro 14

I have installed vmworkstation pro 14 on a ubuntu 14.04 and whenever I try to spin up a vm I get the error

"Unable to connect to the MKS: Too many socket connect attempts; giving up"

And in the syslog I see:

vmauthd[14486]: LOCALE en_US -> NULL

vmauthd[14486]: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL

vmauthd[14486]: setuid: ignoring user's config and preferences

vmauthd[14486]: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

vmauthd[14486]: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

vmauthd[14486]: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

vmauthd[14486]: lib/ssl: OpenSSL using FIPS_drbg for RAND

vmauthd[14486]: lib/ssl: protocol list tls1.2

vmauthd[14486]: lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

vmauthd[14486]: lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

vmauthd[14486]: Connect from (local) AF_UNIX socket.

vmauthd[14486]: Connect from 127.0.0.1

vmauthd[14486]: local verification as xxxx

vmauthd[14486]: received CONNECT_NOSTART command: /usr2/xxxx/vmware/Debian9.x-64-bit/Debian 9.x 64-bit.vmx mkscontrol

vmauthd[14486]: recv() FAIL: 13.

vmauthd[14486]: VMAuthdSocketRead: read failed.  Closing socket for reading.

vmauthd[14486]: Read failed.

Have any of your encountered this?

0 Kudos
4 Replies
admin
Immortal
Immortal

If you don't mind, could you please upload a captured window image?

And you also can try below operation, to see if it will help.

1. Close the tab page.

2. When the dialog pops up, click the "run in background" button.

3. Open the VM again. (click that VM in the library)

0 Kudos
lbay
Contributor
Contributor

Screen shot of the original error.

SCREEN~1.PNG

Then I tried closing, running in the back ground and opening again, but got this error:

SCREEN~2.PNG

0 Kudos
TracyHuang
Enthusiast
Enthusiast

The returned error seems as permission denied issue. Did you set the debian VM fully accessible?

0 Kudos
lbay
Contributor
Contributor

VMware was creating the vm files in my home directory which is on a network share.  I moved it to a local mount and it is working fine now.

0 Kudos