When SSL is turned off I can access OWA via http:// internally and externally but when I enable SSL we get page can not be displayed with no error messages. Once SSL is enabled and I try to access via http:// I get a page that states that the site requires secure access, HTTP Error 403.4.
The environment is a single Windows 2003 Standard server acting as a DC, Exchange server and terminal server. We have a Netopia 3347 router with ports 80, 25, 3389, 443 and 143 open and pointed to the server. Exchange 2003 has SP2 installed.
I installed certificate services as an enterprise CA, generated a certificate request in IIS under the default web site, used the server.domain.com as the common name, saved the request, accepted it thru the internal certificate website, and generated a base 64 encoded certificate and then appended the certificate to the default website. I checked the Require SSL channel and require 128 but encryption, allowed anonymous access and granted all IP access.
What did I miss?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I took the SSL off of the default website and enabled it only on the sites you indicated with 128 bit checked and unchecked. When I try to get access from the server using https://server/exchange I get the same result, page can not be displayed. Anything else I can test?
You cannot turn SSL on and off.
It is either there or it isn't. Don't make the mistake many make who think that REQUIRE SSL is the option to turn it on and off - it is not. All require SSL does is throw an error if you use HTTP. You can use SSL with that option turned off.
Your first mistake was trying to save money by using certificates services. It is a false economy because anyone accessing your server will get security warnings about the certificate. Telling users to ignore security warnings is not a good idea.
You can purchase valid SSL certificates for US$30/year.
If nothing loads at all then the usual reason is the certificate is corrupt. If things work correctly without SSL, then that is the prime cause. If the SSL certificate is corrupt then the secure session cannot be established and you will get an error message.
Simon.
Mestha, thanks for that correction on SSL on and off.
I do get a 403.4 message when using HTTP, but when I Use HTTPS I get page cannot be displayed only, no certificate error mesasge appears. I am looking into getting a certificate, but I need permission to do that first. In the meantime, should I try to generate a new certificate?
The test I am using is accessing the OWA site firectly from the server's brower (IE8) using http(s)://server/exchange.
Ignore the require SSL setting. If you have a certificate in place then you should be able to use HTTP and HTTPS interchangeably.
If nothing loads when you use HTTPS, but the same URL works with HTTP, then the secure session isn't being established. That points to a bad certificate.
You could use the selfSSL tool within the IIS Resource Kit to create a self generated certificate for testing purposes, but I wouldn't recommend its use in production. Telling users to ignore certificate warnings is a bad idea.
Simon.
The Earle, this seems like a classic firewall issue to me correct me if I am wrong mestha! :)
Your firewall rule you have stated that 443 is open but whats its authentication method:
External - NAT Public IP - Private IP
If so this should be changed to
External & Internal - NAT Public IP - Private IP
IMPORTANT - Please attempt this test enable SSL as you are before and add the following registry key in the default OWA registry location on the server:
HKEY_LOCAL_MACHINE\SYSTEM\
AllowRetailHTTPAuth - DWORD Value 1 ***Important do this as a test only please for the obvious reason its not best prac to have everything sent over clear text***
Then will SSL on do http://server/exchange or http://server if you have /exchange automatically redirecting
DOH just read that again your doing https://server/exchange so your not going to the firewall.......hmmm interesting
Business Accounts
Answer for Membership
by: Narayan_singhPosted on 2009-10-10 at 12:49:50ID: 25543525
You will not be able to access OWA using http once you have enabled SSL.
Make sure you have port 443 opened and natted correctly.
check if you can open OWA over Https internally anf from Server itself,if its working internally its gotta be issue with firewall.
Make sure you dont have SSL enabled on default Web site it should be enabled on Exchange,Microsoft-Server-