Office 365 - Autodiscovery not working
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)
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)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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>
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/Autodis
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
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
================
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>
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/Autodis
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
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
No, sorry, not a Linux guy.
Check here for example: http://community.office365.com/en-us/f/156/t/293985.aspx
Check here for example: http://community.office365.com/en-us/f/156/t/293985.aspx
ASKER
Thank you for your assistance
ASKER
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.