Keep experiencing issues with IE11 - using Cisco ASA 5510 VPN -> Exchange 2013 CU8. 

:-( Something Went Wrong

X-Clientid: GVDX-TBXO-EUDH-YLOA X-OWA-Error: Unknown;handle boot error failed X-OWA-Version: undefined X-FEServer: EXCHANGE X-BEServer: Undefined Date: (time stamp is off for some reason)

This is working fine in Firefox and Chrome externally. Everything works internally. 

Any ideas where to look? 

Thanks,

I'm willing to bet that if you enable compatibility mode in IE when connecting externally that it would work fine.

I ran into this same type of behavior with SharePoint 2013.  The problem is that .NET 2.0 and .NET 4 has a bug in the browser definition files in unpatched versions.  Specifically, these definitions are only applicable to a certain range of browser versions.  Any newer browser (like IE 10 or 11) are not supported and ASP.NET sees them as unknown browsers and defaults to a down-level definition, which doesn't support features like JavaScript or Silverlight.      

So I would check your .net versions and patches/updates on your CAS servers.

• Edited by Corey Riley 17 hours 49 minutes ago

Exactly what do I need to be looking for with .NET 2.0 and .NET 4?  Any permissions I need to check?  I installed 4.5.2 required during pre-requisites. 

Are there any logs I can check out?  I am a bit stumped at this point.

Thanks,

I'm willing to bet that if you enable compatibility mode in IE when connecting externally that it would work fine.

I ran into this same type of behavior with SharePoint 2013.  The problem is that .NET 2.0 and .NET 4 has a bug in the browser definition files in unpatched versions.  Specifically, these definitions are only applicable to a certain range of browser versions.  Any newer browser (like IE 10 or 11) are not supported and ASP.NET sees them as unknown browsers and defaults to a down-level definition, which doesn't support features like JavaScript or Silverlight.      

So I would check your .net versions and patches/updates on your CAS servers.

• Edited by Corey Riley Wednesday, June 17, 2015 1:40 PM

Hi mjmummert,

Thank you for your question.

We could check if we have enable Add-on in IE->Tool.

If the issue persist, you could contact your VPN supplier to check it because it is fine in internal, it means the Exchange and IE work without any problems.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Try enabling compatibility mode in IE11 for your external URL and see if it still occurs.  Go to "Compatbility View Settings" and add your external URL.

If that fixes the issue then go to Windows Update on your CAS servers and make sure there are no .Net related updates to install.

*edit*

Does this behavior occur on other workstations as well?

• Edited by Corey Riley 18 hours 54 minutes ago