none
Autodiscover not working in some of the Windows Vista machines RRS feed

  • 問題

  •  

    Hi all

     

    We have setup autodiscover as well as configured our DNS server to

    serve the SRV record _autodiscover._tcp.xxx.com and pointing to

    the CAS server cas.xxx.com

     

    On some Windows Vista machine, autodiscover works perfectly fine,

    but on some, even with Outlook 2007 SP1, autodiscover failed.

     

    Using the Outlook 2007 autodiscover tester, it shows that

    it can successfully look up the SRV record to cas.xxx.com,

    then, it said that SRV record lookup failed. I am a bit puzzled

    as the test log shows that it is trying to access cas.xxx.com,

    which means that SRV record lookuop should be successful.

    Then, it said that SRV record lookup failed.

     

    We tried on both domain joined or non-domain joined machines

    and found that it is not really related. We have no idea why

    autodiscover works on some systems but some do not.

    2008年12月11日 上午 11:27

解答

  • Dear customer:

     

    An Outlook 2007 client connects to the Autodiscover service as follows:

     

    1.      Outlook 2007 sends a Lightweight Directory Access Protocol (LDAP) query to Active Directory looking for all available SCP objects.

     

    2.      Outlook 2007 sorts and enumerates the returned results based on the client's Active Directory site by using the keyword attribute of the SCP record. One of two lists is created, an in-site list or an out-of-site list. The in-site list provides the SCP records that have AutodiscoverSiteScope information. AutodiscoverSiteScope is a parameter that is set on the Client Access server by using the Set-ClientAccessServer cmdlet. The parameter specifies the site for which the Autodiscover service is authoritative. The AutodiscoverSiteScope information contained in the SCP records for the in-site list matches the Active Directory site for the Outlook client. If there are no in-site records, an out-of-site SCP record list will be generated. The list is not sorted in any particular order. Therefore, the list is approximately in the order of oldest SCP records (based on creation date) first.

     

    3.      Outlook first tries to connect to each Autodiscover URL that it had previously generated from either an in-site list or an out-of-site list. If that doesn't work, Outlook will try to connect to the predefined URLs (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.xml) by using DNS. If that fails also, Outlook will try the HTTP redirect method and, failing that, Outlook will try to use the SRV record lookup method. If all lookup methods fail, Outlook will be unable to obtain Outlook Anywhere configuration and URL settings.

     

    4.      The Autodiscover service queries Active Directory to obtain the connection settings and URLs for the Exchange services that have been configured.

     

    5.      The Autodiscover service returns an HTTPS response with an XML file that includes the connection settings and URLs for the available Exchange services.

     

    6.      Outlook uses the appropriate configuration information and connection settings to connect to your Exchange messaging environment

     

    Please try the following suggestion:

     

    1. On your client, check whether you can ping autodiscover.domain.com, if not, please contact DNS provider to add autodiscover.domain.com record and check the effect.
    2. Did you add the SRV on the public DNS provider or not?
    3. Try to fix the issue via the following article and check the effect.

     

    A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service

    http://support.microsoft.com/kb/940881/en-us

     

    For more information about Exchange 2007 Autodiscover Service, please refer to the following article:

    White Paper: Exchange 2007 Autodiscover Service

    http://technet.microsoft.com/en-us/library/bb332063.aspx

     

    Hope it helps.

     

    Rock Wang - MSFT

     

    2008年12月17日 下午 12:01
    版主

