OWA, E2k "page can not be found" problem


Here is the environment:

1 Server, only server in the forrest, running Win2K as AD forest root DC with Exchange 2000 back-end and OWA on a private (internal 172.16.x.x) network.

Firewall that does NAT between this network and the internet.

Two external IP addresses, translated directly two two internal addresses.  For external DNS lookups, i.e. WM.SomeCompany.Com, both ports 80 and 443 are open to the "second" site which has only an HTML/js redirect page to the OWA web site.  The OWA web site is accessable only via SSL (port 443).  (to make life easier for the users, eh?)

Okay - I can use the encrypted (OWA) site from the internal network - using machines that are in the AD domain (apparently) without difficulty.

Externally, Internet Explorer redirects correctly.  The SSL connection is established (cert-admin created certificate in use) and I am prompted with the OWA logon prompt (username, password, domain).  After entering correct logon credentials, I am greeted with the 'ole HTTP 404 - File not Found error.

The redirected site is using the external side of the firewall's IP address, so the URL re-directed to is such like "".

If I THEN at this time ask my browser to access "", I am greeted with the generic IIS5 "under construction" page.  If after THAT I re-enter the correct url "", the OWA client uses the logon credentials provided above and logs me in correctly.

I'm totally stumped.  

TY VM for your help with this one!

Points will increase if this takes a long diagnosis to resolve!

-- Scott.

Who is Participating?
David WilhoitSenior Consultant, ExchangeCommented:
Is this the article you followed to force client SSL?


David WilhoitSenior Consultant, ExchangeCommented:
Why are you redirecting to the external side of the firewall? To get the ogin screen, you've already come thru the firewall, then you tell it to redirect to a name/IP address outside the firewall, and come back in?

"For external DNS lookups, i.e. WM.SomeCompany.Com, both ports 80 and 443 are open to the "second" site which has only an HTML/js redirect page to the OWA web site."

What is the 2nd site? Are you redirecting thru a secure site, back into Exchange OWA?

scdavisAuthor Commented:

Here is the redirect code that I put up:

<html> <head> <title> SomeCo Email
<body onload="document.click.submit();" bgcolor="#ffffff">
 action="" method="post" name="click"</form>

It's just a simple HTML/js redirect.  I can't figure out what's wrong with that?  

Regardless, I'm trying out the method in q279681 - let ya know how it goes in a bit.

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

David WilhoitSenior Consultant, ExchangeCommented:
It needs an FQDN, I would think. But yea, let me know how it goes...

scdavisAuthor Commented:
Thanks, Kidego.

I've moved onto a 2k3 installation - but I'm pretty sure your answer is correct.  :)  

Best wishes.

David WilhoitSenior Consultant, ExchangeCommented:
Oh, you'll LOVE E2K3....enjoy!


Let me know how it turns out....
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.