asked on

Exchange 2003 SP2 on Windows 2003 SP - http OWA works but https returns page cannot be displayed

Hi all,

Currently have Exchange 2003 SP 2 running on Win 2000 SP4. Added a new server (Win 2003 - later will move to 2012) and installed Exchange 2003. Mail flow is working properly between the two servers. I can access http://server/exchange or http://localhost/exchange fine. If i try https://localhost/exchange i get a page could not be displayed message.

I checked IIS default site and exchange virtual directory port settings
I confirmed the SSL certificate is current (view certificate option)
I did an IISReset

At a loss as to what could be happening. I had installed a new VM with same and got the same results.

thanks

Manpreet SIngh Khatra

Is SSL and 128bit set on the OWA virtual directory

- Rancy

Pradeep

Check the default website settings. This should be the way it is configured :

1) Default Website : Annonymous & Integrated---------NO SSL
2) Exadmin : Integrated------------------NO SSL
3) Exchweb : Annonymous------------------NO SSL
4) Exchange: Basic------------------SSL Optional
5) RPC : Basic------------------SSL Required
6) OMA : Basic------------------SSL Optional
7) Public : Basic+Integrated------------------SSL Optional
8) exchange-oma : Basic & Integrated------------------ NO SSL
9) Microsoft-Server-ActiveSync : Basic------------------SSL Optional.

Before performing this its better to take IIS Backup once.
Once done restart IIS using "iis/noforce" in command prompt.

scoobyftl

ASKER

When i enable SSL and 128bit on the Exchange virtual directory i get the same page not displayed.

scoobyftl

ASKER

Exchange 9 - just confirmed those settings (cpl changes) and i'm still getting page could not be displayed

Pradeep

What happens if you try Https://publicip/exchange on server as well as from External..?

ASKER CERTIFIED SOLUTION

Simon Butler (Sembee)

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

scoobyftl

ASKER

it looks like that might be the problem. Previous cert had a private key associated so i could not just import the old cert on the new mail server. I am requesting a new cert from the new mail server and will see once i import the new one.

Thanks