Solved

Office 365 - Autodiscovery not working

Posted on 2015-02-18
8
582 Views
Last Modified: 2015-02-24
Hello,

Our customer is using Exchange on-line plan P1, with Outlook 2010 as the client.

Their are having issues with their email calendar system. some employees get the following error when trying to access the  free / busy data:

     No information; No Free/ busy information could be retrieved; Your server location could not be      
     determined; contact your administrator

However, when connected to the private network, this problem does not arise.

To me, this would indicate a possible problem with records defined in the company zone file as the auto discovery is what appears to be failing (according to what I read on the internet).

For instance, when adding a new user in Outlook from the private network, the dialogue box for connecting to Exchange (online) prompts for user name and password; However, when performing the same steps outside of the network (without VPN and different DNS server), the dialogue box for connecting to Exchange (online) lists the server name and then asks for the username and password.

The server name name that appears in the server name field is:  domain.com

Is this correct? I would think that this value is incorrect.

For access the free / busy data of colleagues (in same domain), one user (external) reported that it was not working, two hours later it was working and then two hours later not working.

Is it possible that there is some problem within Microsoft ?

Any suggestions / assistance in resolving this problem would be greatly appreciated.

Thanks,

Mark





T


When they are remote (no VPN)
0
Comment
Question by:mbudman
  • 4
  • 4
8 Comments
 
LVL 38

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 40618359
Where is your Autodiscover pointing at? Are all the mailboxes located in O365 or there are some on-prem? Run the Autodiscover and the Free/Busy tests from ExRCA (Office 365 tab) here: https://testconnectivity.microsoft.com/
0
 
LVL 1

Author Comment

by:mbudman
ID: 40618585
All the mailboxes are on office 365.

I ran the free / busy tests and this is the error I received (all other tests passed):

      Determining where the source mailbox is hosted based on the Availability Service URL (ASURL).
       The check to determine where the source mailbox is hosted failed.
       
      Additional Details
       
No account settings found in the Autodiscover response.
HTTP Response Headers:
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 1211
Content-Type: application/xml; charset="UTF-8"
Date: Thu, 19 Feb 2015 11:53:56 GMT
Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Elapsed Time: 1642 ms.
0
 
LVL 38

Assisted Solution

by:Vasil Michev (MVP)
Vasil Michev (MVP) earned 500 total points
ID: 40618597
That's definitely not a response from Microsoft servers, so it seems you are hitting a different autodiscover endpoint that does not link to EO. Can you post the full sanitized report from ExRCA, or provide the domain name?
0
 
LVL 1

Author Comment

by:mbudman
ID: 40619266
Would you say that this is something caused by Microsoft or something caused by some organizational setting / configuration?

================

Here you go:

Performing Free/Busy Test. See guidance about the Hybrid Configuration Wizard at http://aka.ms/HCW Free/Busy test failed
 
Additional Details
       Elapsed Time: 3037 ms.
 
 
Test Steps
        
Determining where the source mailbox is hosted based on the Availability Service URL (ASURL).
       The check to determine where the source mailbox is hosted failed.
        
Additional Details
       No account settings found in the Autodiscover response.
HTTP Response Headers:
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Length: 1211
Content-Type: application/xml; charset="UTF-8"
Date: Thu, 19 Feb 2015 12:30:31 GMT
Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Elapsed Time: 1874 ms.

        
Test Steps
        
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for <<user_account>>@<<domain>>.com.

       Autodiscover was tested successfully.
        
Additional Details
       Elapsed Time: 1861 ms.

        
Test Steps
        
Attempting each method of contacting the Autodiscover service.
       The Autodiscover service was tested successfully.
        
Additional Details
       Elapsed Time: 1861 ms.

        
Test Steps
        
Attempting to test potential Autodiscover URL https://<<domain>>.com:443/Autodiscover/Autodiscover.xml

       Testing of the Autodiscover URL was successful.
        
Additional Details
       Elapsed Time: 1860 ms.

        
Test Steps
        
Attempting to resolve the host name <<domain>>.com in DNS.
       The host name resolved successfully.
        
Additional Details
       IP addresses returned: xxx.xxx.xxx.xxx
Elapsed Time: 45 ms.

 
Testing TCP port 443 on host <<domain>>.com to ensure it's listening and open.
       The port was opened successfully.
        
Additional Details
       Elapsed Time: 100 ms.

 
Testing the SSL certificate to make sure it's valid.
       The certificate passed all validation requirements.
        
Additional Details
       Elapsed Time: 365 ms.

        
Test Steps
        
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server <<domain>>.com on port 443.
       The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
        
Additional Details
       Remote Certificate Subject: CN=<<domain>>.com, O=<<Company name>>., <address>>, C=CA, OID.9.9.9.9.9.9.999.99.9.9.9=<<location>>, OID.1.3.6.1.4.1.311.60.2.1.3=CA, SERIALNUMBER=9999999 OID.9.9.9.99=Private Organization, Issuer: CN=GlobalSign Extended Validation CA - SHA256 - G2, O=GlobalSign nv-sa, C=BE.
Elapsed Time: 310 ms.

 
Validating the certificate name.
       The certificate name was validated successfully.
        
Additional Details
       Host name <<domain>>.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.

 
Certificate trust is being validated.
       The certificate is trusted and all certificates are present in the chain.
        
Test Steps
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 38

Assisted Solution

by:Vasil Michev (MVP)
Vasil Michev (MVP) earned 500 total points
ID: 40619623
The first lookup, "HTTPS Root domain" succeeds. This means that somewhere in your organization there is a web server listening on https://<<domain>>.com:443 and replying to the request. While you can use GPO to instruct Outlook to not look there, you obviously cannot control this for external users. So the best solution in your case is to locate that server and remove the binding.
0
 
LVL 1

Author Comment

by:mbudman
ID: 40619637
Here is the report from Microsoft (the customer hosts their website at an external location on a Linux box):

We have identified the root cause is due to a recent update to Linux based web servers (that host root domain of customers). Technically webservers should not be responding to Autodiscover traffic but the recent update has turned on some email capabilities on these servers with Web Hosting provider and that is causing some serious problems

Do you know how to disable responding to Autodiscover?

Thanks.
0
 
LVL 38

Expert Comment

by:Vasil Michev (MVP)
ID: 40619774
No, sorry, not a Linux guy.

Check here for example: http://community.office365.com/en-us/f/156/t/293985.aspx
0
 
LVL 1

Author Closing Comment

by:mbudman
ID: 40628502
Thank you for your assistance
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Find out what Office 365 Transport Rules are, how they work and their limitations managing Office 365 signatures.
This article explains how to prepare an HTML email signature template file containing dynamic placeholders for users' Azure AD data. Furthermore, it explains how to use this file to remotely set up a department-wide email signature policy in Office …
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now