Re: Exch 2K3 OWA port 80 conflict with SUS
- From: "Bharat Suneja [MVP]" <bharatsuneja@xxxxxxxxxxx>
- Date: Mon, 29 Jan 2007 17:47:02 -0800
- Do you see the Exchange virtual directories in the default web site on the
BE?
- Is the default web site set to use SSL only by any chance?
- Are there other web sites bound to port 80?
- Is another web server/app bound to port 80?
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------
"jkegley" <jkegley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51100509-0CA8-41F2-B06B-F96E407BDD9A@xxxxxxxxxxxxxxxx
I just setup a new Front End Exch 2k3 Server. It will authenticate users
but
when it is time to get the users mailbox, I get an HTTP 404 error, page
not
found or missing. I found that the Default Web Site on my Back End server
was using port 8080 instead of 80. Port 80 was being used by SUS. I
uninstalled SUS but the Virtual Directory was left behind, still using
port
80.
I deleted the SUS Virtual Directory and changed the port on the Default
Web
Site from 8080 to 80. I still can not get my Front End to talk to my Back
End.
I think the problem is with the Back End not listening to port 80. How do
I
check / validate or fix this in IIS on the Back End Server. OWA only
works
using SSL on the Back End, if I try to use SSL on the Front End or just
HTTP
on either I get the 404 HTTP error.
Any thoughts?
.
- Follow-Ups:
- Re: Exch 2K3 OWA port 80 conflict with SUS
- From: jkegley
- Re: Exch 2K3 OWA port 80 conflict with SUS
- Prev by Date: Re: Move exchange to a new box
- Next by Date: Re: Upgrading from Exchange 2000 to 2003
- Previous by thread: Re: Move exchange to a new box
- Next by thread: Re: Exch 2K3 OWA port 80 conflict with SUS
- Index(es):
Relevant Pages
|
Loading