• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 372
  • Last Modified:

OWA (Exchange 2007) not working externally for IE

We have a CAS server running Exchange 2007 on Server 2008 R2 Enterprise that was working fine until today. Nothing should have changed; no updates have been installed, I am the only one who makes administrative changes to this server, etc.

OWA works normally on our internal network. Externally, OWA works as intended with Firefox. With IE 8/9/10 (and I would assume 11), all that happens is IE errors out instantaneously with "Internet Explorer cannot display the webpage".

Any help would be greatly appreciated.
0
synaptix
Asked:
synaptix
  • 4
  • 2
1 Solution
 
David CarrCommented:
Try using compatibility mode for the IE browsers with OWA 2007. Also you could try disabling your antivirus on the machine trying to connect to OWA and see if it works.
0
 
synaptixAuthor Commented:
Thank you, but compatibility view has no effect, nor does adding to trusted sites/etc. Also, this is not a feasible solution as we have over 100 users who must be able to access OWA remotely.

So far I have gone through IIS and checked all redirect settings, permissions, etc. Nothing appears out of the ordinary. We have also restarted IIS, restarted the CAS server, and looked through the IIS logs.

It would appear that users trying to connect externally with IE do not even show up in the IIS logs.
0
 
Simon Butler (Sembee)ConsultantCommented:
If it isn't showing in the logs, then it has to be outside of Exchange.
The error you have posted often means the SSL session cannot be established, but even that is logged.

Check your firewall and turn up logging on it if you can. If it works internally then it is almost certainly something outside of Exchange.

Simon.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
synaptixAuthor Commented:
My thoughts were similar, but there's nothing I can think of that would selectively block browsers without some real effort to do so. Recall that Firefox works both internally and externally, but Internet Explorer only works internally.

I've had our network admin double-check our firewall/router configs and the only rules in place related to Exchange are translations simply allow the traffic to pass in, and on the appropriate ports (80, 443, 110, 995, 143, 993).

Exchange Connectivity Analyzer (testexchangeconnectivity.com) is not reporting any issues for any of the services we have configured.

Given the circumstances, what kinds of things should I look at on the outside that might be able to cause something like this?
0
 
synaptixAuthor Commented:
Oddly enough, the issue seems to have resolved itself. External connectivity with all browsers appears to be working now. I have no idea what corrected this, as the OWA site, IIS services, and even the server itself were restarted throughout the process without effect.

After leaving the system alone for a while, everything appears to be working normally again. Multiple users have confirmed this.

I'm glad that we're no longer experiencing problems, but I'm very disappointed at the fact that we may have to chalk this one up to a "Microsoftism", and that we may never know the "true" cause of our problems.
0
 
David CarrCommented:
Those Microsoftisms can be frustrating. Glad your issue resolved itself.
0
 
synaptixAuthor Commented:
Issue resolved itself. No cause for the issue was ever found.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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