 Question concerning testing ActiveSync using Microsoft Remote Connectivity Analyzer [message #148042] |
Wed, 29 April 2020 22:59  |
blackbox
Messages: 46
Registered: May 2006
|
|
|
|
I'm troubleshooting an ActiveSync related issue concerning connectivity from a web based sales platform.
While troubleshooting I bumped into an issue with Microsoft Remote Connectivity Analyzer (https://testconnectivity.microsoft.com).
For those of you using ActiveSync, have you ever tested your server's ActiveSync using the analyzer?
If so, was the test successful?
I've so far been unable to receive a successfully result.
For the most part (other than a single instance mentioned above) I have many different devices seemingly connecting and communicating with the server over ActiveSync without issue.
From looking at Kerio's ActiveSync debug output during a test connection attempt, it looks like the site may be attempting to use ActiveSync v12.0.
[29/Apr/2020 13:43:14][12744] {activesync} Receiving request from 168.61.212.41:2493: Version: 12.0, Command: FolderSync, Device Id: 1049192159, Policy Key: <no policy key>, Device Type: TestActiveSyncConnectivity, User: user<_at_>domain.com, User Agent: Microsoft-Server-ActiveSync/12.0+(TestExchangeConnectivity.com)
According to Kerio's documentation Connect supports ActiveSync version 14 and higher, suggesting connecting clients using versions of ActiveSync less than 14 may experience erroneous behavior.
https://manuals.gfi.com/en/kerio/connect/content/email-clien ts/activesync/setting-a-compatible-exchange-activesync-versi on-for-specific-mobile-devices-1799.html
I may attempting to add the test site's user-agent to Kerio's ActiveSync v14 exclude list. Perhaps this may change test results. This will need to wait for an available maintenance window to stop/start the server.
In the meantime, I'm wondering if this version requirement may possibly have something to do with test results. I'm wondering if any other Kerio administrators have had success running the ActiveSync test via https://testconnectivity.microsoft.com.
For me in my testing it looks like failure is within the final state of the test, during the FolderSync command, with output "A Web exception occurred because an HTTP 400 - BadRequest response was received from Unknown".
Test output below:
The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
The Exchange ActiveSync test failed.
Additional Details
Test Steps
Attempting to resolve the host name server.domain.com in DNS.
The host name resolved successfully.
Testing TCP port 443 on host server.domain.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Testing HTTP Authentication Methods for URL https://server.domain.com/Microsoft-Server-ActiveSync/.
The HTTP authentication methods are correct.
An ActiveSync session is being attempted with the server.
Errors were encountered while testing the Exchange ActiveSync session.
Test Steps
Attempting to send the OPTIONS command to the server.
The OPTIONS response was successfully received and is valid.
Attempting the FolderSync command on the Exchange ActiveSync session.
The test of the FolderSync command failed.
A Web exception occurred because an HTTP 400 - BadRequest response was received from Unknown.
HTTP Response Headers:
Connection: Close
MS-Server-ActiveSync: 8.1
X-UA-Compatible: IE=edge
Content-Length: 0
Date: Wed, 29 Apr 2020 19:59:47 GMT
Server: WebServer
Elapsed Time: 96 ms. |
|
|
|
|
|
Members
Search
Help
Register
Login
Home
