Solved: Workstation 14 Player MKS: too many socket attempt...

onyekatabansi · ‎09-28-2017

Hi There,

I have VMware Workstation 14.0.0 Build-6661328 Player installed on Windows 7 Professional, I am trying to create a Windows XP Proffessional virtual machine (tried with a CD and also an ISO), the trouble is when I start it up I get the message "Unable to connect to the MKS: Too many socket connect attempts; giving up".

Any ideas greatly appreciated.

Thanks

Harwise · ‎09-29-2017

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)

View solution in original post

haiweiz · ‎09-28-2017

Hi, Onyekatabansi:

Did you upgrade from the old version of Player? Is yes, please provide the old version number.

Did you get reboot prompt when you install the 14 Player? if yes, please reboot the host machine.

If after reboot you have the same result, please open one administrator command line, and run these command:

sc query vmx86

sc query hcmon

sc query VMauthdService

Please paste the result to us.

Thanks.

onyekatabansi · ‎09-29-2017

Thanks Haiweiz,

This is a fresh install of Workstation 14 (I have never used it before), I did get the reboot prompt when I first installed it.

These are the results of the command line inputs:

C:\>sc query vmx86

SERVICE_NAME: vmx86
        TYPE               : 1 KERNEL_DRIVER
        STATE              : 4 RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\>sc query hcmon

SERVICE_NAME: hcmon
        TYPE               : 1 KERNEL_DRIVER
        STATE              : 4 RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\>sc query vmauthdservice

SERVICE_NAME: vmauthdservice
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 4 RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

C:\>

Harwise · ‎09-29-2017

Could you please power on the VM again and upload the log files? The file paths can be found from opening the About dialog (Menu Help -> About).

Both the UI log file and the vm log file are needed.

Harwise · ‎09-29-2017

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)

onyekatabansi · ‎09-29-2017

Thanks Harwise, that seems to have solved it, Windows XP is now installing.

Greatly appreciated.

Thanks

hmdat · ‎09-30-2017

Hi Harwise,

I also faced this issue on Windows 10 64 bit, when I installed the first time VM Workstation 14, I got this issued, after that, I try uninstalled and re-installed, the issue was resolved. But, today it happened again and I already tried re-installed, but it didn't work. I'm sorry but I didn't see what you called "run in background" button, because the popup dialog only has one button is "OK" button.

I attached log files here,

Could you please help check ?

Thanks and Regards,

haiweiz · ‎09-30-2017

Could you help to check the background service status as I mentioned before? looks like your case is different with previous, you need check these services status firstly:

sc query vmx86

sc query hcmon

sc query VMauthdService

Please paste the result here.

Thanks.

hmdat · ‎10-01-2017

Hi Haiweiz,

my checking result:

C:\>sc query vmx86

SERVICE_NAME: vmx86

TYPE : 1 KERNEL_DRIVER

STATE : 4 RUNNING

