Why does it take so long for networking, specifically wirele

[nikemen]

Why does it take sooo long for networking to boot up in WinXP? It is usually about 2-3 minutes after I see the desktop, that networking loads and is available. Not just seeing the wireless network, but networking computers popping up in the menu bar and AC coming to life.

any thoughts about how to speed this up, or have it load earlier.

[Leon]

Start the Zero Wireless Config Service.......

[nikemen]

Why would that affect all networking, ether as well?

[level]

I've got the same problem on a T-41. Hope someone has an answer and work-around.

[nikemen]

to be honest with ya'll, I think this is a WinXP issue, since it has been such a problem since Winxp one, sp1 on an A20 from a few years ago. I think MSFT just wanted people to get to the Desktop fater, and not necessarilly connect faster.

Maybe it has something to do with antivirus, till that service is running?

[Leon]

Why would that affect all networking, ether as well?

cause it slows down the wireless connect considerably if it's not running, and other network connections might be waiting to start until wireless connects (or doesn't)...

[Kenn]

Start the Zero Wireless Config Service.......

That is exactly the right answer.

Windows XP had an issue where a wireless connection might take 60 or 120 seconds after boot to find a connection (this happened whenever I booted up on a different network from where I shutdown previously. If I rebooted while on the same wireless network, it would connect instantly).

SP2 specifically addresses this fault, but only when Wireless Zero Config is enabled. So if you run IBM Access Connections without Wireless Zero config, the solution is to re-enable WZC.

Hope this helps!