Article ID: 931856 - View products that this article applies to.
Consider the following scenario:
This problem occurs because the client computer that uses 802.1X authentication will not respond to the EAP request identity packets that the Ethernet switch sends. The client computer does not respond because it does not have a valid certificate. Therefore, the client computer sends an EAP over LAN (EAPOL) start frame and does not respond to the EAP request identity packet.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756To resolve this problem, follow these steps:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
The following table describes the SupplicantMode registry entry for values from 0 through 3.
The SupplicantMode registry entry is also explained in the "Deployment of IEEE 802.1X for Wired Networks Using Microsoft Windows" article. To download this article, visit the following Microsoft Web site:
Collapse this tableExpand this table
http://www.microsoft.com/downloads/details.aspx?familyid=05951071-6b20-4cef-9939-47c397ffd3dd&displaylang=enNote The SupplicantMode registry entry is no longer valid for Wired 802.1X in Windows XP SP3. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/949984/ )Changes to the 802.1X-based wired network connection settings in Windows XP Service Pack 3
Article ID: 931856 - Last Review: September 24, 2009 - Revision: 2.0