Unable to connect to the MKS: internal error

After you add the hosts to vCenter, when I try to KIKILA the VMRC, I get the error: could not connect to the MKS: internal error

First of all, this isn't the usual DNS resolution of Host IP addresses MKS error! This is something totally different.

An unusual thing in the manifestation of this problem which is to turn it off (completely off, not a reboot) and then turn the virtual machine in question, the console will work for this virtual machine, but the console continues to malfunction for the other virtual machines on the same host until these virtual machines are vMotioned or completely powered by bicycle!

Here's the workflow:

  1. I have to stand up a new ESXi (patched and firmwared to the latest updates)
  2. I build a Windows or Linux VM to serve DNS and/or be an AD domain controller
  3. I have install the VCSA (or Windows vCenter)
    1. I connect and test forward and reverse the resolution for all hosts in the Broadcast domain
  4. I add the ESXi host (and all other hosts) to vCenter
  5. I try to open a VMRC and get the MKS error!

It is a minor problem, with the exception of the VCSA himself!

Any ideas?

I had the same exact symptoms as you. Fortunately, I was able to find this link:

http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2116542

Looks like we have a need is power off and turn it back on, suspend and energy back or vMotion to another host to resolve. I guess it has to do with the generation of a new SSL certificate when joining a host to vCenter? I checked that at least the first two options work, so I hope that answers your question.

Tags: VMware

