Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

VMware: Unable to connect to the MKS

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

VMware: Unable to connect to the MKS

Postby guest » Mon Jun 03, 2013 10:27 am

Situation: The client has VMware 4.1. They can't access the VM with thi smessage: "Unable to connect to the MKS: Connection handshake failed for mks of .....". The Recent Tasks also shows: Reset virtual machine Status: 95%. You don't have options to power it off and shutdown.

Troubleshooting: 1. Try to re-build the VM using the same VM file.

2. vmx file may be corrupted. Re-create a new VM.
Last edited by guest on Mon Jun 03, 2013 11:09 am, edited 1 time in total.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: VMware: Unable to connect to the MKS

Postby guest » Mon Jun 03, 2013 10:44 am

I found some suggestions in the Internet:
1) Edit the settings of the virtual machine, click the Options tab and make sure that the guest operating system version is correct. This can cause this error, so make sure you select the correct OS. E.g. “Microsoft Windows Server 2008 R2 (64-bit)”.
2) Try removing the virtual machine from the vCenter inventory and re-adding it.
3) Try restarting the VMware management agents (service mgmt-vmware restart and service vmware-vpxa restart).
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: VMware: Unable to connect to the MKS

Postby guest » Mon Jun 03, 2013 11:08 am

VMware website has an article. It states that could be firewall issue. Try these:
1.Log into vCenter Server directly through Terminal Services or a Remote KVM and attempt a connection using the vSphere Client from this system. If this method works, the firewall may be preventing the console from working.


2.Configure your firewall to allow communications between the ESXi/ESX host and the workstation running the vSphere Client using port 903. For more information, see Testing port connectivity with Telnet (1003487).

If port 903 is not open or cannot be opened in your environment, enable the vmauthd proxy. This forces remote console communication to be sent on port 902 on the Service Console, instead of 903.

Note: By enabling this setting there may be degradation in the performance under heavy usage while communicating to the ESXi/ESX host service console.

To enable the proxy:

a.Log into the ESXi/ESX host's service console as root.
b.Open /etc/vmware/config using a text editor.
c.Add this line to the file:

vmauthd.server.alwaysProxy = "TRUE"

Note: In ESXi 4.x and 5.x, vmauthd.server.alwaysProxy is, by default, set to true.


d.In ESX, run this command to restart xinetd:

service xinetd restart



3.Verify the ESXi/ESX firewall policy:

◦For ESXi 5.0, see About the ESXi 5.0 firewall (2005284).
◦For ESX 3.x to 4.x, see Troubleshooting the firewall policy on an ESX host (1003634).


4.Verify that the ESXi/ESX host and the workstation running the vSphere Client are correctly synced to an NTP service. This is required to satisfy SSL handshaking between the vSphere Client and the ESXi/ESX host. For more information, see Verifying time synchronization across an ESXi/ESX host environment (1003736).


5.DNS problems are a common cause of virtual machine console problems. Verify name resolution in your environment. For more information, see:

◦Identifying issues with and setting up name resolution on ESXi/ESX Server (1003735)
◦Configuring name resolution for VMware vCenter Server (1003713)


6.After verifying DNS, open a command prompt on the vSphere Client machine and run these commands:

ipconfig /flushdns
ipconfig /registerdns


7.Ensure that the VMware ESXi/ESX host has enough disk space in /var and other required partitions. For more information, see Investigating disk space on an ESX or ESXi host (1003564).


8.Verify that the permissions for the virtual machine's .vmx file are set correctly. To set the permissions, run the command:

chmod 755 full_path_to_virtual_machine.vmx


9.If your ESX host has more than one service console configured, verify that they are not on the same network. For more information, see ESX 4.x hosts lose network connectivity when multiple service console interfaces are configured on subnets that use DHCP IP addresses (1010828).


10.Check if the Service Console IP is routing traffic to the workstation running vCenter Server. For more information on configuring the Service Console Gateway, see Changing the IP address, default gateway, and hostname of the Service Console in ESX (4309499).
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 4 guests