OWA on port 8080? Possible?

[Kerry]

I have been running Exchange OWA on port 80 (with SSL on 443). I want to run
OWA on a different internet port, such as 8080. Is this possible? If so, does
this require anything more than changing the IIS web site port to 8080 and
opening the same port on my firewall? What URL would I use to connect to OWA?
mail.domain.com:8080/exchange/user?

While I'm here, I'd like to get your opinion on the larger motivating
question. I want to host multiple websites on the same server that is also
running Exchange. Because OWA requires SSL, and SSL is incompatible with host
headers, I thought I could work around the conflict by moving the OWA site to
a different port. My hope being that I could still use host headers on the
standard port (80) to differentiate my other sites.

Am I courting heartbreak? Any comments?

[Mark Arnold [MVP]]

On Sat, 26 Feb 2005 05:41:02 -0800, "Kerry"

Post by Kerry
I have been running Exchange OWA on port 80 (with SSL on 443). I want to run
OWA on a different internet port, such as 8080. Is this possible? If so, does
this require anything more than changing the IIS web site port to 8080 and
opening the same port on my firewall? What URL would I use to connect to OWA?
mail.domain.com:8080/exchange/user?
While I'm here, I'd like to get your opinion on the larger motivating
question. I want to host multiple websites on the same server that is also
running Exchange. Because OWA requires SSL, and SSL is incompatible with host
headers, I thought I could work around the conflict by moving the OWA site to
a different port. My hope being that I could still use host headers on the
standard port (80) to differentiate my other sites.
Am I courting heartbreak? Any comments?

No problem. It's best to leave OWA where it is and set the ports you
want, both SSL and HTTP.

[Kerry]

Thanks for the reply, Mark. But I don't quite follow your comment. Let me try
to clarify my question.

I want to keep the non-Exchange websites on the standard HTTP port (80) to
allow general internet users to access these sites without the need to append
port numbers to the URL (e.g.: www.mysite.com:8080). In contrast, I have only
a small group of Exchange users so I don't mind asking them to add a port
number (such as 8080) to the URL to reach the Exchange server.

Does anyone have experience moving the Excahange HTTP virtual directories
(i.e. the default IIS website) to another port? Furthermore, has anyone
succeeded in continuing to use host headers to distinguish sites on the
standard port while simultanseously enabling SSL for the Exchange website on
a different port?

Example:
Name Port Identified by:
------ ------ ----------------
website1 80 host header1
website2 80 host header2
Exchange website 8080 port number
(w/ SSL enabled)

Thanks,
Kerry

Post by Mark Arnold [MVP]
On Sat, 26 Feb 2005 05:41:02 -0800, "Kerry"

Post by Kerry
I have been running Exchange OWA on port 80 (with SSL on 443). I want to run
OWA on a different internet port, such as 8080. Is this possible? If so, does
this require anything more than changing the IIS web site port to 8080 and
opening the same port on my firewall? What URL would I use to connect to OWA?
mail.domain.com:8080/exchange/user?
While I'm here, I'd like to get your opinion on the larger motivating
question. I want to host multiple websites on the same server that is also
running Exchange. Because OWA requires SSL, and SSL is incompatible with host
headers, I thought I could work around the conflict by moving the OWA site to
a different port. My hope being that I could still use host headers on the
standard port (80) to differentiate my other sites.
Am I courting heartbreak? Any comments?

No problem. It's best to leave OWA where it is and set the ports you
want, both SSL and HTTP.

[Lanwench [MVP - Exchange]]

Post by Kerry
Thanks for the reply, Mark. But I don't quite follow your comment.
Let me try to clarify my question.
I want to keep the non-Exchange websites on the standard HTTP port
(80) to allow general internet users to access these sites without
www.mysite.com:8080). In contrast, I have only a small group of
Exchange users so I don't mind asking them to add a port number (such
as 8080) to the URL to reach the Exchange server.

OT, but do not host public websites on your LAN at all, let alone on your
Exchange server. OWA is often scary enough to admins. If you must host
something in-house at all, a) put the webserver(s) in your DMZ and b) maybe
consider running them on something besides Windows. Or - better still - get
some inexpensive third party hosting company to host your websites. It is
*much* better for most.
And don't open up port 80 at all - OWA should be using SSL and accessible
only via 443.
<snip>