大网数据广告活动
账户与安全

SSO with pre-logon fails during user logon after a restart

· 52CE 我爱测

Wireless and Wired 802.1x Authentication may fail on the first logon after a restart if the client system is configured to use a Single Sign On (SSO) profile with pre-logon.

This article provides a solution to an issue that Single Sign On (SSO) profile with pre-logon fails during user logon after a restart.

Original KB number:   3063910

Symptoms

Wireless and Wired 802.1x Authentication fails on the first logon attempt after a system restart if the client system is configured to use a SSO profile with pre-logon. In this situation, the user receives the following error message:

There are currently no logon servers available to service the logon request.

The message window resembles the following screenshot.

Cause

This problem is caused by a race-condition that occurs during the boot sequence between the Pre-Logon Authentication Provider (PLAP) logon filter and either the Wired Autoconfig service (for wired connections) or the WLAN Autoconfig service (for wireless connections). The logon filter queries for SSO profiles. However, if the respective Autoconfig service is not fully initialized by the time of the query, the client won't be SSO-configured. Therefore, users can't log on by using SSO.

Workaround

To work around this problem, connect users through a non-802.1x -protected network to cache their credentials during the first logon.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

More information

This problem doesn't usually occur. However, if you do encounter this problem, we recommend that you open a support case and collect the relevant log information. To do this, follow these steps:

  1. Open an elevated command prompt.

  2. Run the following command:

    netsh trace start persistent=yes overwrite=yes maxsize=4096 tracefile=c:\net_plap.etl provider={2CF38663-F760-46AC-AAFA-2DDE7F9DB417} keywords=0xffffffffffffffff level=0xff provider="Microsoft-Windows-L2NACP" keywords=0xffffffffffffffff level=0xff
    
  3. Restart the computer.

  4. Reproduce the logon issue.

  5. Connect to an unprotected network to successfully log on and stop the trace. To do this, run the following command:

    netsh trace stop
    

    This generates the trace file: c:\net_plap.etl.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。