Link to home
Start Free TrialLog in
Avatar of montcadalr
montcadalr

asked on

owa: https not working?

Hello

I have a owa over Exchange 2003 server.
It works fine on LAN, but for some reason, it doesn't work for external access since last week. It worked fine for months without troubles, but now it doesn't.

What I have is that when I write my URL :https://owa.myspace.com/exchange, a page not fount - DNS error is displayed on my internet explorer.

If I write http://owa.myspace.com/exchange, a SSL-needed connection is displayed. So I arrive to my ISA Server in http but not in hhtps? Is that possible?

Thanks a lot.

ASKER CERTIFIED SOLUTION
Avatar of kristinaw
kristinaw
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of hstiles
hstiles

Has anyone played around with your firewall or IIS config to prevent port 443 access to the Exchange server?  If it works internally, then that seems quite a plausible reason.

Avatar of montcadalr

ASKER

Owa expires??? :-O

I will check the ISA configurations.

Thanks.
an expired cert on your OWA server would generate a browser warning to the effect that the certi had expired or is not yet valid, but wouldn;t prevent acess.
i have seen it where an expired cert will cause owa to just flatly bomb out. more than once.
 
https://www.experts-exchange.com/questions/21922968/OWA-was-working-just-suddenly-stopped.html
Montcadalr's original post states that OWA works internally which I would assume rules out the expired cert issue.
The kristinaw post with the cert issues shows the exact error that I have on my internet explorer when I connect.
I've deleted the owa server on my ISA and recreated the server publishing on my ISA and now works, so it's not the cert 'itself'?, it's some expiration on the ISA too?

My cert expires in three months, it's free to create a new one? I would like to have a brand new one to prevent this errors, I'm still not sure about what is causing the error...

Thanks.
a new cert will cost.  A cheaper alternative to verisign, etc... is www.instantssl.com.  It costs around £130 for a 3 year pro certificate.
mont, glad you got it fixed. i think going with a paid cert is better for a number of reasons. i've always been happy with thawte.

kris.
you might also want to make sure isa has the most current updates/sp available. i'm not an isa expert but given the problem looked like it may have been with isa it might not be a bad idea.