5.1.3.2.1.9. 802.1x Client issues

Here you can find a list of reported 802.1x issues with related hotfixes:

• KB 976210: You cannot connect to an 802.1x wired network when you run an automated build process

• KB 976373: A computer that is connected to an IEEE 802.1x-authenticated network via another 802.1x enabled device does not connect to the correct network

• KB 980295: No response to 802.1x authentication requests after authentication fails on a computer that is running Windows 7 or Windows Server 2008 R2

• KB 2481614: Windows 7 may connect to a guest network instead of a corporate network (defined by GPO)

• KB 2491809: Logged-on user accounts do not receive a pop-up balloon to authenticate an 802.1x secured network in Windows 7 and in Windows Server 2008 R2

• KB 2494172: Windows 7 does not connect to an IEEE 802.1x-authenticated network if an invalid certificate is installed

• KB 2769121: 802.1x authentication fails on a Windows 7-based or Windows 2008 R2-based computer that has multiple certificates

• KB 2736878: 802.1x authentication fails after you connect a computer to a network in Windows 7 SP1 or Windows Server 2008 R2 SP1

• KB 2835595: The logon pop-up dialog box does not appear when you connect a Windows 7 SP1-based or Windows Server 2008 R2-based computer to a network

If you have the 802.1x User authentication configured, but a client fails to authenticate, then when wire is reconnected or Wired AutoConfig service is restarted, the authentication is done.

The problem could occur because Wired AutoConfig service was not ready when the Netlogon tried the authentication.

You can configure a service dependency, to start Netlogon service when Wired AutoConfig”* starts.

You can also the see the Event Viewer under Windows Logs -> System and look for events with Source as RemoteAccess or Rasman that could help troubleshoot the issue.