LinkBack URL
About LinkBacksESX 2.5 had pretty decent web access, vanished in v3 though.
ESX 2.5 had pretty decent web access, vanished in v3 though.
Thanks for all the pointers guys. Having a slightly diff problem now...
When starting the console window for a VM I have created I get the following error in the console window... "Unable to connect to the MKS: Timeout While attempting read."
Any idea what this means? Never used ESXi before, always vmware server and never encountered this error.
Do you have a DNS record for your host?Originally Posted by m1ddy
The hosts needs a DNS record on the DNS server it uses for the console connection to work on clients. The client you are using must have a way of using this DNS server too.
Last edited by Theblacksheep; 30th October 2009 at 12:45 PM.
What are you connected to the ESXi host with? vSphere client? Web? What version is the client?
Are you connecting to the server IP or hostname when you log in to vsphere client?
Connecting using vSphere. ESX V4 and vSphere V4.
Ahh, the DNS server it was given by DHCP is an infoblox unit. This will need an A record adding?
yes indeed.
Is SSH off by default? The trouble is the box is running headless.
Yeah it is.... ilo?
hmmz
The problem I am having is that myself and our DNS server are on a different subnet than the ESX host. We have a Palo Alto firewall bridging the networks and doing the routing. However, sessions can be created from this network to the ESX boxes network, but sessions cannot be created going the other way. Traffic can flow between both subnets but only if the session is created by a host on this subnet.
Am i going to have to setup a DNS server on the same subnet as the ESX box? I assume I can keep the ESX hosts as localdomain.
Sorry to jump in with a couple of "minor" questions. I'm almost at the stage of getting my hardware sorted to run ESXi but it's purely for learning purposes - 1 or 2 server OS plus 1 or 2 clients. I don't want or need to deploy anything in the real live situation (yet).
1. I was under the impression that ESXi is free. Is that the case or is there a "slimmed down" free version which can be upgraded for a fee to allow much more functionality? If so, I hope that I could use the free version. If so, is it time-limited?
2. I've read about the VI Client (downloaded from the ESXi server installation to a client) which is used to install guest OSs, access VMs and manage everything. Earlier in this thread, and indeed the title, there is mentioned vSphere. What's the difference between VI Client and vSphere?
Apologies if I appear stupid but I want to get everything right in my head so I don't make any major (read expensive!) mistakes.
ESXi is the free hypervisor that VMWare offer. ESX is the full version with all the bells and whistles, vmotion etc. ESXi can do this but only for 60 days I believe. Then it just defaults back to the basic hypervisor, which for testing etc is perfectly fine.
vSphere is the new client released with vmwares 4.0 products I think. VI3 is the last generation equivelent.
ESXi effectively IS ESX without the Linux Console. They have the virtually the same features, apart from missing serial port virtualisation on ESXi.
ESXi is not cut down in any way, features for both versions are dependent on the license you obtain, there is only a free version of ESXi however.
OK guys. It looks like I'll be getting my hands on ESXi with vSphere. I just need to sort the hardware now.
Does this work on esxi 4? I ran service vmware-webAccess start but that gives
Code:-ash: service: not found
ahhhh, its not in 'i'... I didnt know that. GRRR
VMware Self-Service- VMware ESX and ESXi 4.0 Comparison
Last edited by Theblacksheep; 3rd November 2009 at 01:01 PM.
There are currently 2 users browsing this thread. (0 members and 2 guests)
Posting Permissions
