locked
Skype4B Mac - (sudden) Certificate Issue RRS feed

  • Question

  • Hi!

    Our clients informed us, that they cannot connect the S4B Mac clients from outside the network any more - starting
    a few days ago.

    No matter what if they use Mohave or High Sierra and we tried an older Skype4B client without any success.
    The error is a certificate problem although the certificate is active for a month now (and valid until end of january)

    We run our skype-edge server (2016) with the latest CU for 3 weeks without any updates or restart.
    The windows clients and mobile clients connecting without any problems.

    Any ideas?

    lg

    Martin

    Friday, November 30, 2018 1:21 PM

Answers

  • We found the solution today - was not that simple ;)

    The mac client is, contrary to the windows client, contacting one of the addresses that
    is handled over the proxy server (like lyncdiscover or meet).
    The windows client contacts the sip. directly - or at least it seems like that.

    And ... the proxy had an invalid certificate ...

    Friday, December 7, 2018 9:47 AM

All replies

  • And is the certificate really valid and trusted (and all of the chain) to end user workstation? Like Symantec legacy certs which are currently blocked already by some.
    Friday, November 30, 2018 1:42 PM
  • Thanks for the response.

    The certificate is an Let's Encrypt and perfectly valid for

    The testconnectivity site from microsoft
    The ssl-lab test
    All windows clients

    Safari on the same Mac's loads the edge server url (https://sip....) without any complaints.

    I read the same warning for the legacy certs, but if i interprete that correctly, this affects only Mohave and we have High Sierra and Sierra Mac's with the same issue ...

    I updated the edge server today with the latest november update from windows (just to get sure) ... no effect

    Friday, November 30, 2018 1:48 PM
  • Hi Martin,

    Based on your description, the logon issue only affects High Sierra Macs, what if the Mac users log on with other Mac books, does it work?

    Also, please also try with Skype for Business Basic verison to have a test.

    I suggest that you could update to the latest verision of of SFB Mac client.

    If it works fine with the above methods, then it might be caused by a client side issue.

    In addition, please clean the SFB cache on MAC and refer to the following ways:

    Skype for Business 2016 for MAC

    • Log out and quit Skype for Business.
    • Go to Finder > press Command+Shift+G > type in /users/<MacUsername>/library > delete the following files:
    • Containters > com.microsoft.SkypeForBusiness
    • Internet Plug-Ins > MeetingJoinPlugin.plugin
    • Logs > LwaTracing
    • Saved Application State > com.microsoft.SkypeForBusiness.savedState
    • Preferences > com.microsoft.skypeforbusiness.plugin.plist
      • Open Keychain Access from /Applications/Utilities folder.
      • Delete all keychains starting with Skype For Business.

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. 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.

    Monday, December 3, 2018 8:11 AM
  • Hi!

    Thank you for your response.

    It affects ALL Macs from Sierra->Mohave and all of our users.
    We are using the latest Version of Skype 4B Mac

    It does not affect any Windows Clients with Skype for business.

    We tried your steps with High Sierra and Mohave clients, without success.

    Tuesday, December 4, 2018 9:42 AM
  • Hi,

    Though it is a certificate error message, I think it may be related something other, it may be an idea to check the MAC client logs to see if there is any related information.

    Here is a reference.

    https://www.itprotoday.com/microsoft-exchange/mac-skype-business-2015-client-side-logs
    Friday, December 7, 2018 9:44 AM
  • We found the solution today - was not that simple ;)

    The mac client is, contrary to the windows client, contacting one of the addresses that
    is handled over the proxy server (like lyncdiscover or meet).
    The windows client contacts the sip. directly - or at least it seems like that.

    And ... the proxy had an invalid certificate ...

    Friday, December 7, 2018 9:47 AM
  • Sounds great, thanks for sharing, Martin!

    Kind regards,

    Calvin Liu


    Please remember to mark the reply as an answer if you find it is helpful. It will assist others who has similar issue. 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.

    Friday, December 7, 2018 12:38 PM