locked
OWA via chrome and/or firefox, safari RRS feed

  • Question

  • Hello,

    Does anyone have a solution to owa access via chrome, firefox and/or safari.. appears to be security related but not sure what to look for and/or fix... works find in IE and EDGE

    Thursday, February 9, 2017 6:42 PM

Answers

  • actually found that it was a cipher and/or hash issue as indicated from this thread I found....

    I had the exact error with Windows Server 2016 and Exchange 2016 CU3 using a self-signed certificate on a fresh test environment.

    I've resolved it using iiscrypto (https://www.nartac.com/Products/IISCrypto GUI) chose the "Best Practice" option.

    After rebooting, the OWA login form showed up.

    ran app on server and worked fine afterwards

    thanks to your replies.

    Monday, February 13, 2017 10:27 PM

All replies

  • Hi,

    Thanks for contacting our forum.

    Are there any error message when you use OWA via chrome, firefox or safari?  What's the detailed versions of your Exchange server?

    Meanwhile, please refer to below articles:

    What's new when updating from Exchange 2016 RTM to Exchange 2016 CU1? In : https://technet.microsoft.com/en-us/library/jj150540(v=exchg.160).aspx

    The part “Supported browsers” in the article: https://technet.microsoft.com/en-us/library/jj150522(v=exchg.150).aspx

    Thanks for your effort and hope it helps.


    Regards,

    Jason Chao


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

    Friday, February 10, 2017 2:41 AM
  • running ex2016 std CU3 on server 2016 std DC

    error message from chrome is... 

    The webpage at https:// *******.***/owa might be temporarily down or it may have moved permanently to a new web address.

    ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY


    similarly from firefox and safari...

    Friday, February 10, 2017 5:02 PM
  • now i test safari and Chrome on a MAC OS and it works fine. (Server Exchange 2016 CU4)

    It think you should check your certifikate, DNS and URL Names (virtual Directories).


    Chris

    Sunday, February 12, 2017 6:17 PM
  • actually found that it was a cipher and/or hash issue as indicated from this thread I found....

    I had the exact error with Windows Server 2016 and Exchange 2016 CU3 using a self-signed certificate on a fresh test environment.

    I've resolved it using iiscrypto (https://www.nartac.com/Products/IISCrypto GUI) chose the "Best Practice" option.

    After rebooting, the OWA login form showed up.

    ran app on server and worked fine afterwards

    thanks to your replies.

    Monday, February 13, 2017 10:27 PM
  • Thanks for your answer, it's a cipher and/or hash related issue, please make the reply as answer and it'll help others.

    Thanks for your time and effort again.


    Regards,

    Jason Chao


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

    Tuesday, February 14, 2017 2:02 AM