i have problem when i want to connect to my vm and show the console window
my vcenter and my esxi server is behind the NAT
all of them has invalid ip address(172.20.20.0/24) and they have been NAT to the valid ip address
all of esxi servers added to the vcenter via their invalid ip address
i connected to the vcenter via a VALID IP ADDRESS
when i connect vcenter through vsphere client or vsphere web client i cant get console window and it doesnt show any thing just give an error for port 902
and when i connect the esxi hosts directly via their valid ip i can get console window and it does not have any problem
i know that via vcenter when i get console window , i directly connect to the ESXi host with valid ip address and problem is because of this, because i connected to that vm via their invalid esxi ip (172.20.20.0) and i can not access to it
but i want to know is there any solution to solve this?
in vcloud director we have an option (VMRC) for solving this
i think it will be solves with 2 dns severs
Creating a proxy
1. Add your ESXi hosts, and vCenter, to your public DNS (split DNS). Meaning your external DNS would have publics IPs while internal DNS would have your private network IPs.
2. Create a VM (or physical machine) with 2 NICs. One NIC to your backend network to access ESXi hosts and One NIC to public IPs used for ESXi and vCenter. vCenter and each ESXi host need a public IP and that public IP is on the proxy host and also what is entered into DNS. A request is made to the public IP and forwarded to the backend ESX host. So when you open a console and vCenter is telling vSphere Client to go to esx02.backend.network.yourdomain.com, external DNS knows that this is actually PU.B.L.IC IP and not 10.10.10.x
3. Port forward each public IP to the proper backend private IP and port.