Jump to content
  • 0
Sign in to follow this  
Followers 0

ESXi issue! VMK

Question

Posted

hi! I m having trouble with my ESXi every time i try and view a virtual machine console it keeps coming up with saying there is an issue with the MKS*** and cannot connect via the IP:port ... I am tried editing the host file but nothing seems to be happening I dont know how to fix this :/


MKS**************** sorry i meant MKS************

Share this post


Link to post
Share on other sites

8 answers to this question

  • 0

Posted

To resolve this issue, remove the environment variable from the vSphere Client machine or vCenter Server: 1.Click Start > Run, type sysdm.cpl, and press Enter. The System Properties window opens.
2.Click the Advanced tab.
3.Click Environment Variables.
4.Remove any user variable and/or system variable named User.
5.Reboot Windows and launch the vSphere Client.
6.Verify that the vSphere Client virtual machine console now functions normally.


Alternative Resolution
1.Close all vSphere Client sessions.
2.Open Task Manager.
3.Search for any vmware-vmrc.exe processes and end the process.
4.Start the vSphere Client and connect to the host directly or to vCenter Server.
5.Attempt to access the MKS console.

You should be able to view the virtual machine and perform actions on the virtual machine using the keyboard and mouse.

Share this post


Link to post
Share on other sites
  • 0

Posted

[quote name='1ON' timestamp='1365776797' post='595633020']
To resolve this issue, remove the environment variable from the vSphere Client machine or vCenter Server: 1.Click Start > Run, type sysdm.cpl, and press Enter. The System Properties window opens.
2.Click the Advanced tab.
3.Click Environment Variables.
4.Remove any user variable and/or system variable named User.
5.Reboot Windows and launch the vSphere Client.
6.Verify that the vSphere Client virtual machine console now functions normally.


Alternative Resolution
1.Close all vSphere Client sessions.
2.Open Task Manager.
3.Search for any vmware-vmrc.exe processes and end the process.
4.Start the vSphere Client and connect to the host directly or to vCenter Server.
5.Attempt to access the MKS console.

You should be able to view the virtual machine and perform actions on the virtual machine using the keyboard and mouse.
[/quote]

no none of this solutions worked sorry :/

Share this post


Link to post
Share on other sites
  • 0

Posted

So - some details of your setup would be helpful. Are you running vcenter, or just vclient directly connecting to the host?

Could you post the exact error your getting.

Share this post


Link to post
Share on other sites
  • 0

Posted

[quote name='BudMan' timestamp='1365781975' post='595633194']
So - some details of your setup would be helpful. Are you running vcenter, or just vclient directly connecting to the host?

Could you post the exact error your getting.
[/quote]

i got it working but from another machine ...using vsphere

Share this post


Link to post
Share on other sites
  • 0

Posted

Was this error on a windows 8 machine? if so, it's because the vclient uses an IE plugin for the console which isn't compatible with IE10. VMware won't fix the problem because they say we should all be using the web app now (from v5.1 anyway).

Share this post


Link to post
Share on other sites
  • 0

Posted

Are you trying to use a newer version of a OS while you have an older version of ESXi? I remember that issues with an older version of 5 that could not support Windows 8 via the console screen.

Share this post


Link to post
Share on other sites
  • 0

Posted

[quote name='BudMan' timestamp='1365781975' post='595633194']
So - some details of your setup would be helpful. Are you running vcenter, or just vclient directly connecting to the host?

Could you post the exact error your getting.
[/quote]

bud man you seem to be a network guru .... we just set up a inter vlan route ... everything can ping everything ...but my ESXi vm ubuntu can only ping things on the same vlan.... any ideas why ??

Share this post


Link to post
Share on other sites
  • 0

Posted

you don't have a gateway or correct gateway (check mask) setup would be the first thing to check if can only ping stuff on same segment. Verify mac for gateway is correct, if another box is stepping on your gateway IP your going to have a bad day ;)

Can you ping the gateway? If not then why not?

Do you have intervlan acls setup? I firewall between my segments, so if you don't allow the correct stuff between vlans that you need, again your going to have a bad day ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.