Re: OWA on port 8080? Possible?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Kerry (Kerry_at_discussions.microsoft.com)
Date: 02/26/05 

Date: Sat, 26 Feb 2005 14:25:01 -0800

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

"Mark Arnold [MVP]" wrote:

> On Sat, 26 Feb 2005 05:41:02 -0800, "Kerry"
> <Kerry@discussions.microsoft.com> wrote:
>
> >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.
>

Relevant Pages

  • Re: Newbie (!) Exchange 2003 push and SPV M5000 Active SYnc 4.2
    ... I wouldn't worry too much about SSL. ... Since you aren't port-forwarding port 80, OWA won't currently work from the ... Install a certificate on your Default Web site (on the Exchange server). ... Make sure that OWA is working externally. ...
    (microsoft.public.exchange.admin)
  • Re: ISA2004 SP2: EventID 14148
    ... In SBS the external accessible websites are configured to listen on "(All ... Unassigned)" IP addresses and TCP port 80. ... to use a second server (with the costs of an additional Windows 2003 Server ... resolve this issue, ...
    (microsoft.public.isa.configuration)
  • Re: Setting up MX records etc
    ... Also need port 443 open for SSL in OWA ... > DNS if you have a DNS on your server in site ONE. ...
    (microsoft.public.exchange.admin)
  • Re: owa and isa2k4 on single-nic machine
    ... why don't you terminate the SSL channel at ISA. ... Bridge the OWA ... > - To avoid port contention, in IIS, the default web site's SSL port is ...
    (microsoft.public.isa)
  • Re: Port 80 for exchange 2007
    ... something critical that needs port 80. ... if i'm using ssl for owa do I really need port 80 to be open as ... If you require SSL on everything (OWA, AS, any ... Outlook Web Access For PDA, ...
    (microsoft.public.exchange.setup)