Similar Questions

  • 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:

    vmware tools error.jpg

    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

  • Unable to connect to the MKS: (name of user and password) Login incorrect

    I am trying to use the VMware workstation 12, connect to the server feature but I get this error message.

    My desktop pc (host) is running windows 7 and running VMware workstation 12. I shared one of my virtual machines. I have activate port, 443, 902 and 903 on my router. I temporarily disabled my firewall.

    When I try to connect to my laptop running Kubuntu and Vmware workstation 12 host, I am able to connect to the host, I am able to see my shared VM and I am able to turn on and off but that's about all. I can not actually use the virtual machine, because I get the message in the title.

    Can someone help me? Thank you.

    Found a solution.

    In the host (windows)

    Open Notepad as administrator

    Edit the file in:

    C:\ProgramData\VMware\VMware Workstation\config.ini

    Change:

    Authd.client.port = "903".

    TO:

    Authd.client.port = '902 '.

    Save

    Unable to connect to the MKS: Login (user and password name) incorrect - Spiceworks

  • Unable to connect to the MKS: the operation is not allowed in the current state

    Hi all

    After the upgrade of vmware tools, we have a problem while safeguarding a guest vm with avamar. VM freezes and he said; "Unable to connect to the MKS: the operation is not allowed in the current state.  It can be stopped only by killing the task in the service on the host esx console.

    VMware vCenter Server 5.1 - 5.1.U1b - 1235232

    2013 12-19 T 00: 49:15.146Z | vCPU-1 | W110: MONITOR PANIC: vcpu - 0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

    2013 12-19 T 00: 49:15.156Z | vCPU-1 | I120: Core dump with construction build-1065491

    2013 12-19 T 00: 49:15.156Z | vCPU-0 | I120: Exit vcpu-0

    2013 12-19 T 00: 49:15.156Z | vCPU-1 | W110: Writing monitor corefile "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmmcores.gz".

    2013 12-19 T 00: 49:15.202Z | vCPU-1 | I120: Save the anonymous memory

    2013 12-19 T 00: 49:15.209Z | vCPU-1 | W110: Dumping core for vcpu-0

    2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: CoreDump: dumping core with superuser privileges

    2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: VMK battery for vcpu 0 is 0 x 412248155000

    2013 12-19 T 00: 49:15.209Z | vCPU-1 | I120: Start monitor coredump

    2013 12-19 T 00: 49:16.454Z | vCPU-1 | I120: End monitor coredump

    2013 12-19 T 00: 49:16.455Z | vCPU-1 | W110: Dumping core for vcpu-1

    2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: CoreDump: dumping core with superuser privileges

    2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: VMK battery for vcpu 1 is at 0x4122481d5000

    2013 12-19 T 00: 49:16.455Z | vCPU-1 | I120: Start monitor coredump

    2013 12-19 T 00: 49:17.420Z | vCPU-1 | I120: End monitor coredump

    2013 12-19 T 00: 49:17.421Z | vCPU-1 | W110: Dumping extended monitor data

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | W110: A core file is available in "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmx-zdump.000".

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: Msg_Post: error

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: fatal error [msg.log.error.unrecoverable] VMware ESX: (vcpu-1)

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120 + vcpu - 0:NOT_IMPLEMENTED devices/vide/iovmk/videVMK-vmkio.c:1492

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.haveLog], a log file is available in "/ vmfs/volumes/4ff12f8d-9d4d7a89-9341-e4135bb796b4/TEADEV/vmware.log".

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.requestSupport.withoutLog] you can ask support.

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.requestSupport.vmSupport.vmx86]

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120 + to collect data to be submitted to the technical support of VMware, run 'vm-support.

    2013 12-19 T 00: 49:31.966Z | vCPU-1 | I120: [msg.panic.response] we will respond on the basis of your entitlement to support.

    We realized that the problem is our url filtering service checkpoint firewall. When we have disabled all begins to work very well.

  • 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 MKS: invalid default VIM connection

    As a result of a hardware failure, we have rebuilt our VC and guests now have a little exclamation point and show the error "unable to connect to the MKS: VIM invalid connection fault.

    This could be due to the version of the db you have, it might be an older version. You could rebuild the db from scratch, if you have problems because it s almost like a clean install. (You would lose however inherited events) depends on how much you need of these

  • vCenter on Windows Server 2008 cannot open VM´s. unable to connect to the MKS console: Timeout during an attempt to read

    I have setup a new vCenter to replace the old (new on MS server 2008, an old man on MS server 2003), but after registering the VM´s, I am not able to connect to them with the console. Error message: unable to connect to the MKS: Timeout during an attempt to read

    If I connect directly to the host ESX 4 it works fine.

    Is that what someone has any ideas, how to solve this problem? I have already tried:

    -Added the new vCenter address and IP to the/etc/hosts

    -restart the ESX servers

    -Re-installed VMware tools to the new vCenter

    None of the above has helped, and I start to desperate... Anyone have an idea?

    If you use vcenter to manage your servers from another computer. You should try to disable the windows firewall on the vcenter computer that manages the esx server. He worked for another problem in the past. Windows firewall started blocking applications of mks someday and we don't know why. Allowing exceptions in windows firewall did not work if the firewall has been turned off completely and then it worked.

    (Please allow points)

  • "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

  • "Unable to connect to the Skype server" error on samsung wave 723

    I got Skype Lite (or the Java thing, whatever we call it - does not allow calls - only CAT) on my Samsung Wave 723 for more than six months. Earlier this week he suddenly disconnected me and when I tried to log in again it showed this error "Unable to connect to the server of Skype." almost immediately after, I started signing in. I tried to reset the settings in Skype, my phone settings, I took out the battery and reset even WiFi. Then I tried to connect with a few other WiFis - still the same error. My friend has the same version of Skype Lite on his cell phone, and it works very well and without errors.

    Anyone know how to fix this error? It is urgent, please.

    Solved the problem on my phone. I just had to add the area code to my phone number in the connection menu.

    @yousef8824: I downloaded my Skype Java one of those ages of links it is a. not useful at this time.

  • Unable to connect to the server Essbase (error #1051293)

    Hello

    Using Essbase Integration Services Consol, I created a template OLAP, and then click OLAP Metaoutline and even checked. But when I tried to load the members and the data I just had an error that is "unable to connect to the Essbase server: Localhost (error #1051293).

    If any of you have solution for this issue, so kindly help me.

    Saami

    Do you know who your security Admin? Or at least you have access to Shared service URL?

    In LDAP, type your user ID and you see your start-up. Add the new app to your user ID, and you define.

    Essbase Administration Services to help online

  • 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.

  • Unable to connect to the wireless network, error message "Windows could not finish repairing the problem because it is impossible to perform the following action. Renewal of your IP address.

    Original title: Unable to connect to the wireless network

    Unable to connect to the network wireless Toshiba Satellite A105 PC running Windows 7.  "Windows could not finish repairing the problem because it is impossible to perform the following action. Renewal of your IP address.  Works with Windows XP SP2, IE 8.00.6001.18702 file, I think that Version 3.  It has been installed on a disk provided by Microsoft after that old installation became corrupt (in the sense of Microsoft technical support.)  Before that, wireless network worked well.   (So unable to connect to the Internet for updates.)   Have tried to change the other settings and different messages acquired when it SHOWS that I am connected but cannot connect because of something to do with the certificate.  I don't remember what I did to try to solve this problem in the last days.

    I should add that I have tried the solutions of the previous forum on this topic, and none worked.

    Hi Marilynnla,

    Sorry to hear about the bad experience you encounter. Lets see if the network problem can somehow be archived.

    Read this article and follow the steps. Lets see if it helps in any way.

  • Unable to connect to the Internet, receive error message: DEBUGER END WIRE.

    Original title: unable to connect to the Internet

    Hello

    I am using Dell inspiron 1525 with Win.Vista Home Premium 32 bit

    When I connect to internet I displays message DEBUGER CANCEL THREAD

    There is no driver problem

    Someone help me

    I thank & regard

    Satish Baker

    Hi Sissi,

     

    1. you are using a wired or wireless?

    2. do you and changes to the network card or manually change all the settings?

    3 when was the last time it worked?

    4. are you tring to set up internet connection in windows vista for the first time?

    Please follow the links below to solve the problem.

     

    Windows wireless and wired network connection problems

    http://Windows.Microsoft.com/en-us/Windows/help/wired-and-wireless-network-connection-problems-in-Windows

     

    See also this: the problems of Internet connection

    http://Windows.Microsoft.com/en-us/Windows-Vista/troubleshoot-Internet-connection-problems

     

    I hope this helps!

  • Unable to connect to the Internet - DNS error - Windows 7

    Hello

    I have a new (3 months) desktop XPS from Dell with Windows 7 (64-bit), the Motorola SBG6580 Wireless Modem/Gateway and Comcast is my ISP.

    My computer is connected to a modem with an Ethernet cable. Nothing unusual in the installation program. I just plugged my PC and it worked.

    In the last three months everything worked well. Then all of a sudden, from Friday last I can no longer access the internet.

    The connection at the bottom right shows that I'm connected, and every few minutes a yellow exclamation icon above him. Some sites Web opens very, very slowly, some are open to all and another just give a straight error that I'm not connected. It's weird - I can connect to the first seconds when I restart the computer and the speed is extremely fast, and then all of a sudden I can't connect.

    When I right click on the connection icon for helps out sometimes it says "The DNS does not" and sometimes he can't detect any problem (but I can still access all Web sites).

    Now, I also connected with Ethernet cables to the modem game both consoles and they work very well - I can get online, play games, stream movies etc. My wife and I can also connect our iPhones over Wi - Fi, and I can also connect my laptop running Vista by Wi - Fi.

    The problem is just the Windows 7 PC.

    I already googled the problem and tried all the solutions offered - I rinsed and renewed the DNS using the commands ipconfig, I put the DNS manually but nothing seems to work!

    Could this be a virus any? I have McAfee running and I did a scan, but it does not detect. My feeling is that there is a virus which changes the DNS.

    Any suggestion on how I can confirm to you, or what other measures can I take?

    Thank you!

    Hello

     
    Perform the steps mentioned below and check if the problem persists.
     
    a:  Click on start and then Control Panel.
    b: go to work in network and sharing Center and then click on change adapter settings.
    c: right click on Local area connection and select Properties.
    d:  Select Internet Version 6 protocol, and then click Properties.
    e: choose DNS servers obtain address automatically, then press Ok.
    f: choose address automatically get IP.
    g: repeat the steps for Internet Protocol version 4 as well.
     
    Hope that helps.
  • Unable to connect to the MKS: unable to connect to the server [hostname]: 903

    Hello

    * I installed esx 4.0 within a vmware desktop 7.

    * whenever I try to open an OS Fords under army exh via VI client I get this error message.

    * I can ping from the host esx server but I can not telnet the BONES on the 903 host port.

    * I have reset the firewall configuration to allow everything on the esx server still the same thing.

    * can I get help on this.

    I want to build some virtual machines under esx server. This error is not to let that happen.

    Try to stop the firewall on the ESX host, as well as on the computer where you run VI client.

    If possible please delete the firewall between the two, then try to connect using the VI client. If it does not connect remove the firewall between a connection attempt

    In this way, you can locate the problem if it is with the firewall or the server itself.

    To stop the firewall on ESX run below command

    esxcfg-firewall - allowincommin - allowoutgoing (this is for ESX4)

    Firewall service stop (that's ESX3)

    Also follow the KB article

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=749640

Maybe you are looking for