Wireless Zero Configuration Service

[samuraijake]

I have a Toshiba laptop [A15-s157] running Windows XP with an integrated 802.11b wireless adapter. I haven't been able to get the wireless adapter to work. I was forced to use an external D-Link USB adapter [DWL-120d] to connect to my wireless networks. Having recently been annoyed by the external device, I began to investigate why the integrated adapter would not function. I discovered that the Wireless Zero Configuration Service in Windows XP is not installed. There is no third party software to control the internal adapter, thus I need the WZC service. Many guides which I consulted gave instructions on how to start/stop the service, but that only works if the service is available. It is not even listed with the other services. Any ideas on how to get it installed? Any help is appreciated. Thanks.

 

[cmetz]

That's odd, I believe it's installed by default in Windows. I don't know how to install it from scratch, some Windows person might, but a Windows reinstall should hook you up and might be appropriate anyway. My non-expert experience is that the WZC service is needed for Windows to manage an 802.11 device, no WZC, no proper function.

 

[samuraijake]

Thanks for the input. I just figured it out. In the registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WZCSVC was missing a DWORD value. It was named "Start" and it had a hex value of 2. I added that "Start" entry and WZC now works like a charm.

 

[bsobel]

Originally posted by: samuraijake
Thanks for the input. I just figured it out. In the registry, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WZCSVC was missing a DWORD value. It was named "Start" and it had a hex value of 2. I added that "Start" entry and WZC now works like a charm.

Weird, very weird (but glad it's working!)
Bill

 

[ktwebb]

"My non-expert experience is that the WZC service is needed for Windows to manage an 802.11 device, no WZC, no proper function."

Not only is it not needed most of the time but it's better to not use. IMO anyway. Unfortunately some vendors aren't making utilitites that work with XP and you really do need it to monitor but it's basically a tool for noobs. Not very detailed and can cause problems with dropped connections etc. Just not very good software. Disabled on all my rigs.

 

[samuraijake]

Not very detailed and can cause problems with dropped connections etc. Just not very good software.

I agree. Unfortunately, no software is available for this particular adapter, and I am forced to use WZC. I guess until I get around to writing my own configuration software, I'm stuck with the industry default...

 

[JackMDS]

I think that WinXP is a great OS.

However it was released in 2001 and Microsoft can not predict all the future moves of Hardware Manufactures that do not adhere to many Agreed upon Settings.

The Entry Level Wireless Network Hardware is really great considering the price, but most of the manufactures are employing variety of technological short cuts.

ktwebb post above is quite right.

My way to deal with it is to disable the WCZ (the best way to enable and disable it manually in the Computer Management Services).

If there is no manufacture Utility available you can not configure through the Drivers than there is no other choice but the use WCZ. I never had to use it, but I am still short of claiming that I used all the Wireless hardware in the world.

 

[Salvador]

If you select manual instead of automatic, will it stop drop outs? You can't disable it really because then you'd just be shutting off your wireless configuration all together. One thing that I noticed is that whenever I reboot, I have to go back into Management Services and start the device each time. Is this correct?

The jury is still out on the drop outs for me. When I enabled it, the connection didn't come on right away, even though it said that my connection was excellent. I haven't surfed enough on regular basis with it yet to find out if it's not dropping my connection.

KT: Are you saying that you disable WZC all together and then use the software for the device from the manufacturer instead? I didn't even look at Linksys' site to see if they have separate software to run for XP.

BTW.. I'm having the drop out problems with my Linksys WUSB11. I hate it because it seems to drop out at the most inopportune times for me. The device works perfectly in Windows 98SE with the Linksys software, so it has to be XP that's causing the problems.

Sal

 

[ktwebb]

"KT: Are you saying that you disable WZC all together and then use the software for the device from the manufacturer instead? I didn't even look at Linksys' site to see if they have separate software to run for XP.

Yes. WZC was an idiotproof procedure for microsoft. Easy to use, just not very well put together. Unfortunately some Mfg's don't make a utility for XP. If linksys does, then I'd use it. Even if they don't I'd try the utility that is designed for win2000. That may work fine in XP. Stop and disable the service. It WON'T stop your ability to use a wireless card, though your card may require it.

 

[Salvador]

I looked on the Linksys site and they don't have any software for XP. Just the drivers is all. Whenever I want to update the drive from Linksys, Windows tells me that the driver that I currently have from Windows is better, even though it's older. I had to force the issue and tell Windows that I wanted this other driver instead of the one that they wanted to keep. I see no difference so far.

What do you mean by using the Windows 2000 Utility? Where can I find just the Windows 2000 utility and how to I implement it?

I just may go back to Windows 2000 for my wireless systems if this is all the better I can get with XP.

Sal

 

[ktwebb]

I don't use linksys gear. Nothing against it, just haven't used their wireless. I assume they have a utility that supports windows 2000. Don't really know how to be clearer than that.

 

[Salvador]

I don't use linksys gear. Nothing against it, just haven't used their wireless. I assume they have a utility that supports windows 2000. Don't really know how to be clearer than that.

Ok.. You're saying to use software that Linksys might have for Windows 2000 even though they say it's not for XP. I thought you were saying to do something more elaborate than that.

What kind of hardware do you use? I don't mind spending extra money for something that's going to work well. I have no choice with the basement because it would take a lot of time and money to get a cat5 cable run down there.

Sal

 

[ktwebb]

Currently I am using a Avaya (Orinoco) in one laptop, a cisco 350 in another. Have a Orinoco based no name brand USB card for a desktop. Not that it matters. I'd imagine the linksys works fine in XP most of the time. You may have a specific issue with yours but Linksys sells too many AP/card solutions for them to be completely broke.

 

[Salvador]

I thought that I had upgraded my driver, but Windows still didn't let me. The newest driver was out 10/2003 and my driver is from 2001. What pisses me off is that I can't figure out how to get Windows to accept the new driver. I've tried uninstalling, but every time I go to install it, Windows detects the device and installs its own drivers. When I try updating the drivers, Windows tells me that the drivers that I currently have are better than the newer drivers.

How can I uninstall the old drivers and get Windows XP to accept the new drivers?

BTW.. Linksys doesn't have a utility for Windows 2000 either, so I guess I'm stuck with trying drivers for XP.

I can't imagine that I'm the only person having problems with this device. I've tried it on several different XP systems with the same results. Works perfectly with Windows 98SE.

When you guys disable WZC, do you have a device utility that you use instead? Or.. If you select manual, do you have to go into computer management services each time and then click on start if you reboot the system? This is kind of a pain if you ask me. With WZC on manual, it doesn't seem to help any. With it disabled, I can't use the device, so..

Thanks again.

Sal