scraftaus
asked on
New Exchange 2016. Exchange ActiveSync does not work
This is a new Exchange 2016 installation on an internally hosted Windows Server 2016.
DNS (Including Autodiscover) is set up.
3rd party SSL certificate is set up.
OWA is working fine. Browser shows secure connection. (Ie. using https://servername.domain.com/OWA
Outlook 2010/2013/2016 connection to mailbox is working fine (internally and externally). Accounts are easily set up via Autodiscover and no SSL errors during account set up.
Send/receive working fine via Outlook and OWA.
When I try connecting via Exchange Activesync on iOS or Android it fails to connect.
iOS says "Unable to verify account information."
Android says "Cannot connect to server"
I checked Activesync status in Exchange Administration console. It's turned on by default and I did not change the settings.
I used the Microsoft Connectivity Analyzer to test Exchange ActiveSync.
Errors:
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
I reseached this and tried troubleshooting steps from other forums.
Exchange Management shell:
Get-AutodiscoverVirtualDir ectory | fl
This shows the correct URL which matches the host name in my SVR record. Ie. servername.domain.com
I put: https://servername.domain.com/Autodiscover/Autodiscover.xml into a browser (externally and internally). After putting in the credentials it shows the expected 600 error.
Please advise of further troubleshooting steps.
Thanks.
DNS (Including Autodiscover) is set up.
3rd party SSL certificate is set up.
OWA is working fine. Browser shows secure connection. (Ie. using https://servername.domain.com/OWA
Outlook 2010/2013/2016 connection to mailbox is working fine (internally and externally). Accounts are easily set up via Autodiscover and no SSL errors during account set up.
Send/receive working fine via Outlook and OWA.
When I try connecting via Exchange Activesync on iOS or Android it fails to connect.
iOS says "Unable to verify account information."
Android says "Cannot connect to server"
I checked Activesync status in Exchange Administration console. It's turned on by default and I did not change the settings.
I used the Microsoft Connectivity Analyzer to test Exchange ActiveSync.
Errors:
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
I reseached this and tried troubleshooting steps from other forums.
Exchange Management shell:
Get-AutodiscoverVirtualDir
This shows the correct URL which matches the host name in my SVR record. Ie. servername.domain.com
I put: https://servername.domain.com/Autodiscover/Autodiscover.xml into a browser (externally and internally). After putting in the credentials it shows the expected 600 error.
Please advise of further troubleshooting steps.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
HI Scraftaus,
Please you need to configure the external url:
Get-ActiveSyncVirtualDIrec tory | Set-ActiveSyncVirtualDirec tory -ExternalUrl "url"
Regards
Valentina
Please you need to configure the external url:
Get-ActiveSyncVirtualDIrec
Regards
Valentina
ASKER
Hi,
I did this via the Exchange admin center>Server>virtual directories
Now the result shows the ExternalURL with the address as well.
I tried the Conectivity Connectivity Analyzer again. It got passed the "failed to obtain an Autodiscover XML response" error but got a new error: "Testing of the OPTIONS command failed. For more information, see Additional Details."
I've attached a screenshot.
When I tested setting up on Android again, this time it auto populated the correct server address but still fails to connect.
Thanks.
M.PNG
I did this via the Exchange admin center>Server>virtual directories
Now the result shows the ExternalURL with the address as well.
I tried the Conectivity Connectivity Analyzer again. It got passed the "failed to obtain an Autodiscover XML response" error but got a new error: "Testing of the OPTIONS command failed. For more information, see Additional Details."
I've attached a screenshot.
When I tested setting up on Android again, this time it auto populated the correct server address but still fails to connect.
Thanks.
M.PNG
Your autodiscover shouldn't be the servername as mentioned:
https://servername.domain.com/Autodiscover/Autodiscover.xml
It should be something like:
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml or https://mail.domain.com/Autodiscover/Autodiscover.xml
Also the autodiscover name needs to be on your SSL cert.
Also do you have DNS setup externally with an Autodiscover A record?
https://servername.domain.com/Autodiscover/Autodiscover.xml
It should be something like:
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml or https://mail.domain.com/Autodiscover/Autodiscover.xml
Also the autodiscover name needs to be on your SSL cert.
Also do you have DNS setup externally with an Autodiscover A record?
ASKER
Hi.
It seems that ActiveSync is working OK for user accounts now. Just not the Administrator account. But that's OK.
I have a wild card certificate set up.
Will there be issues with using servername.domain.com for autodiscover?
I have a separate DNS entries set up for exchange.domain.com also.
Autodiscover.domain.com is also set up as a CNAME.
Everything seems to be working OK now.
Thanks.
It seems that ActiveSync is working OK for user accounts now. Just not the Administrator account. But that's OK.
I have a wild card certificate set up.
Will there be issues with using servername.domain.com for autodiscover?
I have a separate DNS entries set up for exchange.domain.com also.
Autodiscover.domain.com is also set up as a CNAME.
Everything seems to be working OK now.
Thanks.
cool. no it should be fine because it's the srv record that outlook looks for. it's just not best practice.
ASKER
I've only tested ActiveSync externally. I'm not onsite to be able to test internally.
See screenshot of result. The InternalURL shows the correct address.
The ExternalURL is missing. I assume this is the issue. How do I fix this?
Thanks.
K.PNG