所有回覆

  •  

    Dear customer:

     

    Please help collect the following information:

     

    1.       Open Outlook 2007, press Ctrl key and at the same time right click Outlook icon on the Task Bar, select Test E-mail AutoConfiguration option, when the Test E-mail AutoConfiguration dialog box is displayed, your e-mail address is automatically populated.

     

    Note: If you are logged into the domain, the E-mail address field is populated by using the account you’re logged onto the machine with. If you have multiple profiles configured and you’re using one that isn’t your own, you will need to change the e-mail address in this field and enter a password.

     

    2.       To test Autodiscover ensure ONLY the Use Autodiscover option is selected. A password does not have to be entered when you are logged into the domain. Your logged in credentials are used. Finally, click on the AutoConfigure button to start the Autodiscover request to the Autodiscover service.

    3.       After Outlook sends your E-mail Address and credentials to the Autodiscover service the various Results, Log, and XML tabs will show status and results of Autodiscover request.

    4.       Click Results tab, send the screenshot of it to v-rocwan@microsoft.com for analyze.

    5.       Click log tab, send the screenshot of it to me for analyze.

    6.       Click XML tab, send the screenshot of it to me for analyze.

    7.       On the problematic client, open command prompt, run the following command and post the result into the forum:

     

    ipconfig /all

     

    Note: when you send e-mail to me, please let me know the subject of the post.

     

    Thanks for your cooperation.

     

    Rock Wang - MSFT

    2008年12月12日 上午 02:18
    版主
  •  

    Dear customer:

     

    Please check whether you set proxy server in Internet Explorer on the problematic client, if so, change to automatically detect settings instead of bypass proxy settings. And then check the effect.

     

    Hope it helps.

     

    Rock Wang - MSFT

    2008年12月15日 上午 08:38
    版主
  •  

    Sorry for the late reply.

     

    We have no proxy in our environment. All our clients use real IP and access the Internet directly.

    I'll send you the log tomorrow.

     

    Thanks for spending time on my case.

     

     

     

     

     

     

     

    2008年12月16日 上午 11:14
  •  

    Hi Rock

     

    I have sent you the result via email with the subject "Autodiscover failure".

     

    Thanks.

     

     

    2008年12月17日 上午 04:27
  • Dear customer:

     

    An Outlook 2007 client connects to the Autodiscover service as follows:

     

    1.      Outlook 2007 sends a Lightweight Directory Access Protocol (LDAP) query to Active Directory looking for all available SCP objects.

     

    2.      Outlook 2007 sorts and enumerates the returned results based on the client's Active Directory site by using the keyword attribute of the SCP record. One of two lists is created, an in-site list or an out-of-site list. The in-site list provides the SCP records that have AutodiscoverSiteScope information. AutodiscoverSiteScope is a parameter that is set on the Client Access server by using the Set-ClientAccessServer cmdlet. The parameter specifies the site for which the Autodiscover service is authoritative. The AutodiscoverSiteScope information contained in the SCP records for the in-site list matches the Active Directory site for the Outlook client. If there are no in-site records, an out-of-site SCP record list will be generated. The list is not sorted in any particular order. Therefore, the list is approximately in the order of oldest SCP records (based on creation date) first.

     

    3.      Outlook first tries to connect to each Autodiscover URL that it had previously generated from either an in-site list or an out-of-site list. If that doesn't work, Outlook will try to connect to the predefined URLs (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.xml) by using DNS. If that fails also, Outlook will try the HTTP redirect method and, failing that, Outlook will try to use the SRV record lookup method. If all lookup methods fail, Outlook will be unable to obtain Outlook Anywhere configuration and URL settings.

     

    4.      The Autodiscover service queries Active Directory to obtain the connection settings and URLs for the Exchange services that have been configured.

     

    5.      The Autodiscover service returns an HTTPS response with an XML file that includes the connection settings and URLs for the available Exchange services.

     

    6.      Outlook uses the appropriate configuration information and connection settings to connect to your Exchange messaging environment

     

    Please try the following suggestion:

     

    1. On your client, check whether you can ping autodiscover.domain.com, if not, please contact DNS provider to add autodiscover.domain.com record and check the effect.
    2. Did you add the SRV on the public DNS provider or not?
    3. Try to fix the issue via the following article and check the effect.

     

    A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service

    http://support.microsoft.com/kb/940881/en-us

     

    For more information about Exchange 2007 Autodiscover Service, please refer to the following article:

    White Paper: Exchange 2007 Autodiscover Service

    http://technet.microsoft.com/en-us/library/bb332063.aspx

     

    Hope it helps.

     

    Rock Wang - MSFT

     

    2008年12月17日 下午 12:01
    版主
  • We have already configured the autodiscover SRV record

    in our own DNS server and autoconfiguration does work, but

    only on some of the machines.

     

    At first, I thought that it is related to domains as our Exchange

    organization is installed in another domain and there is

    no trust relationship between the Exchange domain and the domain

    which our PC has joined. However, further testing shows that this

    is not related.

     

    We do not know under what circumstances that autoconfiguration

    work and under what condition that autoconfiguration will failed.

     

     

    2008年12月19日 上午 10:19