Unable to connect to the vMA ESXi host

Similar Questions

• I have an error msg "Unable to connect to the firewall local host control" is displayed when the system boots

  OS - win7 family Basic 64-bit

  anti virus-macfee
   
  Original title: I have an error msg "Unable to connect to the firewall local host control" is displayed when the system boots. MacAfee antivirus, 1 GB Radeon graphic

  McAfee has been updated at the same time as the last batch of updates from Windows 7 and it seems to be the cause of this problem for most, if not all, users.

  See the communication from this "criticism" - McAfee

  Some customers may experience a loss of network connectivity and/or errors in McAfee Security Center after a recent update

  You should make the fix McAfee, if necessary. There are corresponding communications for their enterprise products.

  I got McAfee, but the connection has started working again on its own so I thought I was clear of problems. However, when I checked it says he was doing routine checks the updates in vain when I told it to do a manually. So stick with McAfee you don't follow their procedure of fix would have upgraded my PC at risk by not updated and, like other McAfee ads have since explained, the application did not refer to its database of threats correctly [and this could explain part of the variability of the symptoms of failure but all involved loss of internet connection]. Actually, I removed McAfee then installed Microsoft Security Essentials rather & my answer IE is faster I knew it [even though I had the Add-ons McAfee disabled for centuries].

  I had to run the removal of McAfee Development tool a few times before and it caused a problem with the license if the PC was not connected to the internet during the abduction. Due cat of McAfee support reset their files in order to allow the relocation-reactivation. Here is their link cat - McAfee - media contains the link to the cat

• Unable to connect to the server esxi vm via http

  I have installed esxi 3.5.0 update 3 on a hp dl380 g3 6 GB ram server. The installation was successful, and I set up an ip address and the root password.

  When I connect at this http://ipaddress/ , I get a request to enter the user name and password with the following in the window

  The server & lt; address ip & gt; level_15_access requires a user name and password.

  WARNING: This server is request your username and password sent precariously (basic without a secure connection).

  I enter the user name & lt; root & gt; and the password, but the guard window reappear. Finally, I get the following error: 401 Unauthorized

  Please can someone help?

  Thank you

  It would be vCenter Server.   The path above is actually on your install ESXi - if you enable SSH you could get to it.

• invoke VMScript unable to connect to the remote server

  I have two PCs, two win 7 x 64. PC1 has powercli 5.5 build 3142196 (5.5u2?) and the other who has now updated 6.0.0.7857 (last AFAIK) via VMware PowerCLI - 6.0.0 - 3205540.exe from the downloads section.

  On PC1, I can run the script

  invoke vmscript - ScriptText '(gwmi_win32_computersystem).manufacturer - like ' * vmware * "'-ToolsWaitSecs 45 - VM VMName - guestuser guestacct - guestpassword blablabla".

  and it works very well and gives me a result.

  If I run the same command on PC1, I get the error:

  Invoke-VMScript: 16/11/2015-18:32:01 VMScript Invoke cannot connect to the remote server

  on line: 1 char: 1

  + Call VMScript - ScriptText '(gwmi_win32_computersystem).manufacturer - like ' * vm...»

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: NotSpecified: (:)) [invoking-VMScript], ViError)

  + FullyQualifiedErrorId: Client20_VmGuestServiceImpl_DownloadFileFromGuest_DownloadError, VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScript

  Anyone encountered this before? I see no difference in the PC it would cause and I wonder if there are logs, etc. for troubleshooting, I'm not aware of. The message is a bit lacking in detail. Probably the client must connect something.

  Thank you!

  The client when you run the Invoke-VMScript cmdlet on must actually be able to connect to the physical ESXi host on which the virtual computer runs on port 443. Are two clients on the same subnet, you have a firewall between the hosts and guests? Just try to open the ESXi host welcome page in a browser from these two clients, e.g. https://myesxihost.local/

