VMFAQ.com - FAQing about virtualization since 2008
Search:     Advanced search
Browse by category:
Contact Us

Unable to connect to MKS: Host address lookup for server

Add comment
Views: 28728
Votes: 7
Comments: 0
Posted: 26 Jul, 2009
by: Troen L.
Updated: 26 Jul, 2009
by: Troen L.

When the client pc where the viclient is installed can't resolve the dns name of the esx host you get the following when trying to open the console of a VM:

To resolve this issue you should ensure that the client can resolve the name of the ESX server (for example by using ping from the command line of the client pc).

Check that the client has similar dns settings as the virtual center server. It's also possible to manually edit the hosts file if the DNS host serving the ESX environment can't be used.

This dns requirement exists in version 3.0.2 and newer.

Others in this Category
document I have 64bit CPU but I can't boot/install 64bit guests?
document My VirtualCenter database is huge and slow, can I purge it?
document Can I grow an existing virtual disk (.vmdk file)?
document Upgrading from ESX 4.1 to ESXi 5 fails: The specified network interface card is not plugged in. Installation cannot continue as requested.
document Recommendations for template virtual machines
document After cloning a Debian/Ubuntu VM, the guest network is not working
document Active Directory and VMware snapshots
document "This installation package is not supported by this processor type." when installing vCenter 4.1
document Need to mount a snapshotted LUN or a LUN that was suddenly lost
document "Invalid DSN" when trying to install 64 bit vCenter Server
» More articles



RSS