VM console over NATed network

[luizhbedin]

Hi all!

I access my VC server throught a nated ip address. EX: My ESX server address is 10.20.40.15 and to access it I type 21.20.40.15.

Everything works fine, ESX configuration, networks, etc.. But when I try to open the VM console I get an error message sayind that is not possible to communicate to 10.20.40.15, and then opens a blank console, and I cannot see my VM console.

does anyone know a solution to this? Why the ESX server doesn´t respond on nated address?

Thanks!

[englem]

I had this happen to me when I was going through the firewall. My issue was resolved when I checked with our WAN group and saw quite a few ports being blocked.

Check your logs or with your networking group and see if there are any ports getting blocked. Can't guarantee this is your problem but they are pretty similar.

[esiebert7625]

The VM remote console connects directly to the ESX server and not the VC server. It also uses port 903 instead of 902.

http://www.vmware.com/community/thread.jspa?messageID=609820

[bflynn0 · Accepted solution]

To use the NAT'ed address add the following to the /etc/vmware/config[/b] file in the VMware ESX Service Console:

vmauthd.server.alwaysProxy=TRUE

[luizhbedin]

Do I need to restart any service on SC?

[bflynn0]

I don't believe you do.

If anything you might need to restart the VMware host agent

service mgmt-vmware restart[/code]

Also, this will only work if you are using the VIClient to connect directly to the ESX Host, it will not work when connecting through a VC server.

[luizhbedin]

But If I want to connect trhought VC?

Is there a solution ?

[bflynn0]

As far as I'm aware this bug hasn't been addressed when connecting through VC. Hopefully VMware will address it soon, but right now the only work around is to use the vmauthd.server.alwaysProxy option and connect the VI Client directly to the ESX Server to view a VM Console on a NAT'ed ESX Host.

[luizhbedin]

It worked also to open console throught VC.

Thanks all for the posts.!

[Oletho]

Ack!

From home I'm connected via MPLS to the ESX cluster, and always wondered why the console didn't work from there. As far as I know there are no filters.

But adding vmauthd.server.alwaysProxy did the trick, thanks!

Ole Thomsen

[Grider]

Im trying to access the VMWare Server cluster and the consoles do not seem to work. Adding vmauthd.server.alwaysProxy does not seem to do the trick. Is there a work around ?