When you work in a wireless network environment on a Microsoft Windows Vista OS based computer, you may encounter several problems as follows: –

a. You try to use computer authentication and user authentication to switch the client computer to different VLANs. However, the client computer does not obtain the correct IP address during VLAN switching. This problem is due to your IEEE 802.1X authentication that is based on Virtual Local Area Network (VLAN) switching may fail.

b. If different vendors provide more than one EAP method, the EAP method that is displayed in a wireless profile is not the EAP method that is actually selected. This is because in a wireless profile, the information about the Extensible Authentication Protocol (EAP) method that is selected in a user interface may be incorrect.

c. A wireless profile that an independent hardware vendor (IHV) provides may be corrupted after you use the wireless profile user interface to edit the profile. When this problem occurs, you may receive an error message that Windows Explorer has crashed.

d. Every time that you roam to a different wireless access point, you are prompted to provide a user credential. This problem occurs even if you have saved the user credential.

e. You registered a Protected Extensible Authentication Protocol (PEAP) method that the IHV provided. When you try to authenticate against an Internet Authentication Service (IAS) server, the server may reject the authentication, and the IAS server may send an error message that the authentication has failed. The Onex.dll file crashes when this problem occurs.

The aforesaid wireless authentication and connectivity problems can be fixed with a supported hotfix from Microsoft. This KB932063 hotfix can be obtained from Microsoft Web site.