Sep 302014
 

If you are working on a VMware vCenter Server v5.5 in an environment that has multiple segregated VLANs designed to isolate certain types of traffic, and find that the web client for your admin-facing interfaces keeps redirecting to an internal isolated IP address – and therefore fails – here’s the solution.

Edit the file C:\ProgramData\VMware\VMware VirtualCenter\proxy.xml and update the vim.ProxyService.RedirectSpec entry at ID 21, on approximately line 93. It’s the hostName value, and it will be set to one of the isolated IPs. Just change it to the new value and restart the VMware VirtualCenter Server services. Use a tool like Textpad because of the typical carriage return concerns with non-Windows-sourced files.

vcenter_proxy

Voila! Problem solved.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close