Forum Discussion

vallesm77_95699's avatar
vallesm77_95699
Icon for Nimbostratus rankNimbostratus
Dec 19, 2014

Exchange iApp 1.3.0 and disconnection of Entourage 2008 EWS

Hello,

 

I use the Exchange iapp 1.3.0 on LTM BIG-IP 11.5.1 Build 2.0.121 Hotfix HF2. I don't use APM. My environment Exchange is 2010 SP3 with 2 servers on DAG configuration (multi-role CAS/HUB/MBX).

 

I've 20 MAC OS with Entourage EWS and all are disconnected several time per day. Appears a new authentication popup.

 

Do you have an idea of the problem ? I think to a persistence problem ?

 

Thanks

 

application delivery
availability
BIG-IP Access Policy Manager (APM)
deployment
devops
iApps
LTM
security

3 Replies

  • Michael_Jenkins's avatar
    Michael_Jenkins
    Icon for Cirrostratus rankCirrostratus
    Dec 19, 2014

    I'm not sure if this would help with your problem, but one of the things we noticed when we were setting up Exchange 2013 is that there are some extra steps that need to be taken to get things working properly (at least for us). I'm not sure if you've looked at the deployment guide, but I know we had to add some additional iRule stuff to get everything working appropriately. It may be worth taking a look at to see if it can help at all.

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Dec 19, 2014

    Hi vallesm77,

    There is logic in the iRule created by the iapp to disable OneConnect if the BIG-IP sees Negotiate in a response. This fixes similar behavior in Windows clients; you might try disabling strictness on the iApp and manually editing the iRule to disable OneConnect for all EWS requests:

    "/ews*" {
             Exchange Web Services.
            pool /Common/exchange_2010.app/exchange_2010_oa_pool3
            ONECONNECT::reuse disable
            ONECONNECT::detach disable
            NTLM::disable
            COMPRESS::disable
            CACHE::disable
            return
        }