Microsoft remote connectivity tester
Question asked by Heimir Eidskrem - 7/23/2020 at 10:19 AM
Answered
Does this work?

When I select Exchange server then run the Outlook connectivity it returns:
No account settings were returned from the Autodiscover response. 

Is this because something is wrong with our setup or does the tester work with smartermail?

11 Replies

Reply to Thread
1
Heimir Eidskrem Replied
Why no response to this?

Smartertools do you know if this works or not?



0
Todd Hunter Replied
How else can we test the MAPI?  Is there another 3rd party test we can  use?
0
Urs Replied
Hello Heimir

guess you had response but maybe something missing.
please expand upper section with xml response - is it really empty, or rather incomplete ?
0
Heimir Eidskrem Replied
Urs,

The question is if the analyzer works or not.
Smartertools needs to answer that.


0
Urs Replied
ok I see
For me the analyzer did not work, I had always message
"The EXCH provider section is missing from the Autodiscover response."

However SmarterMail told me in ticket to just try it with Outlook and it worked, even this section was missing.
So it was just "not nice" and I closed ticket.

According MS article the "EXCH" section is even required if using only RPC over HTTP.
https://docs.microsoft.com/en-us/connectivity-analyzer/missing-exch-element-autodiscover-xml-response?redirectedfrom=MSDN

I could not see this section in SM XML response, so hope they will fix it in future that the MS Test runs accordingly.



0
Heimir Eidskrem Replied
The issue will be with clients that uses the tool and it fails.
They will point the finger at us and we then will need to deal with that.

Not sure why its so hard for Smarterools to answer this question.
Also, not sure why its so hard to get a response now.

1
Larry Duran Replied
Employee Post Marked As Answer
Hello, as Urs pointed out the Microsoft Connectivity Analyzer will not pass with our implementation of autodiscover because it doesn't have the EXCH type in the response.  Our MAPI implementation does not use RPC over HTTP, or any RPC calls, but it does use MAPI over HTTP.

With this in mind, when an Outlook client is trying to autodiscover to SmarterTools (or any Exchange Server) it specifies that it is capable of receiving MAPI over HTTP responses.  The Microsoft Connectivity Analyzer doesn't do this so it technically doesn't test receiving a MAPI over HTTP autodiscover response.

In regards to testing MAPI autodiscover respones, we will use Fiddler or the autodiscover logs to see what the client is requesting and what we responded with to troubleshoot issues.  If you are correctly getting a MAPI autodiscover response and you're still not able to get MAPI to connect then you may want to view the KB, https://portal.smartertools.com/kb/a3491/set-up-a-mapi-account-in-outlook-2016-or-2019-for-windows.aspx, and if that doesn't help then I'd suggest opening a support ticket where we may need to collect some info, like a Fiddler trace.
Larry Duran
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Heimir Eidskrem Replied
Hey Larry,

Thank you for the response.
We need to know whats working whats not.
We started with the private beta and moved in to the public beta.
Knowing whats expect to work is needed.
A simple yes or no would be great from time to time.


0
Jason Earle Replied
I tried but Outlook always fails to add the account. Not sure if I am missing something but I cannot get this to work. 
0
Heimir Eidskrem Replied
Jason,
If you try the microsoft connectivity analyzer and you get a fail.
Expand all the tests.
Ignore the last step where it fails "The EXCH provider section is missing from the Autodiscover response.'

if you can't get a green check on the autodiscover then adding the account is an issue.
You should have this "The Autodiscover XML response was successfully retrieved. " in one of the tests.

You can still  use the analyzer, it will fail but only on the last step as mentioned above.


0
Jason Earle Replied
Got it working after, think I just had to be patient for my DNS to propagate.

Reply to Thread