Article ID: 834565 - Last Review: May 17, 2007 - Revision: 2.7 It takes a long time to connect to your wireless network when you start your Windows XP-based computer
On This PageSYMPTOMS
If you use a wireless connection to your network, it may take up to two minutes to connect to your network when you start your Microsoft Windows XP-based computer. This problem only occurs if you are using 802.1X authentication and you have unchecked the Authenticate as computer when computer information is available option. You may not experience this problem every time that you start your computer. CAUSE
This problem occurs because a race condition is created when the ZeroConfig component and Extensible Authentication Protocol over Local Area Network (EAPOL) initialize. A race condition occurs when data propagates rapidly through a logic circuit far ahead of the clock signal that is intended to control its passage. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:322389
(http://support.microsoft.com/kb/322389/EN-US/
)
How to obtain the latest Windows XP service pack Hotfix informationNote Before you apply the hotfix that is described in this article, apply the Wireless Update Rollup Package for Windows XP. If the Wireless Update Rollup Package for Windows XP resolves the problem, you do not have to apply the hotfix. For additional information about how to obtain the Wireless Update Rollup Package for Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:826942
(http://support.microsoft.com/kb/826942/
)
Wireless update rollup package for Windows XP is available
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 03-Mar-2004 01:29 5.1.2600.1351 103,936 Dhcpcsvc.dll 03-Mar-2004 00:14 5.1.2600.1331 168,192 Ndis.sys 10-Jan-2004 13:33 5.1.2600.1331 12,416 Ndisuio.sys 03-Mar-2004 01:29 5.1.2600.1331 1,630,720 Netshell.dll 10-Jan-2004 13:34 5.1.2600.1331 84,864 Nwlnkipx.sys 03-Mar-2004 01:29 5.1.2600.1335 57,344 Wzcdlg.dll 03-Mar-2004 01:29 5.1.2600.1335 31,232 Wzcsapi.dll 03-Mar-2004 01:29 5.1.2600.1335 282,112 Wzcsvc.dll 02-Mar-2004 00:57 5.1.2600.1359 593,408 Xpsp2res.dll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2. MORE INFORMATIONFor additional information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top