none
У некоторых клиентов телефон не подключается к ActiveSync

    Вопрос

  • Добрый день, в организации используется Exchange 2013. После обновления сертификата некоторые клиенты, не могут подключиться к Exchange через мобильные приложения. В чём может быть проблема? Телефоны не находятся в карантине, доступ разрешён.
    29 января 2018 г. 13:11

Ответы

  • Да, все верно. Меняли что-то или нет, сейчас у вас не работает Autodiscover. Причина - некорректно настроено перенаправление. Как вариант, можете просто его отключить для теста. После убедитесь, что https://autodiscover.contoso.com/Autodiscover/Autodiscover.xml не редиректит на OWA. Далее прогоните тест снова. 

    По настройке и ремонту автообнаружения материалов навалом, если что :)

    30 января 2018 г. 8:47

Все ответы

  • А как выглядит это "Не могут подключиться"? Ругаются на что-то, или молча не синхронизмруются?
    29 января 2018 г. 13:21
  • На айфоне пишет "Сбой доставки почты" c Outlook на андроид "превышен интервал времени ответа" 

    PS: По логам IIS подключение происходит

    • Изменено badcat177 29 января 2018 г. 13:24
    29 января 2018 г. 13:24
  • Какой сертификат вы используете? Выданный доменным СА или публичным (покупной, проще говоря)? Какие имена в нем есть?

    Попробуйте выполнить рестарт пула ActiveSync. 

    30 января 2018 г. 6:53
  • Да, еще проверьте подключение ActiveSync тут:

    https://testconnectivity.microsoft.com/

    Если не поймете, что произошло, покажите эти логи нам.


    30 января 2018 г. 6:55
  • купленный сертификат
    30 января 2018 г. 7:40


  • The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
      The Exchange ActiveSync test failed.
      Additional Details
      Elapsed Time: 21097 ms.

      Test Steps
      Attempting the Autodiscover and Exchange ActiveSync test (if requested).
      Testing of Autodiscover for Exchange ActiveSync failed.
      Additional Details
      Elapsed Time: 21097 ms.

      Test Steps
      Attempting each method of contacting the Autodiscover service.
      The Autodiscover service couldn't be contacted successfully by any method.
      Additional Details
      Elapsed Time: 21097 ms.

      Test Steps
      Attempting to test potential Autodiscover URL https://xxxxx.ru:443/Autodiscover/Autodiscover.xml
      Testing of this potential Autodiscover URL failed.
      Additional Details
      Elapsed Time: 8973 ms.

      Test Steps
      Attempting to resolve the host name xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: 89.108.91.9
    Elapsed Time: 1917 ms.

    Testing TCP port 443 on host xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 1357 ms.

    Testing the SSL certificate to make sure it's valid.
      The SSL certificate failed one or more certificate validation checks.
      Additional Details
      Elapsed Time: 5699 ms.

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server xxxxx.ru on port 443.
      The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
      Additional Details
      The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
    Elapsed Time: 5669 ms.





    Attempting to test potential Autodiscover URL https://autodiscover.xxxxx.ru:443/Autodiscover/Autodiscover.xml
      Testing of this potential Autodiscover URL failed.
      Additional Details
      Elapsed Time: 8082 ms.

      Test Steps
      Attempting to resolve the host name autodiscover.xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: xx.xxx.115.91
    Elapsed Time: 1419 ms.

    Testing TCP port 443 on host autodiscover.xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 357 ms.

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

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xxxxx.ru on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
      Additional Details
      Remote Certificate Subject: CN=autodiscover.xxxxx.ru, Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US.
    Elapsed Time: 484 ms.

    Validating the certificate name.
      The certificate name was validated successfully.
      Additional Details
      Host name autodiscover.xxxxx.ru 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
      The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=autodiscover.xxxxx.ru.
      One or more certificate chains were constructed successfully.
      Additional Details
      A total of 1 chains were built. The highest quality chain ends in root certificate CN=DST Root CA X3, O=Digital Signature Trust Co..
    Elapsed Time: 18 ms.

    Analyzing the certificate chains for compatibility problems with versions of Windows.
      Potential compatibility problems were identified with some versions of Windows.
      Additional Details
      The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 1 ms.



    Testing the certificate date to confirm the certificate is valid.
      Date validation passed. The certificate hasn't expired.
      Additional Details
      The certificate is valid. NotBefore = 1/25/2018 9:47:19 AM, NotAfter = 4/25/2018 9:47:19 AM
    Elapsed Time: 0 ms.



    Checking the IIS configuration for client certificate authentication.
      Client certificate authentication wasn't detected.
      Additional Details
      Accept/Require Client Certificates isn't configured.
    Elapsed Time: 1579 ms.

    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
      Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
      Additional Details
      Elapsed Time: 4190 ms.

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xxxxx.ru:443/Autodiscover/Autodiscover.xml for user xxxxx@xxxxx.ru.
      The Autodiscover XML response was successfully retrieved.
      Additional Details
      An HTTPS redirect was received in response to the Autodiscover request. The redirect URL is https://mail.xxxxx.ru/owa.
    HTTP Response Headers:
    Connection: keep-alive
    Content-Length: 185
    Content-Type: text/html
    Date: Tue, 30 Jan 2018 07:38:55 GMT
    Location: https://mail.xxxxx.ru/owa
    Server: nginx/1.12.2
    Elapsed Time: 629 ms.

    Attempting to test potential Autodiscover URL https://mail.xxxxx.ru/owa
      Testing of this potential Autodiscover URL failed.
      Additional Details
      Elapsed Time: 3560 ms.

      Test Steps
      Attempting to resolve the host name mail.xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: xx.xxx.115.91
    Elapsed Time: 2057 ms.

    Testing TCP port 443 on host mail.xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 166 ms.

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

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.xxxxx.ru on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
      Additional Details
      Remote Certificate Subject: CN=mail.xxxxx.ru, OU=PositiveSSL, OU=Domain Control Validated, Issuer: CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    Elapsed Time: 484 ms.

    Validating the certificate name.
      The certificate name was validated successfully.
      Additional Details
      Host name mail.xxxxx.ru 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
      The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.xxxxx.ru, OU=PositiveSSL, OU=Domain Control Validated.
      One or more certificate chains were constructed successfully.
      Additional Details
      A total of 2 chains were built. The highest quality chain ends in root certificate CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    Elapsed Time: 18 ms.

    Analyzing the certificate chains for compatibility problems with versions of Windows.
      Potential compatibility problems were identified with some versions of Windows.
      Additional Details
      The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 1 ms.



    Testing the certificate date to confirm the certificate is valid.
      Date validation passed. The certificate hasn't expired.
      Additional Details
      The certificate is valid. NotBefore = 12/26/2017 12:00:00 AM, NotAfter = 12/26/2018 11:59:59 PM
    Elapsed Time: 0 ms.



    Checking the IIS configuration for client certificate authentication.
      Client certificate authentication wasn't detected.
      Additional Details
      Accept/Require Client Certificates isn't configured.
    Elapsed Time: 168 ms.

    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
      Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
      Additional Details
      Elapsed Time: 632 ms.

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mail.xxxxx.ru/owa for user xxxxx@xxxxx.ru.
      The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
      Additional Details
      A Web exception occurred because an HTTP 440 - 440 response was received from Unknown.
    HTTP Response Headers:
    Connection: keep-alive
    request-id: 695d6a38-ca60-4ef6-8ab0-955d114d4d0b
    X-FEServer: EXCH-SRV-7
    Content-Length: 154
    Content-Type: text/html; charset=utf-8
    Date: Tue, 30 Jan 2018 07:38:58 GMT
    Set-Cookie: ClientId=CZZNHKZKCEXOFRDLTA; expires=Wed, 30-Jan-2019 07:38:59 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.5
    X-Powered-By: ASP.NET
    Elapsed Time: 631 ms.









    Attempting to contact the Autodiscover service using the HTTP redirect method.
      The attempt to contact Autodiscover using the HTTP Redirect method failed.
      Additional Details
      Elapsed Time: 2552 ms.

      Test Steps
      Attempting to resolve the host name autodiscover.xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: xx.xxx.115.91
    Elapsed Time: 4 ms.

    Testing TCP port 80 on host autodiscover.xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 168 ms.

    The Microsoft Connectivity Analyzer is checking the host autodiscover.xxxxx.ru for an HTTP redirect to the Autodiscover service.
      The redirect (HTTP 301/302) response was received successfully.
      Additional Details
      Redirect URL: https://autodiscover.xxxxx.ru/Autodiscover/Autodiscover.xml
    HTTP Response Headers:
    Connection: keep-alive
    Content-Length: 185
    Content-Type: text/html
    Date: Tue, 30 Jan 2018 07:38:59 GMT
    Location: https://autodiscover.xxxxx.ru/Autodiscover/Autodiscover.xml
    Server: nginx/1.12.2
    Elapsed Time: 314 ms.

    Attempting to test potential Autodiscover URL https://autodiscover.xxxxx.ru/Autodiscover/Autodiscover.xml
      Testing of this potential Autodiscover URL failed.
      Additional Details
      Elapsed Time: 2065 ms.

      Test Steps
      Attempting to resolve the host name autodiscover.xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: xx.xxx.115.91
    Elapsed Time: 33 ms.

    Testing TCP port 443 on host autodiscover.xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 174 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 autodiscover.xxxxx.ru on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
      Additional Details
      Remote Certificate Subject: CN=autodiscover.xxxxx.ru, Issuer: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US.
    Elapsed Time: 322 ms.

    Validating the certificate name.
      The certificate name was validated successfully.
      Additional Details
      Host name autodiscover.xxxxx.ru 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
      The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=autodiscover.xxxxx.ru.
      One or more certificate chains were constructed successfully.
      Additional Details
      A total of 1 chains were built. The highest quality chain ends in root certificate CN=DST Root CA X3, O=Digital Signature Trust Co..
    Elapsed Time: 11 ms.

    Analyzing the certificate chains for compatibility problems with versions of Windows.
      Potential compatibility problems were identified with some versions of Windows.
      Additional Details
      The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 7 ms.



    Testing the certificate date to confirm the certificate is valid.
      Date validation passed. The certificate hasn't expired.
      Additional Details
      The certificate is valid. NotBefore = 1/25/2018 9:47:19 AM, NotAfter = 4/25/2018 9:47:19 AM
    Elapsed Time: 0 ms.



    Checking the IIS configuration for client certificate authentication.
      Client certificate authentication wasn't detected.
      Additional Details
      Accept/Require Client Certificates isn't configured.
    Elapsed Time: 317 ms.

    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
      Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
      Additional Details
      Elapsed Time: 1175 ms.

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xxxxx.ru/Autodiscover/Autodiscover.xml for user xxxxx@xxxxx.ru.
      The Autodiscover XML response was successfully retrieved.
      Additional Details
      An HTTPS redirect was received in response to the Autodiscover request. The redirect URL is https://mail.xxxxx.ru/owa.
    HTTP Response Headers:
    Connection: keep-alive
    Content-Length: 185
    Content-Type: text/html
    Date: Tue, 30 Jan 2018 07:39:00 GMT
    Location: https://mail.xxxxx.ru/owa
    Server: nginx/1.12.2
    Elapsed Time: 157 ms.

    Attempting to test potential Autodiscover URL https://mail.xxxxx.ru/owa
      Testing of this potential Autodiscover URL failed.
      Additional Details
      Elapsed Time: 1017 ms.

      Test Steps
      Attempting to resolve the host name mail.xxxxx.ru in DNS.
      The host name resolved successfully.
      Additional Details
      IP addresses returned: xx.xxx.115.91
    Elapsed Time: 10 ms.

    Testing TCP port 443 on host mail.xxxxx.ru to ensure it's listening and open.
      The port was opened successfully.
      Additional Details
      Elapsed Time: 169 ms.

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

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.xxxxx.ru on port 443.
      The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
      Additional Details
      Remote Certificate Subject: CN=mail.xxxxx.ru, OU=PositiveSSL, OU=Domain Control Validated, Issuer: CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    Elapsed Time: 316 ms.

    Validating the certificate name.
      The certificate name was validated successfully.
      Additional Details
      Host name mail.xxxxx.ru 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
      The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.xxxxx.ru, OU=PositiveSSL, OU=Domain Control Validated.
      One or more certificate chains were constructed successfully.
      Additional Details
      A total of 2 chains were built. The highest quality chain ends in root certificate CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
    Elapsed Time: 13 ms.

    Analyzing the certificate chains for compatibility problems with versions of Windows.
      Potential compatibility problems were identified with some versions of Windows.
      Additional Details
      The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
    Elapsed Time: 2 ms.



    Testing the certificate date to confirm the certificate is valid.
      Date validation passed. The certificate hasn't expired.
      Additional Details
      The certificate is valid. NotBefore = 12/26/2017 12:00:00 AM, NotAfter = 12/26/2018 11:59:59 PM
    Elapsed Time: 0 ms.



    Checking the IIS configuration for client certificate authentication.
      Client certificate authentication wasn't detected.
      Additional Details
      Accept/Require Client Certificates isn't configured.
    Elapsed Time: 160 ms.

    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
      Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
      Additional Details
      Elapsed Time: 321 ms.

      Test Steps
      The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mail.xxxxx.ru/owa for user xxxxx@xxxxx.ru.
      The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
      Additional Details
      A Web exception occurred because an HTTP 440 - 440 response was received from Unknown.
    HTTP Response Headers:
    Connection: keep-alive
    request-id: aaefff17-447d-4486-a905-6f234d2e2a76
    X-FEServer: EXCH-SRV-7
    Content-Length: 154
    Content-Type: text/html; charset=utf-8
    Date: Tue, 30 Jan 2018 07:39:01 GMT
    Set-Cookie: ClientId=UPLTANFKKWIJ9ZTSG; expires=Wed, 30-Jan-2019 07:39:01 GMT; path=/; HttpOnly
    Server: Microsoft-IIS/8.5
    X-Powered-By: ASP.NET
    Elapsed Time: 321 ms.











    Attempting to contact the Autodiscover service using the DNS SRV redirect method.
      The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
      Additional Details
      Elapsed Time: 1191 ms.

      Test Steps
      Attempting to locate SRV record _autodiscover._tcp.xxxxx.ru in DNS.
      The Autodiscover SRV record wasn't found in DNS.
      Tell me more about this issue and how to resolve it

      Additional Details
      Elapsed Time: 1191 ms.



    Checking if there is an autodiscover CNAME record in DNS for your domain 'xxxxx.ru' for Office 365.
      Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
     






    30 января 2018 г. 7:59
  • Вы что-то напутали с редиректами. У вас идет перенаправление с https://autodiscover.contoso.com/Autodiscover/Autodiscover.xml на OWA.
    30 января 2018 г. 8:00
  • Хотя никаких настроек не меняли, предыстория небольшая, у нас кончился сертификат (купленный) мы его проплатили, и после этого отвалились некоторые мобильные клиенты, до этого было всё нормально
    30 января 2018 г. 8:26
  • Если у вас был настроен редирект с httP://contoso.com/owa на httpS://contoso.com/owa, то при установке CU на Exchange или обновлений для IIS могли слететь настройки наследования этого редиректа, проверьте, что по остальным веб-каталогам все в порядке.
    30 января 2018 г. 8:43
  • Да, все верно. Меняли что-то или нет, сейчас у вас не работает Autodiscover. Причина - некорректно настроено перенаправление. Как вариант, можете просто его отключить для теста. После убедитесь, что https://autodiscover.contoso.com/Autodiscover/Autodiscover.xml не редиректит на OWA. Далее прогоните тест снова. 

    По настройке и ремонту автообнаружения материалов навалом, если что :)

    30 января 2018 г. 8:47
  • Attempting to ping the MAPI Mail Store endpoint with identity: 614f5ec9-f01b-41e9-b6b0-13502ea39c93@xxxxxxx.rxx:6001.

      The attempt to ping the endpoint failed.
     
    Additional Details
     
    An RPC error was thrown by the RPC Runtime process. Error 1818 CallCancelled
    Elapsed Time: 32598 ms.

    Пофискили autodiscover, теперь всплыла такая ошибка

    13 февраля 2018 г. 15:57
  • И не стыдно ответы снимать? Показали ведь причину.

    An RPC error was thrown by the RPC Runtime process. Error 1818 CallCancelled

    Outlook anywhere Вообще наружу опубликован? Такое чувство, [CallCancelled] что закрыли.

    13 февраля 2018 г. 17:17
  • Опубликован, щас настроили реверс прокси на iis arr, на внутренем сертификате всё прекрасно завелось, но когда мы выпустили  Let's Encrypt сертификат , перестал настраиваться outlook 2007, упали некоторые клиенты 2010 outlook (постоянно запрашивает логин и пароль).
    15 февраля 2018 г. 14:33
  • упали некоторые клиенты 2010 outlook (постоянно запрашивает логин и пароль).

    Не скромничали бы, а так и написали бы, что древние испихи перестали подключаться.)

    Мы поймем. У всего есть минусы, да. 

    15 февраля 2018 г. 15:00
  • Так про XP молчу, т.к. вкурсе, выскакивает запрос логина и пароля при настройке (win7 и office 2007), при работе в связке (win7 + office 2010, win10 + 2010). 
    15 февраля 2018 г. 15:10
  • А на более высоких не выскакивает? Может апдейты виноваты.

    В любом случае- берем фиддлер и снимаем сессию.

    Ну и новую тему можете создать и сослаться сюда.

    Чтобы не плодить вопросы.

    15 февраля 2018 г. 15:21
  • Опубликован,до этого была публикация на nginx , щас настроили реверс прокси на iis arr (данной ошибки уже нет), на внутренем сертификате всё прекрасно завелось, но когда мы выпустили  Let's Encrypt сертификат , перестал настраиваться outlook 2007, упали некоторые клиенты 2010 outlook (постоянно запрашивает логин и пароль).

    15 февраля 2018 г. 15:22
  • на office 2013 проблем пока нет. 
    15 февраля 2018 г. 15:27