• vCenter Server displays the error message: unable to connect to the host

  vCenter Server displays the error message: unable to connect to the host

  Symptoms

  • vCenter Server cannot connect to a host when you perform operations such as:

  •

  o Storage vMotion

  o cold migration

  o cloning a virtual machine

  o the model deployment

  • Newspapers vpxd that contains an entry similar to:

  [2009-06-04 19:27:16.326 error "App" 4444] [VpxdInvtHost] IP address change for 10.223.122.143 to 10.223.127.197 unhandled, verification of the SSL certificate is not enabled.

  • You see errors similar to:

  Unable to connect to the host o

  o [2009-06-04 19:27:09.952 'Libs' 3902384 WARNING] [NFC ERROR] NfcNewAuthdConnectionEx: unable to connect to peer (numRetries = 2). Error: Unable to connect to the host 10.223.122.143: connection timed out

  • vCenter Server shows the VMS as being disconnected then connected.

  Hello

  Resolution

  Cause

  This problem can occur if an ESX host's IP address is changed while being managed by vCenter Server.

  Check the cause

  To check the cause of the problem:

  1. Log in as root to the ESX host using a SSH client.
  1. In the file etc/opt/vmware/vpxa/vpxa.cfg, find the IP address of the host. The entry looks like:

     
     10.21.48.121
     

     Note: for more information about editing the files, see installation in VMware ESX configuration files (1017022).

  Troubleshooting

  If the IP address is incorrect, perform the following steps in order. If the operation does not resolve the problem, continue to the next step. Don't skip a step.

  1. Disconnect and then reconnect the host:
  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Reconnect the ESX host in vCenter Server.
  1. Restart the VirtualCenter agent on the ESX host:
  1. Stop the service of vpxa with the command:

     # service vmware-vpxa stop

  1. Open the /etc/opt/vmware/vpxa/vpxa.cfg file in a text editor and correct the IP address of the ESX host.
  1. Start the service of vpxa with the command:

     # service vmware-vpxa start

     Note: for VMware ESXi, you may have to restart all the management agents. For more information, see restart the agents on an ESX or ESXi Server (1003490) management .

  1. Rebuild the VirtualCenter agent on the ESX host configuration file:

     Attention: this step removes all the Statistics counters historical host and the virtual machine. If VMware ESX host is running in virtual machines that starts in a permitted CVS environment, you maybe won't be able to add the host without stopping the virtual machines first.

  1. Right click on the ESX host in vCenter Server and click Disconnect.
  1. Remove the ESX host disconnected from vCenter Server.
  1. Backup the file vpxa.cfg with the command:

     # mv /etc/opt/vmware/vpxa/vpxa.cfg /etc/opt/vmware/vpxa/vpxa.oldcfg

  1. Add the ESX host disconnected to the server vCenter inventory.
  1. Run the following command to view the contents of /etc/opt/vmware/vpxa/vpxa.cfg and confirm that the host IP address is correct:

     # cat /etc/opt/vmware/vpxa/vpxa.cfg

