Forum Discussion
NimbostratusExchange 2010 iApp problems with Mac OSX 10.8 Mail App
We have a pair of LTM's (11.2.1 807.0) running the following version of the Exchange 1010 iApp:
f5.microsoft_exchange_2010_2013_vas.v1.2.0rc1
Clients who use OSX 10.8 with the Apple Mail app are not able to access their Exchange mailboxes. I believe the app uses EWS to connect to the user's mailbox. This is the error that the client shows:
The error initially states “The server returned the error: Connections to host exchange.domain.com on the default ports failed”. Opening the connection doctor, it says it could not connect to the Exchange server and suggests turning off SSL.
We previously had a setup on 10.x running an older version of the iApp did not have this problem. OL for Mac connects fine (although it probably uses MAPI).
Any ideas?
Thanks,
Josh
21 Replies
- We're going to do some testing here to see if we can reproduce it. You should keep working with F5 support as well.
Josh_41258Sounds good. I'm in the process of capturing client side traffic to a 10.7 client which does work. Then, I can compare the two.- Josh_41258Uploaded a working OSX 10.7 packet capture to the case as well. While there are several HTTP/401's for the EWS POST, there are also successful 200's unlike the 10.8 capture.
- Josh_41258Mike,
Were you able to reproduce it? Not getting very far with support.
Josh - hi Josh, sorry about the delay, got swamped with other tasks.
I just tested Apple Mail on OSX 10.8.3 and it works without any issues. The NTLM handshake completes as expected without the client FIN in the middle.
I'm not sure which direction to send you at this point. I'm not sure whether I asked you this before-does it work when you point the Mac clients directly at the CAS, circumventing the BIG-IP?
Mike - Josh_41258I'm not sure that has been tried. I'll get someone to test and let you know.
- Josh_41258Mike,
Hitting the CAS array directly works.
Thanks,
Josh - I'm just having a look at your config on iHealth. I'd like you to try a couple of things for me:
1. Disable strictness on the iApp, if you haven't already
2. Remove the Analytics profile from the combined Exchange virtual server
3. Test
4. If it's still not working, comment out the ONECONNECT:: and NTLM:: commands from the when HTTP_RESPONSE section of the FC_EX2010_DC1_CAS_combined_persist_irule3 iRule
5. Remove the OneConnect and NTLM conn pool profiles from the Exchange virtual server
6. Test - Josh_41258Bingo! Removing the analytic s profile fixed the problem. Any idea what the problem is with the profile?
- I have no idea, other than it's caused issues with Exchange services in the past, specifically OAB. If you don't mind, can you let F5 support know so they can create a subcase for this issue? I'll try to reproduce it here, but having a customer case helps get things fixed faster.
