Re: Exch 2K3 OWA port 80 conflict with SUS

Thanks. I will give this a shot. Just got to blow away the DS2MB Key ahe?
When I restart the SA the VirDir's will be recreated, but will they have the
default authentication settings? Thanks.

"Bharat Suneja [MVP]" wrote:

See if this helps:
http://support.microsoft.com/kb/883380

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------



"jkegley" <jkegley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C35942D6-F09A-409E-83AA-750C3FD65427@xxxxxxxxxxxxxxxx
Yes I can see the directories. There "used" to be SUS bound to port 80 on
the Back End. There is nothing else but Exch 2k3 on the front end (new
install). Both Windows server 2003 std SP1, both Exch 2k3 SP2.

On the back end there was SUS on port 80, but I do not think it was
removed
completely. I think the files, db, reg keys were but not the IIS
metabase.

How do I examine the IIS metabase and validate that port 80 is used by OWA
and that the links are OK to the Exchange IS? I would rather not follow
KB320202, I have done it before, but would rather not.

Any reference on the default IIS VirDir settings for auth. I need the
following default settings:

FE - Default Web Site
FE - Exchange
BE - Default Web Site
BE - Exchange

Only the authentication settings. I have the following:

FE - Default Web Site - Anonomouse Auth and Integrated - Require SSL
FE - Exchange - Integrated and Basic - Requre SSL / Forms Auth
BE - Default Web Site - Anonomouse Auth and Integrated - No SSL
BE - Exchange - Integrated and Basic - No SSL

Any thoughts? Maybe an IIS expert could help out?

"Bharat Suneja [MVP]" wrote:

- 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?






.

Relevant Pages

  • Re: OWA logon screen
    ... did you produce a SSL Request from Default Web Site / Exchange Web Site (in ... I just have to get SSL working now. ... Exchange admin. ... I have a certificate enabled within the server and i can click ...
    (microsoft.public.exchange.admin)
  • OWA - SSL exchange 2003
    ... I am trying to Setup OWA to use SSL, I am using the following from 2003 ... Exchange Server deployment guide chapter 8. ... identities for this Web site, verify that the Web site IP address is ... After you obtain an SSL certificate to use either with your Exchange ...
    (microsoft.public.exchange.setup)
  • Re: OWA will not work with SSL
    ... Bob Walker posted their thoughts, ... The entire default web site is set to use port 442 ... > this includes Exchange. ... port 442 and not 443 for SSL, unless that was just a typo? ...
    (microsoft.public.exchange2000.admin)
  • Re: OWA will not work with SSL
    ... Bob Walker posted their thoughts, ... The entire default web site is set to use port 442 ... > this includes Exchange. ... port 442 and not 443 for SSL, unless that was just a typo? ...
    (microsoft.public.exchange2000.general)
  • Re: Exch 2K3 OWA port 80 conflict with SUS
    ... How do I examine the IIS metabase and validate that port 80 is used by OWA ... and that the links are OK to the Exchange IS? ... FE - Default Web Site ... FE - Default Web Site - Anonomouse Auth and Integrated - Require SSL ...
    (microsoft.public.exchange.setup)