Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 681
  • Last Modified:

OWA Intermittent SSL Connection Error

Hi all,

We have a customer with an SBS 2011 Server, running Exchange (2010) on an ADSL connection with a static IP address and a trusted (GoDaddy issued) SSL certificate.

For some reason, much of the time OWA doesn't work and other times it does.  We've tried the big yet simple things:

Reinstalling the SSL Certificate
Replacing the modem
Replacing the network switch
Temporary Disabling the Windows Firewall and Testing
Completely Replacing the SSL Certificate
Disable all non-related sites in IIS (Sharepoint, Client Deployment App, etc).

All with no luck.  Internet Explorer just craps out but Google Chrome gives us an SSL connection error which, when we expand for more details, gives us an error code:

Error code: ERR_SSL_PROTOCOL_ERROR

We're at a loss as to how to proceed here.

If we disable 'Require SSL' on the OWA virtual directly in IIS (within the Default Web Site) OWA works fine so the problem is specific to SSL.

Any help would be much appreciated!

Thanks

Bob
0
Mango-Man
Asked:
Mango-Man
3 Solutions
 
Peter HutchisonSenior Network Systems SpecialistCommented:
A few things to check:
1. Is the latest GoDaddy root certificate on the SBS server and on client machines?
2. Are ports 80 and 443 opened on the Firewall (s) - Server and router etc.
3. Is SSL enabled for all the relevant IIS virtual directories e.g. owa, public, exchange, exadmin, ecl etc.
4. Is the DNS name correctly configured to the correct ip addresses and it matches the address in the SSL certificate.
5. Is the certificate a Subject Alternative Name certificate will all the correct alt subject names added on the server. Exchange 2010 does require additional names e.g. autodiscover, server names etc.
0
 
insidetechCommented:
Did the SSL connection ever worked?
Is it intermittent or just not working as you describe?
If you can provide your URL one may be able to capture the traffic for analysis.
0
 
Mango-ManAuthor Commented:
Hi cmsxpjh / insidetech,

Thanks for your help

I've answered all your questions togehter for clarification:

1. Is the latest GoDaddy root certificate on the SBS server and on client machines?
It's not installed on the client machines and doesn't need to be because its not self-assigned.

2. Are ports 80 and 443 opened on the Firewall (s) - Server and router etc.
Yes - bear in mind it does work sometimes and it currently works on port 80 when 'Require SSL' is disabled in IIS

3. Is SSL enabled for all the relevant IIS virtual directories e.g. owa, public, exchange, exadmin, ecl etc.
Yes - as I say, it works *sometimes*

4. Is the DNS name correctly configured to the correct ip addresses and it matches the address in the SSL certificate.
Yes

5. Is the certificate a Subject Alternative Name certificate will all the correct alt subject names added on the server. Exchange 2010 does require additional names e.g. autodiscover, server names etc.
Yep the correct alt names are on there too, although OWA only requires the FQDN used to access it to be on there (the SANs are for additionals like autodiscover)

Did the SSL connection ever worked?  Is it intermittent or just not working as you describe?
Yes it works intermittently

If you can provide your URL one may be able to capture the traffic for analysis.
Is there anyway I can PM this to you?  Don't want to specific detail on here.

Thanks again for your help!
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Simon Butler (Sembee)ConsultantCommented:
When you did this:

"Reinstalling the SSL Certificate"

What exactly did you do? Did you rekey the certificate at GoDaddy or something else?

The error message is classic interference of some description, which stops the SSL session from establishing. Although it can be a sign of a corrupt SSL certificate.

Simon.
0
 
Mango-ManAuthor Commented:
Hi Simon,

I tried doing a simple rekey and also completely revoked the certificate and issued a new one (done LOTS of these as I manage a web server).  Yep agree everything points to something interfering with the SSL protocol but can't figure out what as all hardware between the phone line and the server has been replaced.

Also - the SSL certificate works just fine when OWA is accessed from the server.  I'm going to get one of our techs to try accessing OWA from inside the network to see if it's some strange port blocking by the ISP.
0
 
Mango-ManAuthor Commented:
have visited site a few times but currently it keeps working from in and out when we're there - need to catch it as it breaks again
0
 
Mango-ManAuthor Commented:
I'd like to reward those who helped and close the question as unanswerable - is there a protocol for this?
0
 
Mango-ManAuthor Commented:
Didn't know how to mark it as unanswerable so have simple closed it and accepted contributions
0
 
Mango-ManAuthor Commented:
For anyone facing the same issue, it was solved by replacing the modem for a THIRD time with a different model of modem.  All of these were provided by the ISP.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now