locked
Skype for Business on Premises login issue RRS feed

  • Question

  • I have installed skype for business server in internal network, but i am unable to login from the same domain. i have checked everything. DNS records are fine, users are enabled and when i captured the packets using wireshark, the strange thing is my client is sending FIN packet after successful TLS handshake with the server. If someone knows the solution kindly reply.
    Thursday, November 16, 2017 9:06 PM

Answers

  • Hi zeeshan813,

    1. If you set your account in another computer, does the issue persist?

    2. Do other users in your organization have the same problem?

    When you cannot sign in the skype for business,did you get some error message?Please give me some screenshot about these error message.

    If client could connect to skype for business server ,DNS is OK,secure TLS connection could establish successfully,you should check the following things

    1.Client should trust the Certificate issued on the Server (Client should contain the Root/Intermediate Certs)

    2.FQDN/ URL that we are trying to access should be part of Certificate SAN entry on the Server where we are connecting to.

    3.Required TLS Protocol & TLS cipher suites should be allowed in Firewall (If any)

    You could refer to the following link.

    https://blogs.technet.microsoft.com/praj/2016/10/14/troubleshooting-skype-for-business-client-sign-in-issues/


    Regards,

    Leon Lu


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

    • Marked as answer by zeeshan813 Saturday, November 25, 2017 1:00 PM
    Friday, November 17, 2017 2:01 AM

All replies

  • Hi zeeshan813,

    1. If you set your account in another computer, does the issue persist?

    2. Do other users in your organization have the same problem?

    When you cannot sign in the skype for business,did you get some error message?Please give me some screenshot about these error message.

    If client could connect to skype for business server ,DNS is OK,secure TLS connection could establish successfully,you should check the following things

    1.Client should trust the Certificate issued on the Server (Client should contain the Root/Intermediate Certs)

    2.FQDN/ URL that we are trying to access should be part of Certificate SAN entry on the Server where we are connecting to.

    3.Required TLS Protocol & TLS cipher suites should be allowed in Firewall (If any)

    You could refer to the following link.

    https://blogs.technet.microsoft.com/praj/2016/10/14/troubleshooting-skype-for-business-client-sign-in-issues/


    Regards,

    Leon Lu


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

    • Marked as answer by zeeshan813 Saturday, November 25, 2017 1:00 PM
    Friday, November 17, 2017 2:01 AM
  • Hi Leon Lu,

    1. Yes, the problem remains same on any computer in the domain

    2. Yes, the issue is with every user

    3. I have added the certificate in clients trusted root certificate list

    4. FQDN is part of the Certificates's SAN

    Error Message : “Can’t sign in to Skype for Business. The server is temporarily unavailable. If the problem continues, please contact your support team.”

    Error logs:

    1 Login: FAIL (hr = 0x80ee001c) 

       VerifyOnEnableEvent result return ONENABLE_FAIL_SERVER_NOT_REACHABLE
       status=0x80ee001c
        ACTION: SERVER NOT REACHABLE
        NO MORE SERVER TO TRY
        ACTION : PERMANENT ERROR
    1.1 Lync-autodiscovery: PASS
    1.1.1 Get-NewWebTicket: PASS
    1.1.1.1 ExecuteWithWindowsOrNoAuthInternal: FAIL (hr = 0x3d0000) 
    Executing wws method with no auth auth, asyncContext=0DAA6570,
     context: WebRequest context@ :493721544
      MethodType:0
      ExecutionComplete? :1
      Callback@ :1D725BB8
      AsyncHResult:3d0000
      TargetUri:https://sfbfe01.contoso.com/WebTicket/WebTicketService.svc/mex

    ...................................................................

    1.1.1.8 ExecuteWithWindowsOrNoAuthInternal: PASS


    Saturday, November 18, 2017 2:19 PM
  • actually i am facing the same issue, may i know how did you resove it?
    Tuesday, April 24, 2018 5:11 AM