VMWARE Workstation 11 failed to connect to server. Server is an unknown server. VMware Workstation cannot connect to this server.

[CossakTarasBulb]

Guys,

On my home lab, where i have a simple router (Netgear Nighthawk R7000) and two workstations after updating to WS11 i cannot connect one PC to another.  On 10 i had many shared vms on one pc, and would connect from my main box and run them.  I get this error: VMWARE Workstation 11 failed to connect to server. Server is an unknown server. VMware Workstation cannot connect to this server.

If i replace the name of the pc with the IP it will connect.  I did not have this issue on WS10.  I uninstalled 10 and recreated my old set up and still have this problem.....

I can connect with IP for the DNS name; however, I want to know whats going on and if this bug will be fixed.

Any advice?

[xindayu]

Hi CossakTarasBulba,

Thanks for using Workstation!

Does the DNS server work well on your lab?

Thanks!

[CossakTarasBulb]

Yes, I use my router as the DNS and DHCP server.

I dont have any issues pinging one box from another.

I also reverted back to Workstation 10, and I do not have this issue.

[xindayu]

Do you have "Connection-specific DNS Suffix" on your PC?

If so, would you please try the full name instead of the short name?

For example, try "aaabbb.eng.com" instead of only "aaabbb".

Thanks!

[CossakTarasBulb]

My Lab is outside of a domain environment.  Its simply dictated by the DNS/DHCP router.

So in my case will be just the actual system name without the .xxx.xxx

And as i stated, i never had the issue in 9 nor in 10...

I have also tested the issue at my company with a normal domain

And adding COMPUTER.XXX.XXX did not make a difference.

So 2 different environments same issue, that did NOT exist on version 10 and 9

[boomshankerx]

Bump. I am also experiencing this issue. I'm running bind9 and all other programs are responding to DNS queries correctly. VMWare Client is able to connect via name but not workstation 11

[CossakTarasBulb]

Tested today on the .2 update. Still the same issue! Come on VMWARE! fix this stupid bug!

[CossakTarasBulb]

Do you have any news regarding this by chance?

[xindayu]

Would you please provide the log files so that we can investigate it further?

Steps:

1. Launch Workstation, reproduce the issue.

2. Check the UI file(location at: "Help" -> "About VMware Workstation" -> "UI log file").

Would you please upload it?

Thanks a lot!

[BorDel]

Hi CossakTarasBulba,

In my case, i solve this problem by disabling use proxy server (Set "No proxy" in "Edit->Preferences->Updates->Connection Settings").

[CossakTarasBulb]

Here you go, clean log. i generated it today.

[canterbury]

I am experiencing the same issue with VMware Workstation 11 for Linux: none of my virtual machines can get internet anymore, it's ridiculous.

Things I tried: (A) Re-installing VMware tools in the guest, (B) Removing and re-adding the ethernet adapter, (C) Switching between NAT and Bridge, disabling and enabling, (D) Trying to troubleshoot the problem inside the guests (but note that this problem affects all guests of different OSes), (E) Re-installing the entire VMware product.  None of these approaches helped.  Everything worked fine just until I upgraded VMware workstation.  There is NO port blocker, NO anti-virus product, nothing.  This problem renders the entire product essentially useless.

I suspect that the problem is down to a problem with the way the DNS information is communicated to the guests via VMware's internal DHCP server.  But I don't know for sure.  I'm quite upset, I really don't have time for this.  Can some developer please sort this out?

Please help.

[ntwalkert]

I believe we may be having a similar problem. See my post vmware-workstation-server will not start after reboot

Workstation 11.1.2 build-2780323 on Ubuntu 14.04 LTS

[CossakTarasBulb]

I dont think its a similar problem but could be related.  Our Server works you just have to connect to it via a direct IP and not via a DNS name, so in a DHCP lease environment its a pain in the ass unless you have static ip.  However, personally my workstations are not on server vlans so set static ips are out of the questions.  I am surprised we are such a small community of users who found this error.  VMWARE! HELP!

[MarianGalieAndr]

