locked
Skype for Business Online - Not Logging on RRS feed

  • Question

  • Hi,

    We use Skype for Business online but for some reason, some installations are able to connect and some are not (stuck on contacting server and signing in). Teams connects quickly and without issue on all devices. I have update our internal DNS with the various SRV records to direct clients to Skype online, I have tried manually entering the correct addresses in the Skype client, I've delete my signin and tried again all to no avail. 

    I'm hoping someone can identify something in the below log that might point to a reason why. I've filtered the log to only show the errors but if the entire log is useful let me know and I'll post. Any assistance would be appreciated

    Log
    06/20/2019|10:51:23.463 21D8:1F90 ERROR :: CHidManager::AddHidDevice - CreateFile(\\?\hid#vid_046d&pid_c52b&mi_01&col01#7&2c7098e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) failed with 0x80070005
    06/20/2019|10:51:23.463 21D8:1F90 ERROR :: CHidManager::EnumerateHidDevices - AddHidDevice failed 0x80070005
    06/20/2019|10:51:23.463 21D8:1F90 ERROR :: CHidManager::AddHidDevice - CreateFile(\\?\hid#vid_046d&pid_c52b&mi_00#7&1a8a95d3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd) failed with 0x80070005
    06/20/2019|10:51:23.463 21D8:1F90 ERROR :: CHidManager::EnumerateHidDevices - AddHidDevice failed 0x80070005
    06/20/2019|10:51:23.494 21D8:1F90 ERROR :: HRESULT failed: 80070032 = hr . failed to get device property MM_DP_LOCATION
    06/20/2019|10:51:23.494 21D8:1F90 ERROR :: HRESULT failed: 80070032 = hr . failed to get device property MM_DP_LOCATION
    06/20/2019|10:51:23.494 21D8:1F90 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi
    06/20/2019|10:51:23.510 21D8:1F90 ERROR :: CUccMediaDeviceManager::LoadCustomTelephonyDeviceCollection: HRESULT failed: 80070002 = hr. Audio capture
    06/20/2019|10:51:23.510 21D8:1F90 ERROR :: CUccMediaDeviceManager::LoadCustomTelephonyDeviceCollection: HRESULT failed: 80070002 = hr. Audio capture
    06/20/2019|10:51:23.980 21D8:1F90 ERROR :: HRESULT failed: 80070032 = hr . failed to get device property MM_DP_LOCATION
    06/20/2019|10:51:23.980 21D8:1F90 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi
    06/20/2019|10:51:24.443 21D8:1F90 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi
    06/20/2019|10:51:25.499 21D8:1F90 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi
    06/20/2019|10:51:48.473 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:51:48.473 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:51:53.503 21D8:2A4C ERROR :: QueryDNSSrv GetDnsResults query: _sipinternaltls._tcp.canadalifere.ie failed 8007232b
    06/20/2019|10:51:53.503 21D8:2A4C ERROR :: DNS_RESOLUTION_WORKITEM::ProcessWorkItem ResolveHostName failed 8007232b
    06/20/2019|10:51:53.503 21D8:1F90 INFO  :: CUccDnsQuery::UpdateLookup - error code=80ee0066, index=0
    06/20/2019|10:51:53.809 21D8:1F90 INFO  :: CUccDnsQuery::UpdateLookup - error code=0, index=1
    06/20/2019|10:51:53.809 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:51:53.809 21D8:2A4C ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:51:53.809 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:51:53.809 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:51:53.809 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:52:14.852 21D8:1F90 ERROR :: CSIPAsyncSocket::OnConnectReady - Error: 10060 dest: 52.112.66.139:443
    06/20/2019|10:52:14.852 21D8:1F90 ERROR :: CSIPClientConnection::OnConnect (80ee0067) this: 000001D9972A3770
    06/20/2019|10:52:14.852 21D8:1F90 ERROR :: SIP_MSG_PROCESSOR::OnConnectComplete connect failed 80ee0067 retry connecting via HTTP tunnel
    06/20/2019|10:52:15.270 21D8:1F90 ERROR :: HTTP_PROXY_RESOLVE_CONTEXT::~HTTP_PROXY_RESOLVE_CONTEXT HPContext handle 1 deleted, this 000001D997AF8370
    06/20/2019|10:52:15.270 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:52:15.270 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:52:15.285 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:52:15.285 21D8:29E4 TRACE :: HTTPPROXYCB:request Complete result(0x0) error(0x2ef1)
    06/20/2019|10:52:15.759 21D8:1F90 INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 000001D9898743C0, callid=(null), ErrorCode: 0x0
    06/20/2019|10:52:16.076 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:52:16.076 21D8:2A4C ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:52:16.276 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:52:16.276 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:52:16.276 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:52:37.318 21D8:1F90 ERROR :: CSIPAsyncSocket::OnConnectReady - Error: 10060 dest: 52.112.67.51:443
    06/20/2019|10:52:37.318 21D8:1F90 ERROR :: CSIPClientConnection::OnConnect (80ee0067) this: 000001D9972A2A30
    06/20/2019|10:52:37.318 21D8:1F90 ERROR :: SIP_MSG_PROCESSOR::OnConnectComplete connect failed 80ee0067 retry connecting via HTTP tunnel
    06/20/2019|10:52:37.803 21D8:1F90 ERROR :: HTTP_PROXY_RESOLVE_CONTEXT::~HTTP_PROXY_RESOLVE_CONTEXT HPContext handle 2 deleted, this 000001D997BDBB10
    06/20/2019|10:52:37.803 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:52:37.803 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:52:37.819 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:52:37.819 21D8:2AFC TRACE :: HTTPPROXYCB:request Complete result(0x0) error(0x2ef1)
    06/20/2019|10:52:38.446 21D8:1F90 INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 000001D997BCADA0, callid=(null), ErrorCode: 0x0
    06/20/2019|10:52:38.609 21D8:1F90 ERROR :: No Certificate
    06/20/2019|10:52:38.609 21D8:1F90 ERROR :: CSipTlsDskSecAssociationNt::ProcessAuthChallengeHelper StartSAProcessingWorkItem fail
    06/20/2019|10:52:38.609 21D8:1F90 WARN  :: SIP_REGISTER(97cd0fd8) SignoutOnError(80ef0191)
    06/20/2019|10:52:38.609 21D8:1F90 ERROR :: HRESULT API failed: 80ee0061 = hr. DisableServManager
    06/20/2019|10:53:25.096 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:25.096 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:30.114 21D8:2A4C ERROR :: QueryDNSSrv GetDnsResults query: _sipinternaltls._tcp.canadalifere.ie failed 8007232b
    06/20/2019|10:53:30.114 21D8:2A4C ERROR :: DNS_RESOLUTION_WORKITEM::ProcessWorkItem ResolveHostName failed 8007232b
    06/20/2019|10:53:30.114 21D8:1F90 INFO  :: CUccDnsQuery::UpdateLookup - error code=80ee0066, index=0
    06/20/2019|10:53:30.294 21D8:1F90 INFO  :: CUccDnsQuery::UpdateLookup - error code=0, index=1
    06/20/2019|10:53:30.294 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:30.294 21D8:2A4C ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:30.299 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:53:30.299 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:53:30.299 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:53:51.329 21D8:1F90 ERROR :: CSIPAsyncSocket::OnConnectReady - Error: 10060 dest: 52.112.66.139:443
    06/20/2019|10:53:51.329 21D8:1F90 ERROR :: CSIPClientConnection::OnConnect (80ee0067) this: 000001D9972A30D0
    06/20/2019|10:53:51.329 21D8:1F90 ERROR :: SIP_MSG_PROCESSOR::OnConnectComplete connect failed 80ee0067 retry connecting via HTTP tunnel
    06/20/2019|10:53:51.939 21D8:1F90 ERROR :: HTTP_PROXY_RESOLVE_CONTEXT::~HTTP_PROXY_RESOLVE_CONTEXT HPContext handle 3 deleted, this 000001D9973EF270
    06/20/2019|10:53:51.939 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:53:51.939 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:53:51.939 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:53:51.939 21D8:2A14 TRACE :: HTTPPROXYCB:request Complete result(0x0) error(0x2ef1)
    06/20/2019|10:53:52.695 21D8:1F90 INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 000001D997BCADA0, callid=(null), ErrorCode: 0x0
    06/20/2019|10:53:52.827 21D8:1F90 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:52.827 21D8:2A4C ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    06/20/2019|10:53:52.996 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:53:52.996 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:53:52.996 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:54:14.033 21D8:1F90 ERROR :: CSIPAsyncSocket::OnConnectReady - Error: 10060 dest: 52.112.67.51:443
    06/20/2019|10:54:14.033 21D8:1F90 ERROR :: CSIPClientConnection::OnConnect (80ee0067) this: 000001D9972A2A30
    06/20/2019|10:54:14.033 21D8:1F90 ERROR :: SIP_MSG_PROCESSOR::OnConnectComplete connect failed 80ee0067 retry connecting via HTTP tunnel
    06/20/2019|10:54:14.365 21D8:1F90 ERROR :: HTTP_PROXY_RESOLVE_CONTEXT::~HTTP_PROXY_RESOLVE_CONTEXT HPContext handle 4 deleted, this 000001D9973EF6F0
    06/20/2019|10:54:14.365 21D8:1F90 ERROR :: CSIPClientConnection::AttachLyntrix no instance of CLyntrixClient
    06/20/2019|10:54:14.365 21D8:1F90 ERROR :: CSIPClientConnection::Initialize AttachLyntrix failed hr=80004005
    06/20/2019|10:54:14.365 21D8:1F90 ERROR :: CSIPAsyncSocket::Connect: HRESULT API failed: 80072733 = hr
    06/20/2019|10:54:14.365 21D8:29A0 TRACE :: HTTPPROXYCB:request Complete result(0x0) error(0x2ef1)
    06/20/2019|10:54:15.155 21D8:1F90 INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 000001D997C0E760, callid=(null), ErrorCode: 0x0
    06/20/2019|10:54:15.359 21D8:1F90 ERROR :: No Certificate
    06/20/2019|10:54:15.359 21D8:1F90 ERROR :: CSipTlsDskSecAssociationNt::ProcessAuthChallengeHelper StartSAProcessingWorkItem fail
    06/20/2019|10:54:15.359 21D8:1F90 WARN  :: SIP_REGISTER(97cd0fd8) SignoutOnError(80ef0191)
    06/20/2019|10:54:15.359 21D8:1F90 ERROR :: HRESULT API failed: 80ee0061 = hr. DisableServManager


    Thursday, June 20, 2019 10:12 AM

Answers

  • Hi Shaw,

    In the end I tethered the problem computers to my phone and was able to log on to Skype. In doing so the certificate was downloaded. Once this was done I reverted back to the network connection and I'm now able to log on as normal.

    What's strange is the fact that only some computers were unable to download the certificate when connected to the network. Other computers on the same subnet, traversing the same routers and firewalls and the same proxy had no issues.

    Either way, problem resolved for now.

    Thanks for your assistance.

    Paul

    • Proposed as answer by Shaw_Lu Wednesday, June 26, 2019 9:58 AM
    • Marked as answer by Paul1Mar Wednesday, June 26, 2019 10:00 AM
    Wednesday, June 26, 2019 9:55 AM

All replies

  • Hi Paul1Mar,

    Do you use Skype for Business online only or hybrid mode?

    Is there any difference between the affected and unaffected user machines, such as network?

    What DNS records do you add in your internal DNS?

    I notice you have tried to manually entering the address, please use the “sipdir.online.lync.com:443” as “Internal server name” and “External server name” in Skype client “Manual configuration”.

    In the logs, there are some DNS SRV query errors, please refer to this article to review your DNS configuration for Skype for Business Online.

    https://docs.microsoft.com/en-us/SkypeForBusiness/troubleshoot/online-configuration/dns-configuration-issue

    In addition, try to use “Remote Connectivity Analyzer” to do a test with the affected account and check the result.

    https://testconnectivity.microsoft.com/


    Best Regards,
    Shaw Lu


    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.

    Friday, June 21, 2019 2:17 AM
  • Hi Shaw,

    That was the document i followed to add the SVR and CNAME record to my internal DNS. We're using Skype online only and have never had on on-prem Lync server. Strangely, when I run the connectivity analyser it comes back with "Connectivity Test failed" and errors stating that it was unable to resolve any of the SRV or CNAME URLs. I've verified them using nslookup though (output below) so don't understand why it would be failing.

    I can confirm that I tried connecting both using DNS and with the URLs hard coded as you've indicated into the Skype client. Below is the output from nslookup

    > _sip._tls.myUPNDomain.com

    Server:  DCHOSTNAME.MyAdDomain.com

    Address:  10.14.208.21

    _sip._tls.myUPNDomain.com       SRV service location:
              priority       = 100
              weight         = 1
              port           = 443
              svr hostname   = sipdir.online.lync.com
    sipdir.online.lync.com  internet address = 52.112.66.139
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:a::b
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:4::b
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:5::b
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:e::f
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:c::f
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:7::b
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037:0:2::b
    sipdir.online.lync.com  AAAA IPv6 address = 2603:1037::b
    > _sipfederationtls._tcp.myUPNDomain.com
    Server:  DCHostname.MyADDomain.com
    Address:  10.14.208.21

    _sipfederationtls._tcp.myUPNDomain.com  SRV service location:
              priority       = 100
              weight         = 1
              port           = 5061
              svr hostname   = sipfed.online.lync.com
    sipfed.online.lync.com  internet address = 52.112.67.51
    sipfed.online.lync.com  AAAA IPv6 address = 2603:1037:0:2::b

    Thanks

    Paul

    Friday, June 21, 2019 4:18 PM
  • Hi Paul1Mar,

    Do you have these DNS records in public DNS?

    “Remote Connectivity Analyzer” would search public DNS records for the test. Usually domain name registrar also provides DNS service, and it could add the related DNS records for your domain.

    In the logs, there are some errors about “CSIPAsyncSocket::OnConnectReady - Error: 10060 dest: 52.112.66.139:443”. I think try to flush the DNS cache.

    In addition, O365 has multiple IP addresses, please check the O365 IPs are allowed in your firewall.

    Here is a reference about O365 IP ranges:

    https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges


    Best Regards,
    Shaw Lu


    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.

    Monday, June 24, 2019 6:06 AM
  • Hi Shaw,

    Before now these records were only internal. Since then though I have had them published but this hasn't made any difference (expect that now the connectivity analyser runs successfully. This is just a DNS test though.

    I have flush DNS many times on all effected client but make no difference. Regarding firewall, I would have expected if this was firewall related that the issue with affect all users, not just some.

    One thing to note, on all effected computers when trying to connect, throughout the trace log I'm seeing "DC8 ERROR :: No Certificate" following by a series of errors like SIP_AUTH failure.

    Why would a Skype for Business desktop client not be able to get a certificate?

    Note:

    - this is a Skype Online environment. There has never been a Lync server on-prem

    - This isn't a user specific issue. I can log on fine on one computer but not another. 

    Regards

    Paul

    Tuesday, June 25, 2019 1:14 PM
  • Hi Paul,

    Skype for Business will require a client authentication certificate to connect to Skype Online.

    You could run “cretmgr.msc” to open current user certificate store, and navigate to “Personal” – “Certificates” to check if there is such a certificate:

    In another way, it only happens on specific machine, have a try to reset the network:

    netsh winsock reset

    netsh int ip reset

    Also check if there is any third-party application cause it.


    Best Regards,
    Shaw Lu


    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.

    Wednesday, June 26, 2019 9:28 AM
  • Hi Shaw,

    In the end I tethered the problem computers to my phone and was able to log on to Skype. In doing so the certificate was downloaded. Once this was done I reverted back to the network connection and I'm now able to log on as normal.

    What's strange is the fact that only some computers were unable to download the certificate when connected to the network. Other computers on the same subnet, traversing the same routers and firewalls and the same proxy had no issues.

    Either way, problem resolved for now.

    Thanks for your assistance.

    Paul

    • Proposed as answer by Shaw_Lu Wednesday, June 26, 2019 9:58 AM
    • Marked as answer by Paul1Mar Wednesday, June 26, 2019 10:00 AM
    Wednesday, June 26, 2019 9:55 AM