locked
Issues with External Skype for Business clients connecting to Edge server RRS feed

  • Question

  • Good afternoon, I was hoping someone could give me a clue to solve my Skype Edge server implementation issue.  I recently setup a skype 4 business edge server and I'm trying to get a client connected to it.  All the DNS entries seem to resolve and I ran a netstat -n and I can see the client come over port 5061 and with a SYN_RECEIVED.  I've tried to go through the CsCLSLogs and look through the sip stack but I don't see anything related to the connection just internal clients trying to reach other domains that I'm not federated with.  I went and looked through the Skype 4 business client log on the external client and I just get a "ONEABLE_FAIL_SERVER_NOT_REACHABLE.  It discovers the server on port 443 just fine so I am kind of at a loss where to check next.  

    If someone could point me in remotely the right direction for logs or something else to look at I would be most grateful.

    Thanks

    Also here's the client logs

    Doing logon attempt with data:

       currState=LoggedOut

       sipUri=sip@domain.com

       server=<auto-discovered name>, internal

       authModes=0x1000c

       logonCredPassword.CredType is Default

       proxyAuthModes=0x3f

       epFlags=200

       withAutoRetrials=0

       credsAvailability=CredsValid

       redirectedServersList=

       newState=AboutToLogIn

       statusCode=0]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x11113B58 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x11113B58 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x11113B58 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x11113B58 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[Discovery task with id(1) sent to URL https://lyncdiscoverinternal.domain.com?sipuri=sip@domain.com completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[Discovery task with id(3) sent to URL http://lyncdiscover.domain.com?sipuri=sip@domain.com completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[Discovery task with id(0) sent to URL http://lyncdiscoverinternal.domain.com?sipuri=sip@domain.com completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[Discovery task with id(2) sent to URL https://lyncdiscover.domain.com?sipuri=sip@domain.com completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[Lync autodiscovery completed with hr: 0X80004005 sipint:  sipext:  authint:  authext:  ucwaint:  ucwaext:  wts:  ucwaurl:  telemetryurl:  isServiceInRefresh: 0 isTempError: 0]]></Info>

          <ExecutionDuration>0</ExecutionDuration>

          <SequenceID>1.1.1</SequenceID>

          <hr>0x80004005</hr>

        </Lync-autodiscovery>

        <DNSAutoDiscovery>

          <ExecutionDuration>5003</ExecutionDuration>

          <SequenceID>1.1.2</SequenceID>

          <hr>0x0</hr>

        </DNSAutoDiscovery>

        <Info><![CDATA[sip.domain.com:443, external, discovered added to list of auto-discovered servers]]></Info>

        <Info><![CDATA[

    1 server(s) returned

    14E05708 added to list of auto-discovered servers

    signin to server=sip.domain.com:443, external, discovered

       redirectedServersList=]]></Info>

        <Info><![CDATA[

       VerifyOnEnableEvent result return ONENABLE_FAIL_SERVER_NOT_REACHABLE

       status=0x80ee001c

        ACTION: SERVER NOT REACHABLE

        NO MORE SERVER TO TRY

        ACTION : PERMANENT ERROR]]></Info>

        <ExecutionDuration>116545</ExecutionDuration>

        <SequenceID>1.1</SequenceID>

        <hr>0x80ee001c</hr>

      </Login>

    </root>




    Monday, April 18, 2016 7:59 PM

Answers

  • Hi 

    The best approach is to use Connectivity analyzer and see the results of the tests

    https://www.microsoft.com/en-us/download/details.aspx?id=36535

    Based on the result we would be able to identify the issue with the DNS records ,certificates etc..


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

    Tuesday, April 19, 2016 6:24 AM

All replies

  • Hi 

    The best approach is to use Connectivity analyzer and see the results of the tests

    https://www.microsoft.com/en-us/download/details.aspx?id=36535

    Based on the result we would be able to identify the issue with the DNS records ,certificates etc..


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

    Tuesday, April 19, 2016 6:24 AM
  • Thanks for the reply, it keeps complaining about lyncdiscover.domain.com can't be resolved.   I thought you only needed a reverse proxy for mobility clients and additonal functionality?  I was thinking about putting the reverse proxy into place but currently just have an edge server.

    [4/19/2016 8:51:36 AM] [DEBUG] Logging test parameters:
    [4/19/2016 8:51:36 AM] [DEBUG] SIP Uri: SIP@domain.com
    [4/19/2016 8:51:37 AM] [DEBUG] User Name: 
    [4/19/2016 8:51:37 AM] [DEBUG] Discovery Type: Automatic Discovery
    [4/19/2016 8:51:37 AM] [DEBUG] Network access: NetworkAccessExternal
    [4/19/2016 8:51:37 AM] [DEBUG] Selected client: ApplicationLMX
    [4/19/2016 8:51:37 AM] [SUBHEADING] Starting Lync server autodiscovery
    [4/19/2016 8:51:37 AM] [INFO] Please wait; this test may take several minutes to complete...
    [4/19/2016 8:51:37 AM] [SUMMARY_ERROR] lyncdiscoverinternal.domain.com and lyncdiscover.domain.com can't be resolved by the DNS server. Make sure the SIP URI was entered correctly. 
    [4/19/2016 8:51:37 AM] [SUMMARY] For more information on DNS requirements for automatic discovery, please refer to http://go.microsoft.com/fwlink/?LinkId=278998 
    [4/19/2016 8:51:37 AM] [DEBUG] None, AutoInternalDNSFail, AutoExternalDNSFail, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [4/19/2016 8:51:37 AM] [SUMMARY] 
    [4/19/2016 8:51:37 AM] [SUMMARY_ERROR] lyncdiscoverinternal.domain.com and lyncdiscover.domain.com can't be resolved by the DNS server. Make sure the SIP URI was entered correctly. 
    [4/19/2016 8:51:37 AM] [SUMMARY] For more information on DNS requirements for automatic discovery, please refer to http://go.microsoft.com/fwlink/?LinkId=278998 
    [4/19/2016 8:51:37 AM] [SUMMARY_ERROR] 
    Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.

    Tuesday, April 19, 2016 12:54 PM