Quantcast
Channel: VMware Communities : Discussion List - vCenter™ Server
Viewing all articles
Browse latest Browse all 6649

Unable to Connect to MKS:

$
0
0

Hi All.

 

I'm hoping someone might have an answer, I tried the VMware blog where I found a "solution" but it hasn't helped.


I hope this will make sense.

 

I have a nested environment in VMWorkstation 10.0.0. Using VMware ESXi 5.1

I currently have 3 hosts, DC, vCenter, openfiler (ISCSI SAN) running. I had this set up with only 1 VM running on host 1. I was able to connect to this host and do anything I needed to using vSphere. I am still able to connect to it now.


On Monday, I reinstalled windows from 2012 to 2008. due to the back ups I do, I restore back my settings in my Firewall program Vipre/Sunbelt.


I created a second VM on host 2, but unfortunately I was getting an error of "Unable to Connect to MKS" So I went and created the VM on host 3, I continued to get the error when I went into Console to install windows.

I am still able to connect via console to the VM on Host 1.


I turned off the Firewall both in Server2k8. and Vipre. I also turned it off in vCenter (AS recommended by VMware) and following their instructions to set a line in the /etc/vmware/config file to "True" (which was already set). No luck connecting to any of them.

 

Each host has 4 NICs, however, only 2 are able to see the production side, and the other 2 are set to see the SAN on a different subnet. They are able to see the SAN still. The two production NICs are set up as Active/Standby. I have added the Mac address into the exception list of my firewall as I have had to do this for VMs in the past with Vipre, I also added the vcenter.


I'm starting to run out of ideas, keep in mind that host 1 is not in any exception list yet, however, host 2 and 3 were set up the same way as host 1, and then got put into exceptions once they weren't working. I have also added the ports 902 - 903 into the open ports list.


I have refreshed/flushed the DNS - removed and created new records.    I have Disconnected and Attemptped to reconnect the hosts, but getting the below Error through the C# Client.

Call "Datacenter.QueryConnectionInfo" for object "New Datacenter" on vCenter Server "server2.ssit.com" failed.


When I log on through the WebGUI from the desktop I am able to see the hosts in the list and both 2 and 3 disconnected, I can connect to 3 without even being asked for Credentials, however, host 2 asks and then fails due to no server available. If I log on through the C# client on the vCenter server I can reconnect all hosts.

 

Hopefully this is making sense, would be great to see if anyone has come across this before.

Any more information, please ask.


 

 

Thanks guys


Viewing all articles
Browse latest Browse all 6649

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>