locked
iOS cannot verity Server Identity with connecting to Exchange RRS feed

 > 

  • Pergunta

  • Question
    Entrar para Votar
    0
    Entrar para Votar

    Hi all,

    Trying to figure out why when any iOS device tries to connect our Exchange 2010 server that a certificate warning pops up stating "cannot verify server identity". When selecting details is comes up with a cert name that is not in our organization. If you click continue it proceeds with connection to the Exchange account.

    For obvious reasons we are concerned about where this cert is residing and how it got there. But I haven't been able to pinpoint where it could be. Our Exchange does have a valid SSL cert.

    Note: We do not use Activsync autodiscover.


    bl

    terça-feira, 29 de maio de 2018 18:29

Respostas

  • Question
    Entrar para Votar
    0
    Entrar para Votar

    your device will still try to do autodicover, it is more than likely getting the certificate from your public website/hoster on this URL https://www.yourdomain.com/autodiscover

    if you run the autodiscover test for active sync from the Exchange Remote Connectivity analyser you will see the steps and certificates found.

    https://testconnectivity.microsoft.com/

    **Please don't forget to mark as helpful or answer**

    • Sugerido como Resposta Allen_WangJF quarta-feira, 30 de maio de 2018 07:44
    • Marcado como Resposta berlan sexta-feira, 1 de junho de 2018 14:35
    terça-feira, 29 de maio de 2018 19:04

Todas as Respostas

  • Question
    Entrar para Votar
    0
    Entrar para Votar

    your device will still try to do autodicover, it is more than likely getting the certificate from your public website/hoster on this URL https://www.yourdomain.com/autodiscover

    if you run the autodiscover test for active sync from the Exchange Remote Connectivity analyser you will see the steps and certificates found.

    https://testconnectivity.microsoft.com/

    **Please don't forget to mark as helpful or answer**

    • Sugerido como Resposta Allen_WangJF quarta-feira, 30 de maio de 2018 07:44
    • Marcado como Resposta berlan sexta-feira, 1 de junho de 2018 14:35
    terça-feira, 29 de maio de 2018 19:04
  • Question
    Entrar para Votar
    0
    Entrar para Votar
    Hi,

    Any further concern about your question?
    If the above suggestion helps, please be free to mark it as answer. Thanks for your cooperation.

    Best Regards,
    Allen Wang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marcado como Resposta berlan sexta-feira, 1 de junho de 2018 14:31
    • Não Marcado como Resposta berlan sexta-feira, 1 de junho de 2018 14:32
    sexta-feira, 1 de junho de 2018 01:38
  • Question
    Entrar para Votar
    0
    Entrar para Votar

    Thanks for the leading me down the right path. I was able to determine that the unknown certificate was coming from that of a company that is using the same A record for our website! This leads me to think that our web host provider is using the same IP for all of their clients they are hosting.

    Regardless we are in the process of changing web host providers anyway, so hopefully we won't be duplicating this issue with another company such as with this one.

    bl

    sexta-feira, 1 de junho de 2018 14:35
  • Question
    Entrar para Votar
    0
    Entrar para Votar
    Thanks for your update and sharing.

    Best Regards,
    Allen Wang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    segunda-feira, 4 de junho de 2018 02:26
  • Question
    Entrar para Votar
    0
    Entrar para Votar
    Hello my clients suddenly started getting this error, nothing was changed, I think its updates for iPhone because I tried to connect old iPad with older version and it's not giving any errors. Any tips?
    sexta-feira, 14 de agosto de 2020 02:13