Skype For Business Mac Showing Network Error

Posted on by admin



PROBLEM

To troubleshoot Skype for Business Online sign-in errors, start by eliminating the most common causes of sign-in difficulty. If necessary, you can then follow specific resolution steps based on the type of error. If the user still cannot sign in, collect additional information, and then seek additional help. Set up Skype for Business Online.

Skype TX control works with the appliance to manage the end to end professional calling experience. Turn any Skype caller in to a professional studio grade feed with the Skype TX appliance Skype TX converts Skype calls in to professional HD-SDI feeds ready to be integrated into production workflows. 24- Cannot hangup interactive call.Sense a pattern here? 35- Not connected.Useful if you think you are talking to someone over Skype, but you actually are not connected to them.Gotta tell ya, has. This integration with Outlook allows us to view the contacts and scheduled meetings details from Skype for Business application itself; instead of opening Outlook application. I'm trying to log in to skype for business on a mac and receive the error: 'You're not configured to connect to the server. Note: in real life not all mentioned steps are conducted by the Skype for Business client. So as you see in the video, the Skype4b client is designed to search for the frontend pool using pre-coded DNS records, it gets the domain name from the user’s sip-address one in red (user@ sip-domain) then start adding to it pre-coded values in the following order.

Consider the following scenario:

  • An Office 365 for enterprises, Office 365 for education, or Office 365 business customer sets up single sign-on (SSO) in Active Directory Federation Services (AD FS) 2.0.

  • Federated users who connect from inside their corporate network can't sign in to Skype for Business Online (formerly Lync Online) from Lync 2013, and they receive the following error message:

    Cannot sign in because the server is temporarily unavailable.

Note This issue only applies to Enterprise SSO users who sign in to Skype for Business Online by using Lync 2013 from inside their corporate network. The issue doesn't apply to users on Microsoft Lync 2010, users who aren't on Skype for Business Online, or users who connect from outside their corporate network.

SOLUTION

Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
Because there are many possible causes, it's best to work through all the following solutions, and then verify the configuration.

For

  1. When you deploy an AD FS 2.0 Federation Server farm, you must specify a domain-based service account that needs a registered SPN to enable Kerberos authentication to function correctly. For more info, see the following TechNet wiki:

    AD FS 2.0: How to Configure the SPN (servicePrincipalName) for the Service AccountThe reasons that you may have to set the SPN manually on the AD FS 2.0 service account are as follows:

    • SPN registration failed during initial configuration of the farm.

    • The Federation Service name was changed.

    • The service account was changed.

  2. Make sure that the AD FS 2.0 service is running under the domain-based service account that was mentioned in the previous step. For example, in the following image, TRLABV3 is the internal host name, and ADFSSvc is the service account:

  3. Configure the AD FS 2.0 server to accept request headers that are larger than 40 kilobytes (KB). You may have to do this when the user is a member of many Active Directory Domain Services (AD DS) user groups. When a user is a member of many AD DS groups, the size of the Kerberos authentication token for the user increases.
    The HTTP request that the user sends to the Internet Information Services (IIS) server contains the Kerberos token in the WWW-Authenticate header. Therefore, the header size increases as the number of groups increases. If the HTTP header or packet size increases beyond the limits that are configured in IIS, IIS may reject the request and send an error as the response. For more info, see the following Microsoft Knowledge Base article:

    2020943 'HTTP 400 - Bad Request (Request Header too long)' error in Internet Information Services (IIS) To work around this issue, use one of the following methods:

    1. Decrease the number of AD DS user groups that the user is a member of.

    2. Change the MaxFieldLength and the MaxRequestBytes registry values on the server that's running IIS so that the user’s request headers aren't considered too long. These two registry values are located under the following registry subkey:

      HKEY_LOCAL_MACHINESystemCurrentControlSetServicesHTTPParameters

  4. If you've deployed multiple AD FS 2.0 servers in a farm and have them load balanced, the Lync 2013 client may be unable to direct the request to the AD FS 2.0 server. Adding an entry for the AD FS 2.0 server to the Hosts file on the client that points directly to the AD FS 2.0 server will bypass the virtual IP of the load balancer.

  5. If the previous solutions didn't resolve the problem and downgrading to Lync 2010 isn't an option, follow these steps to work around the problem.
    Note If a local administrator account doesn't already exist on the computer, you'll have to create one for this solution to work.

    1. Browse to the Lync 2013 executable in Windows Explorer:

    2. Hold down the Shift key, and then right-click Lync.exe.

    3. Click Run as different user.

    4. Enter the credentials for a local administrator account on the computer, and then press Enter.

MORE INFORMATION

Showing

This issue typically occurs because of a misconfiguration in AD FS 2.0. Other services such as Microsoft Exchange Online may work correctly despite this configuration. The usual causes are listed here:

  • The ServicePrincipalName (SPN) isn't configured correctly. The reasons for this include the following:

    • SPN registration failed during initial configuration of the farm.

    • The Federation Service name was changed.

    • The service account was changed.

  • The AD FS 2.0 service isn't running under the correct service account.

  • The request header from Lync 2013 is rejected by IIS and the AD FS 2.0 server because the header is too large. This issue can occur because the user account is a member of too many AD DS user groups.

  • The AD FS 2.0 server farm is load balanced, and the request isn't reaching the AD FS 2.0 server.

Skype For Business Mac Download

For more help with deploying AD FS 2.0 for use with SSO in Office 365, see the following TechNet website:

Skype For Business Mac Showing Network Error 10

Plan for and deploy AD FS for use with single sign-onIn the case when the user is a member of too many AD DS groups, the following entry is entered in the Microsoft Online Services Sign-In Assistant trace logs (these logs are usually located in C: MSOSSPTrace):

Skype For Business Mac Updates


Still need help? Go to Microsoft Community.