Forum Discussion
brent112_11716
Mar 22, 2012Nimbostratus
Yes, we have removed the oneconnect profiles, tcp profiles, http profiles, everything one by one trying to see what would fix it (nothing worked).
I am running a version of the Exchange 2010 iAPP that has not been released yet, and in the persist irule it contains the code to disable OneConnect, this code was not in previous versions.
when HTTP_RESPONSE {
if { [HTTP::header values WWW-Authenticate] contains "Negotiate" } {
ONECONNECT::detach disable
}
}
So should the above really not be there?
Everything is pretty much an out of the box setup as far as Exchange and the F5 VS goes, nothing fancy at all.
It should be said that we have other applications running on the F5 without issue, so whatever the problem is it definetley seems to be related to the Exchange iAPP.