Just for the record this works fine with Windows XP I have a question about Windows 7 and 8021x. You know with windows 7 you can get the pop-up windows and logon using PEAP authentication. If authentication fails for any reason you will never see the pop-up window again. The only way to correct the issue is to disable/enable the nic card or disconnect and reconnect the network cable from the port or enter the 802.1x settings and exit to get the reauthentication to happen. This is the only way I found to get the pop-up window to appear so you can see the message additional logon information is required to connect to this network to this network so you can logon to the network. I also tried this hotfix but it didn't fix the issue. http://support.microsoftkb/980295 Is there any solution so if logon or authentication fails that the pop-up message window will appear so you can logon without doing the steps I mentioned above. Scott

Just a shot in the dark night: Enable baloon? What do Event log files say? Rgds Milos

Hi, I will give this a try tomorrow and get back to you. Thanks Scott Skier The fixed worked great. Thanks for all the help Scott

Hi, I will give this a try tomorrow and get back to you. Thanks ScottSkier

Hi, Please download the hotfix from the link below and see how it works. 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 Tracy Cai TechNet Community Support

Hi Tracy, I did some additional tesing on the hotfix you recommended and I found an issue with Windows 7. When you go to addtional Settings and under 802.1X Settings you can specify the authentication mode. If I select User authentication everything works fine and I am able to get the logon bubble and login without any issues. But if I change it to User or computer authentication then Authenticcation will fail and I will never get th logon bubble until I disable/enable the interface o pull and reinsert the link. Is this a known issue? Also is there another hotfix to fix this issue? Thanks ScottSkier

Hi, Based on my research, User or computer authentication mode is Use computer-only credentials or user-only credentials. An 802.1X always uses security credentials based on the current state of the computer. When a user is logged on, the user's credentials are used for authentication. When no user is logged on, computer-only credentials are used for authentication. If everything works fine with User authentication, this issue may be caused by the failure of Computer credentials authentication. You may recheck the configuration on the server side with guide below and see if any improvement: Configure Wired Computers Running Windows Vista for 802.1X Authenticated Access http://technet.microsoft.com/en-us/library/dd348442(WS.10).aspx Configure Wireless Clients running Windows 7 and Windows Vista for PEAP-MS-CHAP v2 Authentication http://technet.microsoft.com/en-us/library/dd759176.aspx Hope it helps.Tracy Cai TechNet Community Support

Hi, Based on my research, User or computer authentication mode is Use computer-only credentials or user-only credentials. An 802.1X always uses security credentials based on the current state of the computer. When a user is logged on, the user's credentials are used for authentication. When no user is logged on, computer-only credentials are used for authentication. If everything works fine with User authentication, this issue may be caused by the failure of Computer credentials authentication. You may recheck the configuration on the server side with guide below and see if any improvement: Configure Wired Computers Running Windows Vista for 802.1X Authenticated Access http://technet.microsoft.com/en-us/library/dd348442(WS.10).aspx Configure Wireless Clients running Windows 7 and Windows Vista for PEAP-MS-CHAP v2 Authentication http://technet.microsoft.com/en-us/library/dd759176.aspx Hope it helps.Tracy Cai TechNet Community Support