Forum Discussion

tech_contact_90's avatar
tech_contact_90
Icon for Nimbostratus rankNimbostratus
Jul 15, 2010

Problems with Outlook Anywhere

Running 9.4.3 Used the f5 doc to for OA, OWA, and Active Sync OWA is working fine, SSL is offloaded. I havent tested Active Sync yet, but we are stuck on Outlook Anywhere. Outlook simply wont connect. I am unsure where to begin troubleshooting. Everything seems to be setup properly, but obviously I must have missed something. If I point directly at the Exchange server and bypass the BIGIP it works ok so I feel confident the exchange is working

6 Replies

  • I'm not too familiar with "Outlook Anywhere" but standard troubleshooting would have you get packet captures between you and exchange and compare them to a capture between you and the F5.
  • Not that it's related to this problem, but I'd also suggest upgrading to 10.1.0HF2 when you can as there have been a lot of improvements and fixes since 9.4.3.

     

     

    Aaron
  • Thanks, we will look into that. Right now, that is not an option for us. As for the network trace, the only information i see that might be relevant is I am getting a 401 Unathorized error when going through the BIGIP, that I dont get when i am going direct. Any other ideas?
  • Posted By tech_contact on 07/16/2010 02:44 PM

     

    Thanks, we will look into that. Right now, that is not an option for us. As for the network trace, the only information i see that might be relevant is I am getting a 401 Unathorized error when going through the BIGIP, that I dont get when i am going direct. Any other ideas?

     

     

    Almost seems related to SSL termination - but not sure. Can you simply set the F5 up to passthrough SSL connections, rather than terminating them?
  • There's a new post on this here:

     

     

    http://devcentral.f5.com/Forums/tabid/1082223/asg/62/showtab/groupforums/aff/25/aft/1174135/afv/topic/Default.aspx

     

     

    Aaron
  • Phillip_Hocking's avatar
    Phillip_Hocking
    Historic F5 Account
    Typically when I see this it is because the rpc vip is not defined with the correct persistence profile. You can call in and open a ticket, even though those deployments are outside the scope of our support we can provide best-effort troubleshooting.