Exchange 2003 and OWA

At a client, we have the following situation:

They have a Exchange server that is acting as the front end and back end server.  The clients at the site can view their email via OWA by going to the and logging in.  They see their inboxes the way they’ve seen their Outlook 2003 app inboxes.
We configured the firewall to pass HTTPS traffic through to  From the outside, when I hit their web address in HTTPS, I get directed to enter my username and password, which I do.  I then get a page that says “Under Construction”
The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured.
Please try this site again later. If you still experience the problem, try contacting the Web site administrator.
This seems to be a something with the IIS server.  What, I am sorry to say, I do not know.  Please keep in mind that the web site on port 80 points to one server, the 443 address points to the exchange server.  

What am I missing here?  SSL certs are enabled, when I log in I get the little locked icon in the lower right hand corner, I get rejected with wrong authentication and I see that under Web extensions, Microsoft Exchange server is allowed on the Exchange server.  I assume that I am not pointing to the correct web page somewhere in IIS.

Help is REALLY needed.

Who is Participating?
It sounds like you're hitting the root of that web site, not the /exchange virtual root.  What happens when you go to

By default, the root of the website within IIS on the Exchange server will give you that 'Under Construction' page.  I created a new page, default.htm, and placed it in the root of the Inetpub\wwwroot folder.  Within that 'default.htm' page I added a "meta refresh" tag that automatically forwards the user to the /exchange virtual.  That way if they type in the full address (including /exchange at the end) or just the url itself (minus /exchange), they'll get bumped to the same location.  Make sense?  I'd be happy to show you the meta refresh code, if you like.

hglobusAuthor Commented:
OK.  I must be totally stressed out.  'Cause I thought I'd checked that, but of course, it worked.

Yeah, if you could send the meta refresh code along, that'd be great.  

Appreciate it.
Glad I could help.

As for the "meta refresh" code, just create a new page in the Inetpub\WWWroot folder (default.htm, or something like that), and add the following code.  Cut between the SNIPS, of course, and remember to change the 'www.yourdomain' link to match the proper domain name.  

Also, the "0" just before the URL indicates how long to wait (in seconds) before redirecting.  I usually have the page redirect right away (hence the zero), but you could change that if you so desired.




<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">




hglobusAuthor Commented:
Hmmm.  Problem when I use the code.

Here is what I get:

I go to https:\\\exchange and get:
an Outlook webpage login. I login with credentials and I get in fine.
(I think that I already accepted the cert, so I'm not asked to accept again.)
it works.

I go to https:\\ and get:
A cert window pops up that I am asked to accept.  I do.
Login popup window.  I login with credentials and then I get asked to login with
an Outlook webpage login (same as above).  I login with the same credentials and get
"The page cannot be found"  - HTTP error 400 when it is goes to

So, where is the disconnect?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.