For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Joe_5599_134300's avatar
Joe_5599_134300
Icon for Nimbostratus rankNimbostratus
May 08, 2014

iApp- Exchange 2010, Android Mobile Devices using Autodiscover and Active Sync Failing

I have all MS Exchange services working with one F5 VS/IP. I have just upgraded the Exchange iApp to v1.3.0 All external services work from laptops, iPhones and ipads except for some...
application delivery
devops
iApps
iRules
mikeshimkus_111's avatar
mikeshimkus_111
Historic F5 Account
May 08, 2014

Hi Joe, this just started when you upgraded to v1.3.0? Which version of BIG-IP are you running?

 

thanks

 

Mike

 

  • Joe_5599_134300's avatar
    Joe_5599_134300
    Icon for Nimbostratus rankNimbostratus
    May 08, 2014
    No it was happening during our testing on the v1.2 template last week. We are not yet live on the F5 and trying to UAT all before go-live.
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    May 08, 2014
    OK. What are the specific issues? Here's a list of known issues from MS: http://support.microsoft.com/kb/2563324 I recommend opening a case with F5 Support and posting the case number here so I can track it and take a look at your config. They can also take some packet captures to try and discover what's going on.
  • Aviv's avatar
    Aviv
    Icon for Cirrus rankCirrus
    Jan 25, 2017

    I have problem connecting LG G3 (android 5.1)smartphone with exchange active sync. i have an exchange 2010 bigip ver 12 and iapp 1.51 and i'm using apm. the problem is the same with iapp 1.6. other android smartphones and also ios devices does not have problem . can some tell me why the problem is only on LG smartphone? how to investigate the problem?

     

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Jan 25, 2017

    Hi Aviv, if you set APM logging to "debug" and tail /var/log/apm, hopefully you can gain insight into the problem. You will need to identify the APM session for the problem device and then match it to log messages. If you can post sanitized log output here, I can take a look.