• Unable to connect to the MKS: the certificate of the remote host has these problems:

  Hello

  We have a host of ESXi 4 cluster running any vSphere 4.1.  Recently, I started to upgrade to update 2 and all the additional fixes.  After the upgrade of the vCentre server to the latest version (or maybe before I can't noticed) an of are hosts began to show the following error whenever I tried to connect to the console of any guest on this host.

  Unable to connect to the MKS: the certificate of the remote host has these problems:

  It lists any problems at all and no error display in the event log that it simply does not work.  I had a prod around the internet and found nothing.  I then rebuilt the host to exclude and the problem remains.

  Any help would be much appreciated.

  Thanks in advance

  David

  If you can connect to the Console remotely using VMware Infrastructure (VI) Client connected directly to the host, take a look at vmware KB to connect to a remote virtual machine fails with the error: the certificate of the remote host has these problems

  but more generally - remove host to vCenter inventory and then add the host to the back, take a look at opening in the console of the virtual machine after a new installation of ESXi or ESX fails with the error: the host certificate chain is not complete and could not connect to the MKS: the certificate of the remote host has these problems

• Unable to connect to the host.   Error: The specified version is not found

  vmrun-t esx h https://192.168.1.123/SDK u root Pei password list

  Unable to connect to the host.

  Error: The specified version is not found

  Any ideas why it does not work?  It is run on a Windows XP workstation.  The target server is on the local network and running ESXi 4.1.  The vmRun version is 7.1.2 and is installed with Workstation 7.1.2.

  I also tried Ubuntu 10.04 with vmRun from a Workstation 7.1.2 installation.  There, he also fails with the same error.

  Note that ESXi 4.1 is used to test installation is not allowed and is running in demo mode.  Management of the vSphere client works without any problem the same Windows XP workstation.

  Any help would be appreciated.  Thank you.

  You must install the full package of VIX by http://communities.vmware.com/community/developer/downloads. It contains only components to manage the workstation. Please note that I had to install in the VIX 1.10.1 order then Workstation 7.1.2 to get both to work on my Windows 7 computer.

• Error code: 800ccc0e and the message "Unable to connect to the host server", when you set up Windows Mail to receive discussion group messages.

  I recently signed up for Windows Mail, Windows Vista Help. I have configured my Gmail OK account, but when I click TOOLS then Newsgroups I get the following error: unable to connect to the host server. When I click on show details, he said: Microsoft Community Server: msnews.microsoft.com Protocol: NNTP Port: 119 secure (SSL): 0 Code: 800ccc0e

  msnews. Microsoft.com has not existed for about three years now. MS close their news servers. You can still access newsgroups, but you will have to do with one another as eternal September or AIOE news server.
   
   

• Unable to connect to the MKS: address for server esx02.mgmt.domainname.dk host lookup failed: unknown error 11002 (0x2afa)

  I get the following error when I connect to my via Vsphere Vcenter and try to connect to one of my server with the console:

  Unable to connect to the MKS: address for server esx02.mgmt.domainname.dk host lookup failed: unknown error 11002 (0x2afa)

  I'm new to VMware, I can very well do a MSTSC server and work proberly.

  the VMwareTools are out of date, when I log on the server and try to update I get the following message:

  

  any ideas here?

  I discovered that it is related to DNS

  WSATRY_AGAIN

  11002 (0x2afa)

  It is usually a temporary error during hostname resolution and means that the local server does not valuationauront of response from an authoritative server.

  the issue was that the VMware system was on a different subnet, and the firewall (TMG) blocked. bring the RDP to the Vcenter server and vsphere then open works like a charm

• ' Could not connect: unable to connect to the host localhost: connection refused "on variuos orders

  On ESX 4.0.0 Update 1.

  When I run a command like "vim-cmd/hostsvc/hostsummary | "grep inMaintenanceMode" or vimsh - n - e/hostsvc/maintenance_mode_enter ' / 'vimsh - n - e
  "/ hostsvc/maintenance_mode_exit" all returned the same error message ' could not connect: unable to connect to the host localhost: connection refused.

  I checked the checked the file /etc/resolv.conf Bed & Breakfast.

  I am able to ssh on the server as well as the use of WinSCP without any problem.

  I can connect with the VI Client also without problem.

  Any ideas?

  The problem has been resolved.

  The fix:

  =====

  # vimsh-e - n/hostsvc/hostsummary | grep inMaintenanceMode

  Using the libcrypto, version 90809F

  inMaintenanceMode = false,

  # vim-cmd/hostsvc/hostsummary | grep inMaintenanceMode

  inMaintenanceMode = false,

  Rationality for the problem is these commands (vim - FCM or vimsh) were unable to communicate due to lack of xinetd process.

  # ps - ef | grep-i xinet

  root 11527 25978 0 04:30 pts/0 00:00:00 grep-i xinet

  # service xinetd restart

  #

  # Service xinetd status

  #

  # service xinetd start

  # Service xinetd status

  # /etc/init.d/xinetd ls

  /etc/init.d/xinetd

  / * But NETWORK seems to be normal on the server * /.

  # cat /etc/resolv.conf

  nameserver 172.26.6.21

  nameserver 172.25.6.51

  # ifconfig

  Lo encap:Local Loopback link

  INET addr:127.0.0.1 mask: 255.0.0.0

  RACE of LOOPING 16436 Metric: 1

  Dropped packets: 6053620 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 6053620 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:0

  RX bytes: 2021352939 (1.8 GiB) TX bytes: 2021352939 (1.8 GiB)

  ppp0 link encap:Point - to-Point Protocol

  INET-addr:164.152.87.72 P - t - P:164.152.87.64 mask: 255.255.255.255

  Up POINTOPOINT RUNNING NOARP MULTICAST metric MTU:1500: 1

  Fall of RX packets: 208 errors: 2:0 overruns: 0 frame: 0

  Dropped packets TX: 205 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:3

  RX bytes: 18165 (17.7 KiB) TX bytes: 22314 (21.7 KiB)

  vmnic100200 Link encap HWaddr 00: 1B: 21:6 A: C9:C4

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 1383869 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 1382815 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 90351869 (86.1 MiB) TX bytes: 92106912 (87.8 MiB)

  Interruption: 97

  vmnic100201 Link encap HWaddr 00: 1B: 21:6 A: C9:C5

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 24239456 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 23905751 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 2078777971 (1.9 GiB) TX bytes: 2226266024 (2.0 GiB)

  Interruption: 113

  vmnic100600 Link encap HWaddr 00:25:5 C: 2: 75:30

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 13076343 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 5226061 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 1292112365 (1.2 GiB) TX bytes: 1224021381 (1.1 GiB)

  Interruption: 129

  vmnic100601 Link encap HWaddr 00:25:5 C: 2: 75:31

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 819469 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 770101 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 56287946 (53.6 MiB) TX bytes: 52499576 (50.0 MiB)

  Interruption: 137

  vmnic110200 Link encap HWaddr 00: 1B: 21:6 A: CA:44

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 1774795 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 1681079 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 142435399 (135.8 MiB) TX bytes: 135079293 (128.8 MiB)

  Interruption: 145

  vmnic110201 Link encap HWaddr 00: 1B: 21:6 A: CA:45

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 21079616 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 20688606 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 1859632344 (1.7 GiB) TX bytes: 1852761835 (1.7 GiB)

  Interruption: 161

  vmnic110600 Link encap HWaddr 00:25:5 C: 2: 75:32

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 39205375 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 21339531 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 32420064542 (30.1 GiB) TX bytes: 3709579479 (3.4 GiB)

  Interruption: 177

  vmnic110601 Link encap HWaddr 00:25:5 C: 2: 75:33

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 2922150 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 2110634 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 398811808 (380.3 MiB) TX bytes: 245899848 (234.5 MiB)

  Interruption: 185

  vswif0 Link encap HWaddr 00:50:56:41:76:EB

  INET addr:172.26.6.13 Bcast:172.26.6.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Dropped packets: 109779 RX errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 23715 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 10137604 (9,6 MiB) TX bytes: 21716347 (20.7 MiB)

  vswif1 Link encap HWaddr 00:50:56:40:30:F7

  INET addr:172.26.7.11 Bcast:172.26.7.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 36515 errors: 0:0 overruns: 0 frame: 0

  Dropped TX packets: 4 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 3702390 (3,5 Mio) TX bytes: 168 (168,0 b)

  vswif2 Link encap HWaddr 00:50:56:4 A: DF:1 B

  INET addr:172.26.8.11 Bcast:172.26.8.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 20525 errors: 0:0 overruns: 0 frame: 0

  Dropped packets TX: 6 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 2742990 (2.6 MiB) TX bytes: 252 (252.0 b)

  vswif3 Link encap HWaddr 00:50:56:4E:1E:24

  INET addr:172.26.9.12 Bcast:172.26.9.255 mask: 255.255.255.0

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 26408 errors: 0:0 overruns: 0 frame: 0

  Dropped TX packets: 4 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 3095970 (2.9 MiB) TX bytes: 168 (168,0 b)

  # / opt/ft/bin/ftsmaint lsVnd

  Virtual network device (VND) groups

  ===================================

  Status of group name

  --------------------------

  vSwitch0 ONLINE

  vSwitch1 ONLINE

  vSwitch2 ONLINE

  vSwitch3 ONLINE

  Members of the Group of VND

  =================

  Link Group Name status Interface link state speed

  --------------------------------------------------------------------------

  vmnic100200 vSwitch2 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100201 vSwitch3 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100600 vSwitch0 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic100601 vSwitch1 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110200 vSwitch2 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110201 vSwitch3 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110600 vSwitch0 DUPLEX UP LINK 1000 Mb/s-FD

  vmnic110601 vSwitch1 DUPLEX UP LINK

  1000 mb/s-FD

  / * Further consideration on the problem of starting XINETD * /.

  Further examination shows that the xinetd is unable to start because he believed NETWORK unavailable.

  Starting xinetd uses the contents of the sysconfig file where there was an entry incorrect "NETWORKINcesv = yes". We have corrected this entry and restarted xinetd process.

  After this correction, xinetd is restarted, the system seems to be normal.

  # cat sysconfig

  NETWORKINcesv = yes

  HOSTNAME = Server.test .net

  GATEWAY = 172.26.6.1

  IPV6_AUTOCONF = no

  NETWORKING_IPV6 = no

  #

  # cat sysconfig

  Networking = yes

  HOSTNAME = Server.test .net

  GATEWAY = 172.26.6.1

  IPV6_AUTOCONF = no

  NETWORKING_IPV6 = no

  # ps - ef | grep-i xinet

  root 27977 25978 0 04:41 pts/0 00:00:00 grep-i xinet

  # service xinetd start

  [From xinetd: OK]

  # ps - ef | grep-i xinet

  root 28119 1 0 04:41?        00:00:00 xinetd - stayalive - pidfile /var/run/xinetd.pid

  root 28239 25978 0 04:42 pts/0 00:00:00 grep-i xinet

  #

  # service xinetd restart

  [Judgment of xinetd: OK]

  [From xinetd: OK]

  # vim-cmd/hostsvc/hostsummary | grep inMaintenanceMode

  inMaintenanceMode = false,

  # vimsh-e - n/hostsvc/hostsummary | grep inMaintenanceMode

  Using the libcrypto, version 90809F

  inMaintenanceMode = false,

  #

• Error created another Console service, unable to connect to the host by vSphere vCenter

  After creating an another Service Console unable to connect to the host by vSphere vCenter. How can I remove the now Service Console or make the old one further work well?

  Thank you.

  George

  This KB will show you the steps to re-create the Service Console, but you'll need to console or ILO access to the ESX host.

  http://KB.VMware.com/kb/1000266

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

  Twitter: http://twitter.com/mittim12

• Unable to connect to the shares of the host, Windows XP

  I cloned a VM XP base today.  The virtual machine was no shared folders enabled; I had problems with cloning of a machine with shared folders enabled, if I leave it on this virtual machine, that I keep around just to clone.

  When I try to activate the shared folders on the new virtual machine, I got this error: "could not update performance file sharing status: a message header has been altered or has the version incorrect." and I am unable to connect to the new action.

  I fixed the machine virtual and uninstalled and reinstalled extensions nothing doesn't.

  Any ideas what's happening?

  Version of Workstation 7.1.0 host and the guest XP SP3, update today.

  Hmm, I googled your error and did not find much.  Just some VIX-related stuff, which would be only bite you if you installed programs after the installation of VMware Workstation - of the 'old' VMware 'old' a programs may have installed obsolete libraries for automation of VIX.  Just after installing VMware Workstation/Player shouldn't cause a problem VIX.

  Question, you try to enable the records while the prompt is already on?  If so, what happens if you stop the prompt, select the files and then put on the client?

• migrate storage fails with 'unable to connect to the host.

  I'm trying to migrate storage of a virtual machine to a different data store. (on the same san)

  When I start work, I see the task:

  Moving the virtual machine / status 'in process '.

  After 10 minutes, I get 2 pop-up windows:

  -

  ---

  Error

  -

  ---

  Unable to connect to the host.

  -

  ---

  Ok

  -

  ---

  I tried to move the storage of another virtual machine, but I got the same error.

  Also tried a different vmhost (but same cluster), but also the same error.

  When you try to a host in a different cluster, it works without problem (same san/store data used in the cluster where I got the errors)

  There is no difference in the profile of security on the host computers.

  Any tips?

  Logfile attached (vpxd - 353.log) when I was running the migrate storage.

  Part of the error:

  2009-11-03 16:49:07.035 02464 info "App" (1257263347020035) VMotion began

  2009-11-03 16:58:35.903 02464 error "App" (1257263347020035) VMotion failed: vim.fault.HostConnectFault

  When it works ok:

  2009-11-03 17:29:49.470 02456 info "App" (1257265789470153) VMotion began

  Hello.

  See KB 1010837.

  Good luck!

• Unable to connect to the host server: a connection attempt failed because

  Hi all

  I install my host ESX server in vmware workstation.  It works fine except when I am creating virtual machines.

  I'm not able to install the operating system on the virtual machine and I get this error that appears inside the virtual machine.

  Unable to connect to the host server: a connection attempt failed because the connected party did not respond after a certain time, or established connection failed because connected host has no

  to answer.  Do you want to retry?

  My ESX server hosts have static IP addresses.

  I've seen a few similar posts on this issue, but their solutions have not worked for me.

  Best regards

  Nathan

  I think we confuse you.  ESX server is running like a machine virtual within the workstation, correct?  If Yes, then you must edit the vmx esx server with these entries monitor configuration file *.  They can go anywhere in the file.  Once those have been added, you should be able to run 32-bit virtual machines within the esx server.

  -KjB

  VMware vExpert

• "Unable to connect to the MKS: unable to connect to the host [servernamehere] failed on vSphere 4.0 and client.

  Anyone have this problem?  I loaded vSphere 4.0 host ESX 3.5 and everything seems to work very well yesterday, after sleep more testings and this error arose:

  "Unable to connect to the MKS: unable to connect to the host failed on vSphere 4.0 and client.

  After a google search, I could it is resolved by placing the DNS entries on the client machine c:\windows\system32\drivers\etc\hosts file point to my ESX host name and domain name FULL name runs and it worked fine.  I'm curious to know why this went well?

  What is MKS mean in this case?  Server key from Microsoft or the key management server?

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

  When you click on the console of a virtual machine, the server that hosts the vm responds back with its host name for your client to connect to.  Thus, the MKS console could not be connected to, and you could not see the virtual machine console, until you updated name resolution.  Given that the ESX host is back with a name, the customer could not resolve the name, if your client could not connect to the virtual computer mouse, keyboard, screen.  Hope that makes more sense.

  -KjB

  VMware vExpert