Vmware vmrc ошибка подключения
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Cloud & SDDC
- :
- vCenter
- :
- vCenter™ Server Discussions
- :
- The VMRC console has disconnected.. attempting to .
jslarouche
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Seeing this error on my Virtual Center client while tryign to get to the console.. We are running Virtual Center 5.0 Build 455964
Anyone now how to fix it?
Virtualinfra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Please paste a screen shot in here.
DanWebb85
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I'm getting the same message when you open the console to any VM in the vSphere -client 5.0.
satya1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
DanWebb85 wrote:
I'm getting the same message when you open the console to any VM in the vSphere -client 5.0.
have you rebooted ?
pasquito
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
When i try to open a console-screen of a VM a will receive the following error : The VMRC console has disconnected. attempting to reconnect. The screen stays black.
Client : Vsphere 5 Client version 5.0.0-455964
Virtual Machine : Windows 2003 R2 32 bits
I get the error when I attempt to open (in this case) a Windows 2003 VM from my desktop, which is running Windows 7 64-bit with Vsphere 5 Client version 5.
This error is recent, because until a few days ago was to access these VM normally.
Anyone who knows a solution for this case?
J3anss0n
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Im seeing the same issue but only with the console tab, I have no issues when using the open console option to get the console in a separate window. Thats been our workaround so far
ph0bia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
We experienced this issue on Windows XP workstations immediately following the installation of Microsoft Visual Studio. Neither the Console tab or the Console window would work, both reporting the error that "The VMRC console has disconnected, attempting to reconnect" using the vSphere 5 client.
It seems that the installation of Microsoft Visual Studio overwrites or breaks something related to vSphere Remote Console access.
Solution: Re-installing the VMware vSphere client on the affected systems resolves the problem.
ph0bia
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
We have actually experienced the problem again since then, where MS Visual Studio was not a factor, in this scenario I powered off the VM and migrated it to a new host, then powered it back on and the problem was resolved.
SandyB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
has anyone found a fix for this issue?
Virtualinfra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Just to summaries the work around given so far are as follows
1. Reinstall the vsphere client on the affected system
2. reboot the VM
3. move the VM from one host to another host and reboot.
4. open console in separate window and see..
But dont see a fix for.. let see if we get some input from any expert here for this..bouncing this up..
ChipSharpDotCom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I had this problem after I upgraded my VMWare server to 5.0 from 4.1. I found that installing the 5.0 vSphere client did not upgrade from the 4.1 client. I had to uninstall both 4.1 and 5.0 and reinstall just the 5.0.
Hope this helps somebody.
mwpreston
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Did you reboot the machine running the console.
I had a couple of hung vmrc processes in my task manager, I killed those, restarted the client, everything worked fine again
ala139
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Thanks mwpreston. your solution worked for me.
rodnikosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
i had the same issue,
If you have a web cam in the guest computer that runs the cSphere client:
* kill the proces called "fixCamera.exe".
* stop the host server
* close the vSphere client.
* open it again and try again.
Problem solved for me.
canadavirt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I got that error yesterday and I fixed it.
Even after several reboots. no progress. I removed the VClient from my vCenter Server and put it again. I figured this out when I tried connect into my Host by another vClient and worked fine. So the problem was on my VCenter Server.
VSphere Client Version 5.0.0 Build 455964
VMWare vCenter Server Version 5.0.0
cloudsmith
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I had this exact issue, and interestingly enough while i was loading Visual Studio 2010 on a Win 2k8R2 VM. So i'm assuming something in the Visual Studio load causes an issue with the vSphere client.
At any rate, the same error happend "VMRC console has disconnected.. attempting to reconnect". Even when i tried to power off the VM it hung at 95%. I was about to ssh into my esx host to kill the process for the VM when i saw this post and checked the processes running on my PC. Thank you for saving me some head ache pain.
I did not have to reinstall or reboot. I just had rogue vmware_vmrc.exe processes running. I killed them from the task manager and the issue was resolved.
I had upgraded my laptop from Windows 7 to windows 8 Release Preview. when ever open Vsphere client it couldn't shows the virtual machine instead of showing "The VMRC Console has Disconnected.. Trying to reconnect". I tried reinstall but the issue remain the same.
What can go wrong and how to fix it
Some of the MKS errors (for instance, vmware unable to connect to the mks internal error) you might see are as follows:
- Error connecting: Host address lookup for server failed: The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
- Error connecting: cannot connect to host : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because the connected host has failed to respond.
- Error connecting: You need to execute access in order to connect with the VMware console. Access denied for config file.
- Unable to connect to MKS: Failed to connect to server IP:903.
3. Free Disk Space
If firewalling and DNS are not the culprit, verify that the partition where /var lives has enough free disk space. To do this, run df -h from an SSH session on the ESXi hosting the VM you’re trying to remote console to. Make sure that the partition where /var is located is not full.
Checking for free disk space on ESXi
Another command you could use is vdh -h .
Making sure /var has free disk space using the vdf -h command
Conclusion
Being able to remote console to a virtual machine is, of course, an integral part of any admin’s job. Seeing the dreaded “Unable to connect to the MKS” message and being able to console can be highly frustrating more so when you need to fix something fast. In most cases, the problem lies with a firewall blocking one or more required ports and missing or bad DNS entries. For the rest, it’s usually enough to vMotion a VM to another host or restart the management agent on ESXi.
If you enjoyed reading this post, why not have a look at The Complete List of VMware Articles .
У вас есть ESXi (любой гипервизор) на котором запущены виртуальные серваки? Иногда бывает так, что нужен доступ к реальной консоли сервера и не всегда есть возможность использовать консоль vmware. Если решение вам интересно читаем дальше.
Прежде всего, на ESXi можно запустить виртуальную машину, которая будет доступна через VNC. Мы сразу же можем подключиться к виртуальной машине с помощью любого VNC-клиента. Но это не наш путь.Давайте для начала изменим настройки виртуальной машины. Выбираем виртуальную машину -> Edit Settings -> Options -> General -> Configuration Parameters и добавляем 3 параметра:
Если вы используете ESXi 5 версии, то вам еще нужно будет открыть порт на фаерволе этого гипервизора. Сделать это не так легко, как кажется на первый взгляд. Включаем SSH и создаем новый xml файл, с описанием нового правила для фаервола в /etc/vmware/firewall:
После этого обновим конфиг фаервола и посмотрим, появился ли наш новый сервис:
Основная проблема в том, что если сейчас ESXi перезагрузить, то нашего нового правила не будет. Самое простое решение скопировать XML-ку на storage, к которому у хоста есть доступ, а на самом хосте добавить в /etc/rc.local:
Если вы хотите более правильное решение, то можно почитать тут.
Теперь ко всем нашим виртуальным машинам есть VNC доступ. Далее будем делать одну точку доступа ко всем серверам, используя Guacamole
Guacamole
С помощью Guacamole вы можете получить доступ к консоли своих серверов из любого браузера, который поддерживает: HTML5 и AJAXGuacamole умеет работать с VNC и RDP. Установку можно производить на Debian, Ubuntu, Fedora
Установка Guacamole не составит большого труда. Примеры для Ubuntu. Установим зависимости:
Последнюю версию можно найти на сайте продукта:
Если все сделали правильно, то зайдя на myip:8080/guacamole/ увидим окно ввода логина и пароля. Схема аутентификации по умолчанию читает все настройки из файла конфигурации /etc/guacamole/user-mapping.xml
где hostname — это адрес вашего esxi хоста, password — пароль для VNC.
Теперь логинимся под пользователем User1 и подключаемся к вашим виртуальным серверам. Чтобы открыть виртуальную клавиатуру нажимаем: Ctrl+Alt+ShiftAnswers
Vsphere Client 5.1 solved the problem. Now I can able to see the virtual machines.
Considering the issue is related to Vsphere client, it is recommended that you go to VMware Support for help:
Thanks for your understanding and cooperation.
TechNet Community Support
4. Permissions
Verify that the permissions set on the VM’s VMX file are set correctly (755). To check the permissions, run the command:
-rwxr-xr-x 1 root root 3995 Aug 18 10:00 Windows 7.vmx
We can see that the permissions are correctly set for the VMX file of a VM called Window 7.
If the VMX file permissions are not set to 755, run the following command:
chmod 755 ‘Windows 7.vmx’
Note: On ESXi 6.5, setting the permissions to read only had no effect so the permissions issues might only apply to older versions of ESXi.
Answers
Vsphere Client 5.1 solved the problem. Now I can able to see the virtual machines.
Considering the issue is related to Vsphere client, it is recommended that you go to VMware Support for help:
Thanks for your understanding and cooperation.
TechNet Community Support
1. Firewalls
Depending on the version of ESXi / vCenter Server installed, TCP ports 902, 903, 443 and 9443 need to be reachable when using the web based and standalone remote consoles. With vSphere 6.5, I managed to replicate a common problem where a personal firewall, or one sitting between the client computer and ESXi networks, is blocking one or more ports especially 902. To do this, I enabled the Windows firewall and created an outbound rule blocking 902 as shown.
Managing Microsoft Windows firewall rules
When the firewall rule is enabled, the following is what you get when trying to remote console to a virtual machine . The error message might differ slightly depending at which point the connection is dropped.
Remote console connection errors due to a firewall blocking ports 902 and 9443
Changing the firewall rule to Allow from Block fixes the “unable to connect to the mks” issue. Often, the lost ability to remote console occurs right after someone installs or rolls out security software incorporating a personal firewall. From my experience, other primary suspects include updates to group policies governing the Windows firewall and unannounced changes to ACLs on switches / routers. If you’re not the one administering the latter, talk to your colleagues to try and narrow down the source of the problem.
You can use netstat to verify that connections on port 902 are being established when you remote console to a VM. If you don’t see any entries, the issue is definitely firewall / network related. Another trick you can use is to telnet 902 from a command prompt or terminal. If you get a reply, it means that ESXi is listening on the port and ready for connections.
Using netstat to inspect network connections
If you’re not running a personal firewall, SSH to ESXi and temporarily disable the ESXi firewall by running esxcli network firewall set –enabled false. Verify that you can connect. If not, it’s a firewall sitting in between the management station and ESXi that’s dropping the connection.
If the problem persists after having ruled out firewalling as a problem source, move on to the next check.
Answers
Vsphere Client 5.1 solved the problem. Now I can able to see the virtual machines.
Considering the issue is related to Vsphere client, it is recommended that you go to VMware Support for help:
Thanks for your understanding and cooperation.
TechNet Community Support
All replies
I'm having the same issue. I've tried installing in compatibility mode as administrator, and executing as such as well. No luck so far.
I have the same issues. Seems to be a common Windows 8 & vSphere issue. Posts all over VMware sites too.
No solution form VMware yet. :(
Considering the issue is related to Vsphere client, it is recommended that you go to VMware Support for help:
Thanks for your understanding and cooperation.
TechNet Community Support
While the issue IS a vSphere client problem, all information gathered thus far would seem to indicate that the problem lies somewhere within vSphere's reliance upon IE 10. With the right information from the Microsoft side of things, those of us early adopters, holding (IT) positions of influence within companies that are currently determining whether or not they will move to Windows 8 (and when), who are simply trying to utilize the toolsets that they currently rely upon to do their jobs, we might be able to use that information to institute our own workaround until a permanent fix is established. Just because we are asking for some troubleshooting assistance in utilizing a "competing" product, we are using that competing product to manage hundreds (potentially thousands) of VMs that are all running Windows. That said, is there any information that you might be able to provide in regards to what might be different in IE10 that would cause an issue in an application that relies upon IE to function (in this case, remote console)?
I think I am going back to my WIN7 until there is a greater acceptance.
Bump - anyone found a fix yet?
Not yet, although the link provided by PWILEY above does yield some additional information, specifically this event log entry:
Application 'C:\Program Files (x86)\Common Files\VMware\VMware VMRC
Plug-in\Internet Explorer\vmware-vmrc.exe' (pid 1408) cannot be restarted -
Application SID does not match Conductor SID.Joe (from the link) surmised that the vmrc plug-in is simply incompatible with IE10. He even went as far as trying to force the plug-in to utilize another browser, but this failed as well. Again, if we, the IT community, were provided some additional information, we might be able to come up with a work-around that does not involve using VMware Workstation (that is my current work-around of choice) or some other less-than-straight-forward solution.
When was the last time you tried to remote console to a VM only to be greeted with the annoying Unable to connect to the MKS or similar message? Some of the causes leading to this issue range from firewalls blocking the required ports, badly configured DNS, and ESXi services in need of a restart. Today’s post explores a number of ways you can use to remote console to a VMware virtual machine and what you can do when remote connections fail, and you are unable to connect to the MSK .
Speaking of firewalls, adding a persistent firewall rule to ESXi can be daunting. I discuss how to do this in How to create persistent firewall rules on ESXi .
What is MKS?
MKS stands for Mouse, Keyboard and Screen. In vSphere, you can remote console to VMs using the standard vSphere clients and products such as VMware Workstation.
In pre-6.5 vSphere releases, you can use the legacy vSphere client which has now been deprecated for a long time. As shown next, just highlight the virtual machine you want to connect to and click on the Console tab. Alternatively, right-click on the VM and select Open Console . The latter method opens a stand-alone console window for you.
Remote console using the vSphere Client
If you have vCenter installed, the vSphere Web Client provides you with two remote console options, these being VMRC (the standalone VMware Remote Console) and the Web Console .
You can change the default virtual console by clicking on your user in the top right corner > My Preferences > Default Console > You can then select the web or vmrc as your default console.
You also get both options directly underneath the preview of the VM screen in the VM view. VMRC is installed by following the link given in vSphere client or by downloading it from here .
NOTE: Users who have VMware Workstation installed will have noticed that selecting Launch Remote Console brings up Workstation’s VMRC instead of the standalone one. To override this behavior, uninstall the standalone VMRC and reinstall it back.
Back to vSphere Web Client, clicking on the VM’s console screen or selecting Open Console from the VM’s context menu will launch the default remote console.
Choose between the web console and VMRC.
Remote console using the host client (ESXi embedded)
Interestingly, you can configure a virtual machine such that you connect to it using a remote client such as tightVNC. To do this, add the following lines to the VM’s configuration ( Edit Settings -> VM Options tab -> Advanced Settings -> Edit Configuration ). You must disable the ESXi firewall for this to work or add a rule to allow 5900 through, this being the default VNC port. If memory serves me right, this worked with ESXi 5.x versions but to be honest, I had little time to try it out on 6.x. With ESXi 6.5, I manage to establish a connection but it keeps asking for a password regardless of the one specified in the VM’s configuration.
Configuring a VM to accept remote connections from VNC
2. DNS
Connection to remote console can also be impeded if ESXi and vCenter Server hostnames do not resolve correctly. To determine correct DNS resolution, use ping < ESXi hostname > or nslookup to verify that your ESXi and vCenter Server hostnames are resolving to the correct IP addresses and, likewise, to the correct hostnames. If the issues persists, try adding your ESXi hosts and IP addresses to \windows\system32\drivers\etc\hosts , run ipconfig /flushdns and retry.
All replies
I'm having the same issue. I've tried installing in compatibility mode as administrator, and executing as such as well. No luck so far.
I have the same issues. Seems to be a common Windows 8 & vSphere issue. Posts all over VMware sites too.
No solution form VMware yet. :(
Considering the issue is related to Vsphere client, it is recommended that you go to VMware Support for help:
Thanks for your understanding and cooperation.
TechNet Community Support
While the issue IS a vSphere client problem, all information gathered thus far would seem to indicate that the problem lies somewhere within vSphere's reliance upon IE 10. With the right information from the Microsoft side of things, those of us early adopters, holding (IT) positions of influence within companies that are currently determining whether or not they will move to Windows 8 (and when), who are simply trying to utilize the toolsets that they currently rely upon to do their jobs, we might be able to use that information to institute our own workaround until a permanent fix is established. Just because we are asking for some troubleshooting assistance in utilizing a "competing" product, we are using that competing product to manage hundreds (potentially thousands) of VMs that are all running Windows. That said, is there any information that you might be able to provide in regards to what might be different in IE10 that would cause an issue in an application that relies upon IE to function (in this case, remote console)?
I think I am going back to my WIN7 until there is a greater acceptance.
Bump - anyone found a fix yet?
Not yet, although the link provided by PWILEY above does yield some additional information, specifically this event log entry:
Application 'C:\Program Files (x86)\Common Files\VMware\VMware VMRC
Plug-in\Internet Explorer\vmware-vmrc.exe' (pid 1408) cannot be restarted -
Application SID does not match Conductor SID.Joe (from the link) surmised that the vmrc plug-in is simply incompatible with IE10. He even went as far as trying to force the plug-in to utilize another browser, but this failed as well. Again, if we, the IT community, were provided some additional information, we might be able to come up with a work-around that does not involve using VMware Workstation (that is my current work-around of choice) or some other less-than-straight-forward solution.
I had upgraded my laptop from Windows 7 to windows 8 Release Preview. when ever open Vsphere client it couldn't shows the virtual machine instead of showing "The VMRC Console has Disconnected.. Trying to reconnect". I tried reinstall but the issue remain the same.
5. If nothing else works!
If none of the above worked, try doing the following:
- Check that the time on ESXi is set correctly and in sync with the rest of the infrastructure.
- vMotion the VM you’re unable to remote console to, to another ESXi host and retry.
- Restart the management agents on ESXi as per the following KB .
- Reboot the VM.
- Reboot ESXi.
Note: Sometimes to fix if vmware remote console is unable to connect to the mks is as trivial as pressing a key while the focus is given to the console window. This was common with older versions of the legacy client and vSphere releases where nothing is displayed in the VM’s console window. Hitting Enter or another key usually brings the console back to life. An alternative fix is to launch the console in its own window by right-clicking on it and selecting Open Console .
Читайте также: