Windows Wireless Zero Config.... ARGH!

[Gillbot]

Ok, On almost every laptop i've ever used, it was easiest to Disable the Windows Wireless Zero Config by going to Start->Run and typing Services.msc, locating Windows Wireless Zero Config, stopping the service and set it to disabled. Reboot then use whatever Wireless utility came with your wireless adapter to configure and connect without issues.

Well, on my home desktop this doesn't seem to work well. I have been having issues with my desktop losing connectivity randomly and I thought it was the Windows Wireless Zero Config and the Linksys Wireless utility fighting for control over the wireless adapter. Per my usual routine I went to Start->Run and typed Services.msc, located the Windows Wireless Zero Config, stopped the service and set it to disabled. After a reboot, the Linksys wireless utility then proceeded to connect then disconnect itself from my AP repeatedly about 2 times per second until I went back in and restarted the Windows Wireless Zero Config. It seems as though the Linksys util can't keep the connection alive or something because as soon as it connects, it disconnects itself then repeats over and over.

However, If I let windows configure the connection over the Linksys utility, the Linksys utility randomly tries to take over control and kicks me off as well. I can't seem to get just a driver for the USB Wireless adapter so it forces the Linksys utility on there. What can I do!!! It's getting annoying to have to reboot every 10 minutes or unplug and replug in the wireless adapter all the time.

 

[spidey07]

Have you checked your network control panel and deselected the "let windows manage wireless"?

Also try reinstalling the utility, sometimes no matter what you do windows will "fight" to control wireless. It sounds like you're running into this classic problem of them "fighting" each other.

 

[Gillbot]

When the utility is installed, it automatically "unchecks" the "let windows control wireless" blah blah. I know they are fighting each other but that is USUALLY solved by disabling the windows wireless zero config. Unfortunately when I turn that off the Linksys utility doesn't want to connect properly. I've reinstalled the utility thrice so far, I'm about to give up and run cable across the length of the room!

 

[Markbnj]

What's the issue you've seen with WWZC? I used to disable it, but these days I don't even install config utilities from the adapter OEM if I can avoid it. The only problem I have had was its hunting for stronger networks when the signal from mine wasn't solid, and that was solved by unchecking a property in the config for the wireless connection, something like "Automatically connect to non-preferred networks".

 

[JackMDS]

I am not familiar with this Linsys specific utility.

