Discussion Locked

Probs with SSL on Outlook Web Access

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I have set up an OWA server (IIS 5.0 on Win 2000) which works fine until I put on the SSL certificate - then I get the message page cannot be displayed etc etc. I have checked MS site and they say to make sure the default website is not listening on port 443 for SSL connections but as the OWA is on the default website this doesnt matter. I've tried changing port numbers but it doesnt work. Its definitely a problem with the certificate because the server is listening on port 443 and the packets are passing through our firewall etc. OWA works fine without the certificate but we need it to be secured! Does anybody have any idea whats going on??!

6 replies

by lordinfidel

Questions/Insights:

1. Just to make sure, I have to ask, you did not happen to rename the "Default Web Site"?
to something else. If you did, then your site and certificate is messed up. The owa can only be on "default web site"

2. I am not sure what doc you read "MS site and they say to make sure the default website is not listening on port 443 for SSL"
But SSL does go out over 443. It needs to be listed as the port, or else you will need a url like this https://exchange.domain.com/exchange:port#
I have ours set up for port 80 and 443.
I also set it up so that any one who connects via http get's redirected to https.

But when all is said and done, the requests are going over 443.

3. If you generated your own certificate, THERE WILL be a problem with it. Press yes when presented with that screen. The only way around it is to get an actual cert through a 3rd party. If this is just for your users, don't bother. All you care about is whether or not the passwords are encrypted.

4. Big Suggestion: If you are running thr OWA on the same machine as exchange, DON't. Reason being is for every user who logs on to the OWA, it opens an instance of outlook.

Even the beefiest of servers can get bogged down when trying to deliver mail plus proccess ssl connections and multiple instances of outlook.

Putting the OWA on another server is actually pretty easy. Just use the install disk to install the OWA. It will do the rest. Caveat: users will have to put in
domain\username at the username\password prompt.

good luck

by sarahb

Thanks for your comments but unfortunately they are of no help to me. The default web site hasn't been renamed and it is listening on port 443.

It is a Verisign certificate - I didn't generate my own. And OWA is running on a separate machine toExchange.

Any more suggestions!!?

by lordinfidel

When you registered with verisign what web site name did you give it?

What is the host header you are using, and did you add the host header after you installed the cert?

What happens when you type in https://exchange.yourdomain.com/exchange ?

Is the site just for your users and is there a really valid reason why you need the cert from verisign?

You could try something, this is the way I set ours up (i can send you the address via e-mail so you can see how it reacts). I set up the web server that the OWA is on as it's own cert authority. (Just run option pack and install it). I went ahead and generated my own key using the web servers cert authority.

Have you tried pinging the OWA server on port 443 from the outside?

Doyou have any IP filters set up on the OWA. (It would be done thru the advanced settting in Tcp/IP for that connection)

Have you tried the site on the local machine?
What did it do?

by lordinfidel

Some other stupid things,

Did you make sure that the "Require secure channel when accessing this resource" is checked (Directory security/Secure communications).

Did you check the status of the key in key manager?

Did you bind an address tothe key, thru the key manager?

by shanghai sam

Hi - again thanks for the detailed answer but it didn't help me. I'm not using host headers because apparently you can't with SSL. I needed the cert from verisign because we will be using OWA from outside the company - at clients sites etc and it was more secure to use verisign. We're an MOD site as well so we have to err on the side of caution! I can ping the server and if I do netstat -an it shows that the server is listening on port 443. When I type in http://server/exchange it says that https is required so it reaches the server. As soon as I put in https it says page cannot be displayed. The request is reaching the server because it is logged going through our firewall. This is driving me nuts!! The thing is that it was working originally but then I moved the server into our DMZ and its gone wrong since then. I'm sure I've double checked all settings again and again but I'm just not getting it! The site works from the local machine by the way.

by lordinfidel

You need the host Headers. Very important..... This is where your problem is.

When Verisign issued the cert to you, it should of have been issued to a web site name. The cert has no idea what name to bind to.

When you say that you will be using it at client's sites, you mean you have clients who have e-mail being hosted on your server. Or are your employees accesing their e-mail from clients sites.

Our OWA can be accessed from the net by anyone of our employees. The cert is not any more or less secure than that issued by a 3rd party. The whole point of the 3rd party issuer is the trust factor, not the security factor. Someone who does not know your company and trusts the third party will then trust your cert.

Remove the cert. Then add the host header. Stop/Start the site. Then add the cert back in. Then bind the address to the the key.

This should solve your issue. If all you want is security and the trust factor is not an issue, generate your own cert.

But only after you add the host header.

The side affect of generating your own cert is a cert window popping up when users try to go to the site. (https://exchnage.vdat.com/exchange or http://exchange.vdat.com ) Your users will need to press yeswhen the cert is presented.

good luck

This discussion is closed to new replies.