Any update on this? I have a new SA4500 we're getting ready to deploy running 6.5R2 - no legacy stuff from older configs, but having the same issue. FWIW, for various reasons we're actually using the same Authorization Only URL for both EAS and external OWA access (don't ask...) and OWA via this path is broken as well. It seems to be the Authorization Only functionality that is broken, not specifically EAS. I see the same thing descibred above when doing a TCPDump - I can se my client hit the IVE, but the IVE never sends any traffic to the internal resource - I've tried both hostname and IP for the internal resource, and no dice either way. Same thing happens for any other authorization only URL I configure. The weird thing is, the very first time I configured the auth only URL, it worked for a period of time. Then it just stopped and started throwing the 500 errors. I've deleted it, recreated it, rebooted the device, created other auth only URL's pointing to the same as well as different internal resources, and nothing. If no useful updates, I'll go ahead and contact JTAC as well and post ticket here for cross reference. Thanks,
... View more