Forum Discussion
IOS client telling that it can't connect to Exchange, works on Android
How mail is set up on the device is likely irrelevant here. S4B uses the Exchange Web Services interface to Exchange Online or Exchange on-prem to pull that data. It's possible the iPhone client isn't successfully handling the autodiscover for the user (this usually happens when the SIP doesn't match the Primary SMTP). It's tough to say why Android would work and iOS wouldn't. I'd suggest manually configuring the Exchange Web Services URL on the S4B on IOS and see if that corrects the issue. (settings -> My Credentials -> Exchange)
If that works then you have to chase down with the iOS side isn't autodiscovering the EWS settings.
- Kai StenbergFeb 28, 2017Iron ContributorDid find out that they do not use the autodiscover in the url, but PIM.contoso.com. Did this manual, well then it worked on the Iphone. :-)
Maybe create a DNS record in some way to route autdiscover.contoso.com to PIM.contoso.com and then it might work :-)- Joshua WidupMar 06, 2017Brass Contributor
Hmm...that's interesting. I wouldn't advise trying to redirect the autodiscover record - what I would suggest would be to get it back to using autodisvoer for S4B mobile. The user experience is far better if they're able to just log in and everything works as expected. Manual configurations are frought with chaose - that's just my opinon/experience. ;)
- Kai StenbergFeb 24, 2017Iron ContributorHi, I have asked my customer to try this. Will Get back with some update later