802.1 X Client Issues

Some known issues are reported and they have related hotfixes.

Here, you can find some of them:

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 802.1x User authentication configured, but client fails to authenticate, then when wire is reconnected or “Wired AutoConfig” service is restarted, the authentication is done. It could be produced because “Wired AutoConfig” service is not ready when “Netlogon” tries the authentication.

You can configure a service dependency, to start “Netlogon” service when “Wired AutoConfig” would be started.

Debugging and troubleshouting

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