Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Exchange server behind an ISA 2004 server and from inside the network, it's possible to access Outlook Web Access. I have published the server but from outside the network I'm not even getting to the login screen. The ISA log indicates that the HTTPS traffic on port 443 is being blocked by my default deny-all rule.

How do I go about resolving this problem?

share|improve this question
up vote 2 down vote accepted

Turns out that there was an issue with the SSL certificate. I resolved the issue by deleting the relevant certificates on both the ISA server and SBS server. I created a new certificate on my SBS Server and then exported the certificate (with it's private key) to the ISA server. I changed the OWA Listener to make use of the new certificate and voila!

Thanks for pointing me in the right direction

share|improve this answer

You have to activate SSL (checkbox) on the weblistener for the public IP address.

Do you allow the https protocol (tcp port 443) in your inbound rules? Is it enabled?

There is a good tutorial for ISA Server 2004 here: Publishing Outlook Web Access (OWA) Sites using ISA Server 2004 Firewalls

For ISA Server 2006, look here: Using the 2006 ISA Firewall (RC) to Publish OWA Sites – Single Exchange Server Scenario

share|improve this answer
Thanks for the response but I have SSL enabled and have followed the instructions in that tut, but with no luck. – Istari May 8 '09 at 10:41
Updated my answer: "Do you allow the https protocol in your inbound rules? Is it enabled?" – splattne May 8 '09 at 11:45

If it's hitting the default deny-all rule it means it's skipping your custom rule for some reason.

You need to figure out why that is, check the DNS, ports etc.

share|improve this answer
I've created a rule which specifically allows https inbound. Now I can see the connection being allowed in my ISA log, but users get the following browser error message: Data Transfer Interrupted The connection to concept was interrupted while the page was loading. The browser connected successfully, but the connection was interrupted while transferring information. Please try again. – Istari May 8 '09 at 12:32
That sounds like your connection to exchange server is being disrupted after users connect through isa server... There are quite afew google posts about that message though. – Bravax May 8 '09 at 12:47

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.