This update provides support for Wireless Protected Access, a new standards-based wireless security solution developed by the Wi-Fi Alliance. WPA is intended to replace the existing Wired Equivalent Privacy (WEP) standard, offering much more robust methods of encryption and authentication and resulting in a new level of protection for customers taking advantage of the wireless features of Windows XP.
The following problems are resolved by this update: You Experience a Long Delay When You Connect to a Wireless Network
When you connect to a wireless network by using 802.1x authentication, your network connection may take between 30 to 60 seconds to be established. This problem occurs because the Wireless Zero Configuration service is delayed when it tries to start. The Wireless Zero Configuration service does not start in a timely manner because it depends on the NETMAN component, but the NETMAN component has not yet been loaded at startup.An Incorrect Media Status Appears for the Wireless Interface
When your computer is the only computer in a wireless network that is in ad-hoc mode, the wireless network connection icon may incorrectly show that the wireless network adapter is connected. User Interface Items Are Incorrectly Translated in Other Languages
Several user interface items in the Windows XP Support Patch for Wireless Protected Access (WPA) package that is described in the following Microsoft Knowledge Base article are incorrectly translated in some Far East languages: 815485 Overview of the WPA Wireless Security Update in Windows XP WPA Does Not Work Correctly in Mixed AES/TKIP Modes
WPA does not work correctly with an access point that is configured for Advanced Encryption Standard (AES) encryption for unicast transmission and Temporary Key Integrity Protocol (TKIP) encryption for broadcast transmission.WPA Defaults to a Weaker Encryption Scheme
By default, when a wireless client is offered the ability to connect to a wireless network by using the TKIP encryption scheme or by using the AES encryption scheme, the client selects the weaker encryption scheme. Wireless Networking Client Incorrectly Responds to an RC4 Key Message in Non-WEP Mode
When you connect to a wireless connection that is encrypted by using the AES encryption, Windows incorrectly responds to an RC4 encryption algorithm message. Cannot Reconnect to the Preferred Network After an Unsuccessful Key Exchange
When a wireless client key exchange operation is unsuccessful, the client fails the connection and blocks attempts to automatically reconnect. You must then manually try to reconnect to the wireless network. 802.1x Failure Counter is Not Reset After a Successful Key Exchange
The Wireless Zero Configuration service maintains a counter of unsuccessful authentication and key exchange attempts. However, when a wireless client successfully authenticates and performs a key exchange, this counter is not automatically reset.This update also resolves the problems that are described in the following Knowledge Base articles: 822596 DHCP Does Not Obtain a New Address When EAP Reauthenticates Across Access Points with IP Subnets That Differ 826239 Small Delay in Logon to Network When You Use a Wireless Network Connection Download - Multiple language versions available
When you connect to a wireless network by using 802.1x authentication, your network connection may take between 30 to 60 seconds to be established. This problem occurs because the Wireless Zero Configuration service is delayed when it tries to start. The Wireless Zero Configuration service does not start in a timely manner because it depends on the NETMAN component, but the NETMAN component has not yet been loaded at startup.An Incorrect Media Status Appears for the Wireless Interface
When your computer is the only computer in a wireless network that is in ad-hoc mode, the wireless network connection icon may incorrectly show that the wireless network adapter is connected. User Interface Items Are Incorrectly Translated in Other Languages
Several user interface items in the Windows XP Support Patch for Wireless Protected Access (WPA) package that is described in the following Microsoft Knowledge Base article are incorrectly translated in some Far East languages: 815485 Overview of the WPA Wireless Security Update in Windows XP WPA Does Not Work Correctly in Mixed AES/TKIP Modes
WPA does not work correctly with an access point that is configured for Advanced Encryption Standard (AES) encryption for unicast transmission and Temporary Key Integrity Protocol (TKIP) encryption for broadcast transmission.WPA Defaults to a Weaker Encryption Scheme
By default, when a wireless client is offered the ability to connect to a wireless network by using the TKIP encryption scheme or by using the AES encryption scheme, the client selects the weaker encryption scheme. Wireless Networking Client Incorrectly Responds to an RC4 Key Message in Non-WEP Mode
When you connect to a wireless connection that is encrypted by using the AES encryption, Windows incorrectly responds to an RC4 encryption algorithm message. Cannot Reconnect to the Preferred Network After an Unsuccessful Key Exchange
When a wireless client key exchange operation is unsuccessful, the client fails the connection and blocks attempts to automatically reconnect. You must then manually try to reconnect to the wireless network. 802.1x Failure Counter is Not Reset After a Successful Key Exchange
The Wireless Zero Configuration service maintains a counter of unsuccessful authentication and key exchange attempts. However, when a wireless client successfully authenticates and performs a key exchange, this counter is not automatically reset.This update also resolves the problems that are described in the following Knowledge Base articles: 822596 DHCP Does Not Obtain a New Address When EAP Reauthenticates Across Access Points with IP Subnets That Differ 826239 Small Delay in Logon to Network When You Use a Wireless Network Connection Download - Multiple language versions available