(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x0

C:\>sc query hcmon

SERVICE_NAME: hcmon

TYPE : 1 KERNEL_DRIVER

STATE : 4 RUNNING

(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x0

C:\>sc query VMauthdService

SERVICE_NAME: VMauthdService

TYPE : 10 WIN32_OWN_PROCESS

STATE : 1 STOPPED

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x7d0

haiweiz · ‎10-01-2017

Your VMAuthdService is not running, I don't know the extract reason about it, but you can try to start it manually by:

In the "control panel"-> "System and Security"->"Administrative tools"->"Services", find the "VMware Authorization Service", right click and select start. Wait for a while and refresh, if you can see the service status change to Running, you are OK to run the VM.

hmdat · ‎10-01-2017

Thanks a lot Haiweiz, it works now

wtnyein · ‎10-19-2017

Thank you very much.. it's work.... :smileygrin:

AnUnknownUser · ‎10-22-2017

I'm also having this problem & none of these mentioned methods worked for me. Here are logs,screenshots. Can this problem be resolved? Please take a look at these files

Harwise · ‎10-22-2017

2017-10-23T03:45:03.789+05:30| vmui| I125: Cnx_Connect: Error message: Failed to connect to socket to vmware-authd (error 10013).

Connecting to authd failed and the error code was 10013. A Socket Error 10013 can and will occur if there are settings on your computer that are not properly configured. In many instances it is an anti-virus software that will either not scan your computer properly or will take too long to scan them and thus prompt the error. (see How do I fix error code 10013 for IE11 and windows 7? - Microsoft Community ).

AnUnknownUser · ‎10-23-2017

Thanks Harwise, It seems my anti virus is causing the problem.

bewing144 · ‎11-16-2017

This solved my issue. I was stuck on this for a minute, but this was EXTREMELY helpful! Thank you very much!

Taleb00 · ‎03-24-2018

Hi There,

I just faced a same problem, But I managed to solved by starting the following services:

VMAuthdService

VMnetDHCP

VMware NAT Service

VMUSBArbService

Good luck for all

laucha13 · ‎05-14-2018

Hi everybody ... I'm having the same problem here, VM Workstation 14 Pro (windows 7 pro vm on windows 10 pro Think Pad W541 i7 laptop).

"Unable to connect to the MKS: Too many socket connect attemps, giving up."

I used to run 3 VMs at the same time from an external SSD with no problems, thursday everything was well.

Friday I started having this issue, no new installation or windows updates done.

When I switch in "console view" I can see the VM is started, I can see the desktop but when I click inside to give focus, my screen becomes black. From this state I try pushing tab key to see if the keystroke is detected but when I go back in "cosole view" there is no change, same desktop icon has the focus.

Tried the following actions with no resuts:

- Deactivated firewall and antivirus

- Started all services described in forum

- Full uninstall and reinstall the VM Workstation 14 Pro

- Execute the VM form internal HDD

- Exectue other "template" VMs that I now work well

- The same VMs that are on my SSD and that doesn't works on this laptop, work well on another laptop

I add a .zip file with message print screens, logs, services status and about page.

Any comment will be greatly appreciated !!

Thanks for your help!

Peterku · ‎06-14-2018

It seems that the issue has been addressed but I would like to give a brief summary of how I did overcome this issue on My windows 10: The issue was: Unable to connect to the MKS: Too many socket connect attempts; giving up, and the VMauthdService was NOT even found in the /Services in my Win 10 after upgrading from Vmware Player 12 to then VMware-player-14.0.0-6661328.exe. I had to had encountered this error VMware NET HELPMSG 2185.
What I did after some reading:

1>> Deleted all VMs in the VMplayer( yeah, I wish there was a way to uninstall Vmware without doing this painful thing.)

2>> Reboot your PC

3>> Downloaded a fresh and latest VMware Player from this site. Downloaded this installer: VMware-player-14.1.2-8497320.exe ( link here: free )

4>> To REPAIR (or re-install) the PREVIOUS failed uninstalled VMwaplayer, I disabled temporarily My Windows Defender anti-virus and Internet connection by going Airplane mode (for security reasons) and run the setup installer for VMware-player-14.1.2-8497320.exe in Administrator mode, RUN the Installer and chose REPAIR of the previous installation instead of a fresh install.

5>> Once installed, I did recreate my GNS3 VM Linux and on rebooting the same issue persisted but this time the VMauthdService was reinstalled but NOT running as shown below on my CMD:
C:\WINDOWS\system32>sc query VMauthdService

SERVICE_NAME: VMauthdService

TYPE : 10 WIN32_OWN_PROCESS

STATE : 1 STOPPED

WIN32_EXIT_CODE : 0 (0x0)

SERVICE_EXIT_CODE : 0 (0x0)

CHECKPOINT : 0x0

WAIT_HINT : 0x7d0

6>> I did a reboot as someone had mention on the first reply and on Rebooting the PC host, I was able to use this great and awesome free software. Thanks to all esp Vmare team for a great support on your site. I hope that one day we can roll a simple cloud or microservices container such as docker on this Vmplayer app.

All

Workstation 14 Player MKS: too many socket attempts