When trying to connect to the console within the VI Client you receive the following error,
Cannot connect to host my.esx.host.com: no connection could be made because the target machine actively refused it
In this example you have the required ports open on both your firewall and your ESX box. You see the traffic on tcp 902 going to your VMware server but your server is closing the connection.
This is a known bug when trying to access the console of a ESX hosted VM across multiple networks.
To resolve the issue add the following to /etc/vmware/config
vmauthd.server.alwaysProxy = “TRUE”
I believe that you also may need to add this to your advanced options in the VI Client GUI to survive a reboot, but I still need to confirm this……
Has anyone else already tried this ???
- How to Configure a BIND Server on Ubuntu - March 15, 2018
- What is a BGP Confederation? - March 6, 2018
- Cisco – What is BGP ORF (Outbound Route Filtering)? - March 5, 2018
Want to become a VMware expert?
Here is our hand-picked selection of the best courses you can find online:
Complete VMware Administration course
VMware vSphere 7 – Install, Configure, Manage
and our recommended certification practice exams:
AlphaPrep Practice Tests - Free Trial