Tag Archives: console session

Possible bug in VMware Client

Posted on by

KB ID 0000413

Problem

Unable to use multiple console sessions in Windows 7.

1. Seen on Windows 7 x64 Ultimate, with and without aero enabled, on two separate machines.

2. Happens if connected to VCenter OR directly to ESXi (build 4.1.0, 260247)

3. Does NOT happen with the same software from Server 2003. (Same systems, same vesion of the VI client).

4. Does NOT happen on Server 2008 R2 Standard x64 (Same systems, same version of the VI client).

5. Does NOT happen on Server 2008 R2 Standard x64 with Service Pack 1 (Same systems, same version of the VI client).

6. Does NOT happen on Server 2008 R2 Standard x64 aero Enabled with Service Pack 1 (Same systems, same version of the VI client).

7. Does NOT happen on Windows 7 Enterprise (Service Pack 1) x86 (Same systems, same version of the VI client).

Description

 

Related Articles, References, Credits, or External Links

NA

Cannot Open a Console Session in the VMware VI Client on Windows 8

Posted on by

KB ID 0000677 

Problem

Mostly my conversion to Windows 8 has been pretty painless, the only thing that wont work is the VMware VI client cant open a console session to the VMs on my ESX server.

Error
The VMRC console has disconencted…attempting to reconnect

This happens because the IE10 that comes with Windows 8 does NOT LIKE the requests the VI client is sending to the Internet Explorer plug-in.

Update 08/03/13 – This problem has now been fixed! Download the latest 5.1 version of the VI client. (see screenshot).

Solution

Work-Around 1 Use VMware workstation (Note: scroll down for a permanent fix)

Until either Microsoft or VMware change something then we are stuck! however there is a work around. if you have VMware Workstation (download the trial it will keep you ticking over till the problem is fixed!).

1. Launch VMware workstation > File > Connect to Server > Enter your ESX/vCenter server details > Connect.

Note: You may need to accept the certificate warning if you are using self signed certificates.

2. Now you can open a console session to your virtual machines.

Work-Around 2 Use VMware Guest Console

Download and run VMware Guest Console > Connect to to a host or vCenter, and you can access the guest machines consoles from there.

Permanent Fix

Sorry, the only way to fix this (at time of writing) is to upgrade to vSphere 5.1 AND install the 5.1 version of the vSphere client. (You can’t point the 5.1 client at a 5.0 host, it automatically launches the 5.0 version of the VI client).

Note: You will need to update vCenter to 5.1 as well for that to work!

Problem Resolved

Update to the latest VI client, and the problem will cease.

 

Related Articles, References, Credits, or External Links

NA

VMware VI Client error ‘Unable to connect to the MKS: Failed to connect to server {ESX-Host}:902’

Posted on by

KB ID 0000815 

Problem

Seen when connected to the VMware VI client software, and attempting to open a console session with a virtual machine.

Solution

This is a pretty generic error, for whatever reason the client software cannot connect to the KMS (Keyboard, Mouse, and Screen).

In NEARLY every case this is a communication issue, either the machine running the client software cannot resolve the name of the ESX host that is hosting the virtual machines, or TCP Port 902 is being blocked by a firewall.

1. If you can’t simply pop the correct name in your DNS, then add the name and IP to the machines, (the one running the VI client software) host file. You will locate this in;

[box] C:WindowsSystem32Driversetc [/box]

2. Open it with Notepad, and add the IP and name of your ESX host(s), Note: I’m also putting the name and IP of my Virtual Center server as well. Save the file and try again.

3. You should now be able to connect.

It’s NOT DNS!

If you can happily resolve the name and are sure that the port is not being blocked, then have you made any IP changes? Is the default gateway on the ESX Server set correctly? And finally restart the management agents on the host, either from the console, or by running ‘/sbin/services.sh restart’.

I’ve also fixed this error by shutting down the machine > removing it from the inventory > then browsing the storage, to locate the .vmx file > then simply import it back again.

Related Articles, References, Credits, or External Links

NA