snooz Posted January 4, 2007 Posted January 4, 2007 When you enable a WLAN card the WebClient and Wireless Zero Config is required to prevent slow boots. What commonly happens is the WZC service is set to manual or disabled after you install your 3rd party client and the WebClient service is Auto. WebClient trys to start and the Wireless Zero Config is not running so it hangs because it needs the WZC service. After about a 2+ minute delay you will notice the WebClient service is in a Stopped state. This will also occur if you disable both services as well so there is no way to get around it. There is one workaround however and that is to assign a manual IP to your WLAN card.I opened a case with Microsoft on this because I figured it was a bug. They came back and said this was by design and they will not change it.Hope this helps some of you because it appears to be a common problem on the net.
ZileXa Posted January 5, 2007 Posted January 5, 2007 (edited) I use to have this problem (and assigning a manual IP was indeed a workaround), not just with wireless, also with normal LAN.But don't have it anymore (since 2 years or so..) Make sure you use SP2 + RyanVM's updatepack. Edited January 5, 2007 by ZileXa
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now