I am experiencing the same issue. I can not connect via hostname! DNS is fine, i can ping by hostname properly. I can connect to the vmware workstation server only via IP.

This issue needs to be solved ASAP!!!! ! ! ! !@

[admin]

Hi CossakTarasBulba,

I'm a developer in the Workstation team, and I am looking into this issue. But there are a few details that are missing in the logs. Would you mind reaching out to me via e-mail so that I can work on a fix?

Thank you,

spolpaya@vmware.com

[CossakTarasBulb]

SO EXACTLY THE SAME ISSUE IN WORKSTATION 12!!!!!!!

250$ piece of software that has exactly same problem as 11? So instead of fixing the old faults, you release 12 and you charge 250 fee with supposite improvements! This starts to seem like a VMware upgrade rip off model. This is shameful!!!!!!!!

[tuaris]

I've recently upgraded to the Workstation 12 Pro evaluation and have lost the ability to connect to my VCenter 5.1 server.  It worked fine on 10.x and 11.1.0 build-2496824.  With 12.0.0 build-2985596 I get the following error:

2015-09-13T09:11:40.304-04:00| vthread-7| I125: POLL: deleting entry 9E089D0 for invalid fd 664
2015-09-13T09:11:40.304-04:00| vmui| I125: HTTP: BasicHttp error 5
2015-09-13T09:11:40.314-04:00| vmui| I125: HTTP: BasicHttp error 5
2015-09-13T09:11:40.314-04:00| vmui| I125: Failed to parse the JSON response: <unspecified file>(1): expected object or array
2015-09-13T09:11:40.314-04:00| vmui| I125: JSONBuilder::GetLocalizedErrorMessage: Unknown error id .
2015-09-13T09:11:40.316-04:00| vmui| W115: Failed to connect to 10.8.8.2. 10.8.8.2 is an unknown server. VMware Workstation cannot connect to this server.
2015-09-13T09:11:40.316-04:00| vmui| I125: DlgUI: Failed to connect to 10.8.8.2. 10.8.8.2 is an unknown server. VMware Workstation cannot connect to this server.

Here is what the logs says on 11.1.0 build-2496824

2015-09-13T09:19:59.047-04:00| vmui| I120: Resolving IP address for hostname 10.8.8.2
2015-09-13T09:19:59.047-04:00| vmui| I120: Resolved to 10.8.8.2
2015-09-13T09:19:59.059-04:00| vmui| I120: SSL_SetVerifyCb: ctx=3D10800 func=6CC24A80 data=6C917E0
2015-09-13T09:19:59.072-04:00| vmui| A115: GVmomi: Instantiating VMOMI session at https://10.8.8.2/sdk
2015-09-13T09:19:59.072-04:00| vmui| A115: GVmomi: Verifying SSL certificate with thumbprint 83:64:72:56:56:1F:AB:15:0C:C6:5D:30:C4:5B:38:4F:55:CB:33:2D
2015-09-13T09:19:59.072-04:00| vmui| A115: GVmomi: Certificate accepted
2015-09-13T09:20:14.496-04:00| vmui| I120: Connected to server: VMware vCenter Server 5.1.0
2015-09-13T09:20:14.528-04:00| vmui| I120: CVMUIApp::OpenTabInt: opened folder:root
2015-09-13T09:20:14.531-04:00| vmui| I120: Switched to tab: folder:root
2015-09-13T09:20:14.545-04:00| vmui| I120: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.
2015-09-13T09:20:19.593-04:00| vmui| I120: CVMUIApp::MenuButtonClicked: 11905 folder:root

I don't have a log for 10.x, but if needed I can downgrade.

[AdamShepherd]

Good afternoon,

Did you manage to find a resolution for this issue as from my log files i appear to be getting the same error.

Thanks

Adam

[CossakTarasBulb]

I dont think anyone cares about this issue anymore, I just gave up and have a notepad of IPs to know what hosts what....

12.0.1 just came out, still same issues exists. :smileyminus: to vmware, but since no alternatives available eh well...