When the ADAL STS URL resolves to an internal ADFS server, and Integrated Windows Authentication is enabled in browsers, computers on which many users sign in to client applications may not authenticate the logon attempts. The value 0x10000 represents the “Prompt for user name and password” setting. Location: HKEY_LOCAL\MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1 Push the following registry key to the affected client computers by using the following Group Policy Object: In the User Authentication section, select the Prompt for user name and password option. Typically, this is the Local Intranet zone.Ĭlick the Custom level button, and then scroll to the end of the Settings list. Select the security zone that includes the STS URL. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. To do this, use one of the following methods. To resolve this issue, change the Internet Explorer “User Authentication” settings on the affected client computers to “prompt for user name and password” in the security zone. Therefore, users are signing in to Skype for Business by using different user credentials than those for the account that is logged on to the Operating System. This issue occurs because Integrated Windows Authentication is enabled for the ADAL Security Token Service (STS) URL. If that doesn’t work, contact your support team. It might be your sign-in address or logon credentials, so try those again. When done, try signing in to Skype for Business and check to see whether or not the problem has been resolved.You didn’t get signed in.
Type the following into both the Internal server name box and the External server name box:.Click on Advanced after your email address, and select Manual configuration.On the sign-in page in Skype for Business, click on the gear and then click on Personal.
To try and fix this problem by yourself, you need to: However, if the problem doesn’t go away on its own, fear not as there is something that you can do to try and get rid of this problem yourself. If you are experiencing this problem because the Lync server Skype for Business is trying to access is actually unresponsive, the problem should sort itself out in a few hours, and all you have to do is wait. This problem occurs either because DNS records related to Skype for Business haven’t been added to your computer or couldn’t be found by the application, or because the Lync server that Skype for Business is trying to access in order to sign you in is not responding.
0 kommentar(er)
