Forum Discussion
ahlip
17 years agoLevel 5
Hi Lunatic,
You misunderstood my experience. The Proxy does not need to have network connectivity to every VM. Just that it needs to be able to resolve (hosts file or DNS reverse lookup). This is because it seems that when it browses the VM client list, it talks to the ESX/VC to obtain a list of IP identifiers of the VMs available and then tries to resolve it to a hostname label.
When I did not have a windows hosts file with the VM IP address & hostname label, then I get an error while browsing. I put in the hosts file entries, browsing now ok.
Note that my Proxy cannot ping any of the VMs via IP, they are in different network.
You misunderstood my experience. The Proxy does not need to have network connectivity to every VM. Just that it needs to be able to resolve (hosts file or DNS reverse lookup). This is because it seems that when it browses the VM client list, it talks to the ESX/VC to obtain a list of IP identifiers of the VMs available and then tries to resolve it to a hostname label.
When I did not have a windows hosts file with the VM IP address & hostname label, then I get an error while browsing. I put in the hosts file entries, browsing now ok.
Note that my Proxy cannot ping any of the VMs via IP, they are in different network.
Related Content
- 11 years ago