No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

Cannot sign into Lync

  • 3 Followers
  • 5 Replies |
  • This post has 1 verified answer |
Answered (Verified) This question is answered

When I try to sign into Lync I get the following message "Cannot sign in because the server is temporarily unavailable. If the problem continues, please contact your support team. When I used the manual settings "sipdir.online.lync.com:443" I am able to connect. I did some troubleshooting with MOSDAL and I got the below information.

Server:  home.domain.actdsltmp
Address:  192.168.0.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
 timeout was 2 seconds.
Name:    sipdir.online.lync.com
Address:  207.46.5.20

Slow link delay for UDP enabled
Querying target system called:
sipdir.online.lync.com
Attempting to resolve name to IP address...
Name resolved to 207.46.5.20
querying...
TCP port 443 (https service): LISTENING
UDP port 443 (https service): LISTENING or FILTERED
Querying target system called:
 sipdir.online.lync.com
Attempting to resolve name to IP address...
Name resolved to 207.46.5.20
querying...
TCP port 443 (https service): LISTENING
UDP port 443 (https service): LISTENING or FILTERED

Once again when I used the manual setttings I am able to sign in to Lync. Assistance will be greatly appreciated.

  • Post Points: 20
Verified Answer
  • Hi Isiah,
    I understand that you can’t sign in Lync and you get the error message that "Cannot sign in because the server is temporarily unavailable. If the problem continues, please contact your support team”. You can sign in by manual settings.
    Before going further, could you let us know if this problem reoccurs when you login to lync client using user account with @yourdomain.onmicrosoft.com as domain suffix?
    Based on my experience, this problem can be related to various factors, for example, you use a custom or vanity domain in Office 365 and the dns records have not been added on dns server yet, or incorrect configuration of network.
    To narrow down this problem, I suggest you to try the following steps and check if the issue can be fixed.
    1.Make sure the SRV and CNAME records of Lync Online service for your domain have been added correctly on dns server first.
       Note: you will be able to get the DNS information for your domain when you click DNS settings in MOP.
    2.Wait for some hours and try again.
    If the issue persists, please refer to steps in KB articles below to resolve this issue.
    Automatic sign-in, domain federation, and other features do not work as expected in Lync Online when you use a custom domain in Office 365
    http://support.microsoft.com/kb/2566790
    How to troubleshoot authentication and connectivity issues in Lync Online
    http://support.microsoft.com/kb/2541980/en-us

    Regards,
    Robert Li

    • Top 150 Contributor
    • Post Points: 0
All Replies
Page 1 of 1 (6 items)