Changing Management Ports in ESXI 5.5.

[Mast3rNe0]

I been trying to change the management ports for port 443 to port 444 or something different as we use 443 for exchange.

I try to follow the article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102119...

However modifying the proxy.xml and restarting the management service does not seem to work as the ports is still defaulted.

Any help in changing 443 to something else so I can access ESXI from outside the network.

[MKguy]

I been trying to change the management ports for port 443 to port 444 or something different as we use 443 for exchange.

Could you explain why this would be any issue at all? Port 443 is served on your exchange servers or whatever web server or application you have running. But that doesn't matter in the least to what ports an ESXi host with its own interfaces is listening on. Why do you still think you need to change the port?

As you can see on the right pane in the article, it applies up to VMware ESXi 5.0.x only. Not sure this is still supported or supposed to work on 5.5

Try manually running the config backup scripts after making the change:

# backup.sh 0

# /sbin/auto-backup.sh

[Mast3rNe0]

The reason for changing the port is 443 which is HTTPS is being used by our exchange server.

I can manage my ESXI from outside with the public ip but OWA also uses HTTPS and I can only port forward to 1 internal IP, and not the other.

This is for remote management incase I am away and the VM needs to be rebooted.

I am aware the article for 5.0 so I am wondering if their are updated instructions for 5.5. and above on how to do it, their has to be a way to change it as I been just port forwarding one port at 444 which gets redirects to 443.

[MKguy]

Ok, so to confirm, you're basically NATing a public single IP to your internal network that contains the ESXi management vmkernel interface as well as other internal IPs here? Should have mentioned that in the first place.

In that case, why can't you NAT another port on your public IP to a different internal IP/port? Every modern router or firewall should be able to do that. Then you would just need to connect to an arbitrary port with the vSphere Client, your edge route will NAT that external port to the appropriate internal IP and port you set.

[Mast3rNe0]

I am trying to keep things in consistent and rather use the same port internal and external, not having to do natting both and forth like this.

Changing the port should be simple process but I seen other people asking the same exact question and them getting turn the opposite direction with how to remote control their esxi servers such as using RDP to a machine or vpning.