VMware Cloud Community
a_ndyb
Contributor
Contributor
Jump to solution

vSphere ESX 4.1 changing default ports 80 and 443 ???

Hiya,

I'm having problems trying to change the default ports so that i can move my exchange server into VM.

I've tried what it says on the forums here but i just can't get it to work. VMware KB article 1021199

The proxy.xml has about 72 lines in it but i've put this at the top, bottom, no joy.

The top of my proxy.xml now looks like

<ConfigRoot>

  <httpPort>81</httpPort>

  <httpsPort>444</httpsPort>

  <the rest of the file>

  </the rest of the file>

</ConfigRoot>

I've changed the ports in my Client file too.  <add key = "protocolports" value = "https:444;http:81" />

All i get is cannot connect to the server.

I've also tried adding the port to the name such as 192.168.5.111:81, no joy.

What am i missing here ?

Any help much appreciated, taa.

AndyB

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership
Jump to solution

Welcome to the Community,

just a quick question. Why do you ant/need to change the ports on the ESX host? The ESX host as well as the each virtual machine use their own IP address, so there shouldn't be any port conflicts with a virtualized Exchange server.


André

View solution in original post

Reply
0 Kudos
4 Replies
a_p_
Leadership
Leadership
Jump to solution

Welcome to the Community,

just a quick question. Why do you ant/need to change the ports on the ESX host? The ESX host as well as the each virtual machine use their own IP address, so there shouldn't be any port conflicts with a virtualized Exchange server.


André

Reply
0 Kudos
a_ndyb
Contributor
Contributor
Jump to solution

Oh right.  I didn't think that far.

At the moment i have the vsphere server on a subnet all on its own through a router off my office network and i've used it for testing office configurations before doing the jobs.

My exchange server hardware is getting long in the tooth and before i upgrade, i was going to drop it into vsphere nice and safe.

Then i thought, if i'me passing 80 and 443 through the router to use the vsphrere client on my office lan, how do i get round using 443 for exchange ?

So i thought, yeah, i'll change the vsphere ports because i'd read it somewhere that you could...

That probably sounds silly thing to do but i couldn't think of any other way at the time.

All i've been doing is using the client through the router and simply opening up a console session on each server instance i have in vsphere.

Now for the first time, i wished to plug an instance in vsphere into the world and use it properly if that makes any sense...

So i thought i'd forward 25 and 443 from my broadband router to the vsphere router ip address, then forward from there to the exchange instance.

So i suppose really, i've got to plug a workstation into the router on the vsphere side to use the client. ??

On my understanding of routers, i think i can only pass a port to one ip address.

Therefore i couldn't for example have two servers in my vsphere using the same port could i ?

I think my knowledge of routing is not good!

AndyB

: -)

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

So you want to access the systems with a single IP address using port forwarding on a router!?

In this case I would probably leave the ESXi host untouched and only use other ports on the client side. Then on your router forward the traffic to the appropriate IP address and port on your internal network (e.g. vSphere Client: <ext. IP-Address>:8433 -> <ESXi IP-Address>:433) If you wan to be able to have console access to your VMs, you may also need to forward port 902.

André

a_ndyb
Contributor
Contributor
Jump to solution

Yes, I work from home so there's only so much i can do and i understand what you've said to me.  Thank you very much for your help.

I just needed that 'push' and I can see exactly what you mean and i can work on it now...

Thanks, Andy B

: -)

Reply
0 Kudos