Cannot open OWA internally or externally. I think it is because the SSL certificate is corrupted

OWA stopped working internally & externally. We had is setup for SSL and we have an updated cert installed.
When I try https://localhost.com/exchange in the exchange server, Bottom left says "connecting to host 10.11.12.13" after it says connecting to localhost...
then it says "page cannot be displayed"
I disabled SSL just to make sure OWA itself was working. When I went to http://localhost.com/exchange
I got my log in screen. I logged in a 2 separate users and each time after login I got text on th screen that said "Unspecified error".

In my research I learned that if the SSL cert is not installed properly than in Exchange Properties under Secure communications, the Edit button will be faded out. It is not faded out.
But, in both default web site properties and exchange properties, View Certificate is faded out.
This is why I think the cert got corrupted. I don't know how or how to fix it.
I am unable to find any pfx file which is the format of a cert you can install. I do have the cert with a cer extension, but cannot install that one.

For the rest of the settings in IIS, I have compared every setting with those of another client whose OWA is working.

Anyone know what may have caused this and how to fix it????

Thanks in advance.

Mike
Default-Web-Site-Properties.JPG
Exchange-Properties.JPG
DGoncharAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jerry SolomonNetwork  AdministratorCommented:
the good news is that in most cases the certificate is still in the computer's certificate store.  you should be able to click on server certificate, and "ad an existing certificate" to youe web server.  give it a shot.  If it works, it will be a good thing!!
0
DGoncharAuthor Commented:
Sorry,

forgot to tell you, I did try that, but no certificates were listed.
0
Exchange_GeekCommented:
Hello

  1. For Https to work - first, you need to have SSL port opened (by default its 443)
  2. Second, you need to install SSL on default web site
  3. You may want to refer to link: .http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html
Please post your queries and we would be glad to assist.

Take Care.

God Bless.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hey MSSPs! What's your total cost of ownership?

WEBINAR: Managed security service providers often deploy & manage products from a variety of solution vendors. But is this really the best approach when it comes to saving time AND money? Join us on Aug. 15th to learn how you can improve your total cost of ownership today!

DGoncharAuthor Commented:
Port 443 is open. Everything was working fine.
My comments suggest that the cert is corrupted.
Please read my original post again.
Can anyone help in fixing this situation?

Thank you
0
DGoncharAuthor Commented:
Never found cause.
Solution, we were able to find a copy of the cert and reinstall.
As for OWA displaying that text error, found MS article that helped.
http://support.microsoft.com/kb/906907
Although I skipped steps 3-8
And we were back online
0
Exchange_GeekCommented:
Bro, did you even read what i wrote on the suggestions ???

For Https to work - first, you need to have SSL port opened (by default its 443)
Second, you need to install SSL on default web site
You may want to refer to link: .http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html

Now compare your solution...
Solution, we were able to find a copy of the cert and reinstall.

And i'm shocked to read your stating that we were not able to help, if you had doubts or didn't understand the solution given, you should have asked.

WEird...honestly !!!


0
Jerry SolomonNetwork  AdministratorCommented:
While my response was not as thourough as Exchange_Geek's, the point is that the experts let the asker know what that the configuration should be to know if it was right, and the process for installing a certificate.  Helping someone get going, or have a direction to further troubleshoot is valuable feedback. I don't do this for points, but to help others.  
The Experts here helped. That's what this web site is all about.
0
Jerry SolomonNetwork  AdministratorCommented:
When I resolve my own questions, but experts helped, I mark my comment as the accepted solution, but award the most helpful expert(s) assist points.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.