However try to look at the Startup folder (or use this program, http://www.mlin.net/StartupCPL.shtml ) it might be that you can prevent the Utility to start without touching the Drivers,

Alternatively this inexpensive card is very Good, http://www.newegg.com/Product/...x?Item=N82E16833315041

 

[Gillbot]

Originally posted by: Markbnj
What's the issue you've seen with WWZC? I used to disable it, but these days I don't even install config utilities from the adapter OEM if I can avoid it. The only problem I have had was its hunting for stronger networks when the signal from mine wasn't solid, and that was solved by unchecking a property in the config for the wireless connection, something like "Automatically connect to non-preferred networks".

The issue with WWZC is that it "battles" with the OEM utility for control of the wireless card. It then creates lackluster performance since many OEM's don't allow you to use a plain driver without their utility.

I'm trying to just let windows control it but this linksys utility seems to be packaged with the driver so I can't have one without the other.

 

[Gillbot]

Jack, I was looking at that card initially. I may have to grab one and try it over this USB Linksys and see if I get better results.

 

[JackMDS]

You probably would get better result fron the PCI.

I do not know which US you have right Now.

In the past there was No difference between the USB and PCI, there were basically the same radio in a different casing/interface.

In the last few years the Radio chipsets for USB are Not the same as the PCI. Most of the USB Wireless cards were reduced in size and are all plastic, thus many have Heat dissipation problems that is reducing their efficiency.

However Wireless is as "Tricky" as the Social Forums , so YMMV.

 

[Gillbot]

I just don't know if buying the PCI will be worth it as this is a temporary solution until I find my new home. After that i'm going back to wired for sure!!

 

[Markbnj]

The issue with WWZC is that it "battles" with the OEM utility for control of the wireless card. It then creates lackluster performance since many OEM's don't allow you to use a plain driver without their utility.

Do most OEMs require you to install both? I don't remember whether I was able to skip the utility on the last one I did (which was probably 2 years ago), but it plays nice with WWZC. If you have the "Let Windows manage my wireless connection" (or whatever) checkbox enable, and try to start the utility up it redirects to the Windows wireless connection property dialog. Whether it is still doing something in the background I don't know, but the machine has a stable, solid connection. I think it was an SMC or Belkin.

 

[JackMDS]

Actually OEM does not combine the Drivers and the Utility,

It is the Brand name that does it as their way to "World Dominance". They do not writ the core OEM drivers they take them form the chipset manufacture and beef it up with their Branding.

This practice can provide away to may bypass these issue.

The manufactures of the Card?s chipset usually have OEM drivers on their support site.

One can try to find what is the chipset used in the card and then log to the chipset?s manufacturer site and look of the generic drivers.
This page is an example for the above, http://www.ezlan.net/wlan64.html

 

[ChAoTiCpInOy]

Just stop the Linksys Utility from running and you'll be fine. I had the same problem at first then I shut down the Linksys utility, then no problems.

 

[Gillbot]

Originally posted by: ChAoTiCpInOy
Just stop the Linksys Utility from running and you'll be fine. I had the same problem at first then I shut down the Linksys utility, then no problems.

The problem is, I cannot disable the linksys utility. I've tried! I also tried uninstalling and just finding a set of drivers but that has come up empty as all the drivers i've found are tied to the utility.

 

[Gillbot]

Originally posted by: JackMDS
Actually OEM does not combine the Drivers and the Utility,

It is the Brand name that does it as their way to "World Dominance". They do not writ the core OEM drivers they take them form the chipset manufacture and beef it up with their Branding.

This practice can provide away to may bypass these issue.

The manufactures of the Card?s chipset usually have OEM drivers on their support site.

One can try to find what is the chipset used in the card and then log to the chipset?s manufacturer site and look of the generic drivers.
This page is an example for the above, http://www.ezlan.net/wlan64.html

AWESOME!

As an Example: The Linksys WUSB54G v4 is based on the Ralink chipset, while the previous versions are not. There is No way to know when you buy one which version is in the Box.

That's the EXACT model I have!! I will have to try the Ralink drivers and see of that fixes the problems!!!

 

[JackBurton]

Fvck Linksys' wireless adapters. Why Linksys freakin' just can't let you use WZC, I have no idea. Every time I've installed this adapter on someone's machine, there was always some problem, driver issues, freakin' RIDICULOUSLY high CPU spikes due to the adapter trying to connect to an AP that's not there, and so on. My solution, just get one of these or one of these set to "client mode" and be done with it. No drivers to install, and your machine thinks it's using a simple wired connection. You can also EASILY move it to whatever machine you'd like. No driver installations or new configuration. Just unplug it from one, and plug it into another. Simple, easy.

 

[Markbnj]

Yeah, I think if I found that the card required me to use their utilities to manage the connection I would return it. As with most things it's best just to let MS have their way .

 

[JackMDS]

Originally posted by: MarkbnjAs with most things it's best just to let MS have their way .

It has nothing to do with Microsoft.

Microsoft has a product call Windows. If Linksys does not bother to make sure that their product is compatible with Windows OS, they can write their own OS.

 

[Markbnj]

Originally posted by: JackMDS

Originally posted by: MarkbnjAs with most things it's best just to let MS have their way .

It has nothing to do with Microsoft.

Microsoft has a product call Windows. If Linksys does not bother to make sure that their product is compatible with Windows OS, they can write their own OS.

Well, now we're into semantics . Used to be all adapters came with a proprietary utility. MS decided it would benefit users to have one centralized facility. I was just being tongue-in-cheek with regard to that decision.

 

[Gillbot]

I used to have a WAP54G and I sold it. I knew I should have kept it!!

I'm going to tough it out with this USB adapter since it seems to be playing nice here lately. It's only 1.5 more months until I get my new house and I run all wired through the house anyway. No point in spending more $ than I have to. Unless this thing goes into fits again.....

 

[JackMDS]

Mark it is Not semantic it is a matter of Not Interfering with the ?Temporal Rift?.
The chipset drivers are compatible with Windows WZC and when they were written WZC was already part of Windows XP.

Linksys decide to integrate the Utility with the drivers. Most vendors do not do it, some do. There is No technical advantage for this integration, and obviously, Linksys did not bother to test it thoroughly.

 

[Markbnj]

Originally posted by: JackMDS
Mark it is Not semantic it is a matter of Not Interfering with the ?Temporal Rift?.
The chipset drivers are compatible with Windows WZC and when they were written WZC was already part of Windows XP.

Linksys decide to integrate the Utility with the drivers. Most vendors do not do it, some do. There is No technical advantage for this integration, and obviously, Linksys did not bother to test it thoroughly.

Agreed on the ultimate FAIL content in that decision.