Solved

Exchange 2003 and OWA

Posted on 2004-09-27
4
318 Views
Last Modified: 2008-03-04
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 192.xxx.xx.xxx/exchange 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 192.xxx.xx.xxx.  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.

Thanks.
0
Comment
Question by:hglobus
  • 2
  • 2
4 Comments
 
LVL 6

Accepted Solution

by:
chumplet earned 500 total points
ID: 12164217
It sounds like you're hitting the root of that web site, not the /exchange virtual root.  What happens when you go to https://www.theirwebserver.com/exchange?

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.

Chumplet
0
 

Author Comment

by:hglobus
ID: 12164378
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.
0
 
LVL 6

Expert Comment

by:chumplet
ID: 12164546
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.

Chumplet

===========SNIP=============

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<META HTTP-EQUIV="refresh" CONTENT="0;URL=https://www.yourdomain.com/exchange">
<title>Redirecting...</title>
</head>

<body>

</body>

</html>

===========SNIP=============
0
 

Author Comment

by:hglobus
ID: 12166131
Hmmm.  Problem when I use the code.

Here is what I get:

I go to https:\\www.domainname.org\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:\\www.domainname.org 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 https://www.domainname.org/exchweb/bin/auth/owaauth.dll

So, where is the disconnect?
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

709 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now