Issue with Exchange 2010+ federation on BIGIP VE LTM+APM

Thanks for the help Michael,

 

 

I've tried your suggestion and it's confused me more.

 

I tried adding the following to the irule above the ews uri path.

 

"/ews/exchange.asmx/wssecurity" {

 

ACCESS::disable

 

log local0. "Disabled APM enforcement for EWS HTTP path: [HTTP::path]"

 

return

 

}

 

 

Which didn't work and it looked like it caused the uri to break and produce the following log on the cas server

 

Process 53124: ProxyWebRequest FederatedCrossForest from S-1-5-21-2546138925-1139648620-3264887618-5569 to https://mail.pod101.cstack.co.nz/ews/exchange.asmx/wssecurity failed. Caller SIDs: WSSecurity. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

 

 

Then I made a few changes and accidently forgot to remove the original bypass irule I had in place and free/busy started working. :/

 

 

So what I've got now is the previous irule I mentioned in my first post assigned to the virtual and also the above entry in a modified APM_ExchangeSupport_OA_BasicAuth irule.

 

If I remove either the original irule I used or the additional lines I added to the OA_basicauth irule it stops working. Yet they do the same thing.

 

 

I'd really like to have an understanding on why its behaving the way it is as it seems a bit crazy.