VMware vSphere

 View Only

  • 1.  VMware vSphere vCenter Server Web Access from Internet

    Posted Mar 09, 2010 02:40 AM

    I am testing VMware vSphere (ESX 4) and wanted to connect to the VM's from the internet for Admin Only Web Access. I can connect to the vCenter Server (on Windows) via the Web Access http functionality and administer the configuration of all VMs. But when I attempt to connect to an actual vm via MKS, I get a MKS error like "Unable to connect to the MKS: Failed to connect to server xxx.xxx.xxx.xxx:902." The xxx.xxx.xxx.xxx is the IP address of the ESX server HOST and not the vCenter Server (which administers the host). I have ports 80, 443, 902 and 903, on the firewall, opened to point to the vCenter Server. When I am on the local LAN, I can do everything without issue. Its only when I attempt to connect directly from the internet through our firewall that I get the above error.

    Anyone have any suggestions?



  • 2.  RE: VMware vSphere vCenter Server Web Access from Internet
    Best Answer

    Posted Mar 09, 2010 03:56 AM

    Andrej770,

    vCenter Server is forwarding you to the ESX Host that is hosting the VM, and the remote console is running on port 902.

    You require access directly to the ESX Host on port 902 through the Firewall to connect to the Virtual Machine consoles.

    You will want to review the "ESX Configuration Guide" pages 146 for more information.

    http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf






    If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".



  • 3.  RE: VMware vSphere vCenter Server Web Access from Internet

    Posted Mar 09, 2010 12:36 PM

    These are the ports I had to open up on the firewall to enable direct access from the Internet to VMs on a specific host via vCenter Server:

    Opened up ports (TCP) 903, 427, 5989, 22 and ports (UDP) 427 to the vCenter Server

    Opened up port (TCP) 902 and port (UDP) 902 to the Host

    Let me first say that this is not the SECURE solution. It is just for testing. A safer solution would be to VPN into the LAN, then connect to the vCenter Server directly.

    Secondly, this enables access only to a specific host. It does not solve the issue if you have to connect to VM's on multiple host via vCenter Server and directly from the Internet.