Linksys WUSB11 Not Recognized by WinXP

[msmamet]

I'm setting up a home wireless network with Linksys BEFW11S4 WAP router and Linksys WUSB11 ver 2.6 adapter.

The router installed fine and is working. I'm having problems with the adapter. I'm running Win XP Home and it simply will not recognize the new hardware. I plug it into any of my USB ports and the new hardware wizard fails to see it. I manually run the new hardware wizard, it fails to see it. In the new hardware wizard I select the device type, point it to my linksys driver disk and it fails to see any drivers.

Any ideas?

Thanks,
Matthew

 

[smah]

First, the basics. Do you have any other functioning usb devices? Your usb ports are enabled and functioning correctly?

 

[msmamet]

Yes. I have 4 USB ports and they all work properly.
To be certain, I removed my Webcam and replaced it with the wireless adapter. I know for sure that port works because my webcam was working properly.

 

[deltat]

I had the same problem with the wusb11 ver. 2.6 on both my desktop and my laptop. I have three wusb11's and they all did the same thing. I tried them on a different desktop and it loaded just fine. I think it's the USB controller so I'm going to try getting a pci usb adapter. I'll post the results. I don't, however, know what I'm going to do with my laptop seeing as how all of my pcmcia slots are full.

 

[sazebac]

I'm having the same problem. Bought one, tried to hook it up to 2 XP machines and one 2000 pro machine and none of the machines recognized the adapter. I returned it and got another one and the same thing. Have no idea what could be causing this.

 

[bcastner]

Try if appropriate to disable "Legacy" USB support in the BIOS.

Then see if the device is recognized.

In the alternative, boot the PC with the device unplugged.
right-click My Computer, Manage, Services, Services, and scroll down until you see Wireless Zero Configuration Service. Stop it. Set the default setting to disabled.
Reboot.

Use the setup instructions in your manual for a Win2k machine. This will install the client monitor.
Now use Device Manager and find the device, it should now be recognized. Right-click, Properties. Use the Configure button first, Advanced, to set SSID, Channel and WEP. Apply. Look at the protocol/client/services window now to see that everythhing you want is there. Under TCP/IP set to auto obtain its IP, click Advanced, undere the WINS uncheck LMHOSTS, check enable Netbios over TCP/IP.

Reboot.

 

[bcastner]

I want to also note that there has been a minor rash of reports of essentially non-working Version 2.6 devices in the last several weeks. Returning them for a replacement has resulted in a working device the second time, although one user reported waiting three days to make certain he had a unit from a fresh shipment. (He knew it was a new shipment because he asked for a replacement when the current stock was replaced.)

 

[maumau27]

I have Windows XP Pro, and had Linksys wireless WUSB11 adapter working without any problems. However, tonite I installed Norton Systemworks 2003 and now my wireless adpater isn't communicating with the Access Point router.

The status on the wireless device, as returned by "right mouse click" over the network connection icon shows the device to be fine as does wireless device configuration. However the on;ly sign of something is work, aside the fact that my browser can't connect out, is the "support" tab in "connection status" panel
states:

Address Type: Invalid type
IP Address: 0.0.0.0
Subnet Mask: 0.0.0.0
Default Gateway: 0.0.0.0

When really I expect

Address Type: Assigned by DHCP
IP Address : 192.168.1.145
Subnet Mask : 255.255.255.0
Default Gateway: 192.168.1.1



Sure, I've ensured that my Access Point is correctly configured, and since there was no change made at the Access Point I can't resolve it.

I've reinstalled the wireless adapter several times, with the same end result. The adpater things its good to go, and infact it does locate the correct SSID of the Access Point, yet no send & recieve occurs. On the access point router, I look at the DHCP client table, and where once I would have seen my remote wireless client being assigned an IP, I now see no clients. I have :

1) reset the Access Point
2) removed/reinstalled the wireless adapter, and configured correct SSID and WEP keys.


Why should Nortone Systemworks have impacted the device, given that there is no real connection between the two. Okay, I know its MicroSoft, o even if there wasn't a plausible connection between the Anti-Virsus and System utility toolkit (Norton SystemWorks) and wireless network, they may well have made some dependency.


Many thanks for any help

Any ideas, anyone ?

 

[bcastner]

Your Winsock stack has become corrupted.

The Norton installation may be responsible for this result, but other things can do this too. Less than up-to-date trojan scanners and registry cleaners often lead to this result.

Now the fix. Download this utility. One menu button lets you save your existing registry. Do so. A second choice is to repair your Winsock stack services. Do so. A reboot will be required.

http://members.shaw.ca/techcd/VB_Projects/VB_WinFix.exe

 

[CableInstaller]

bcastner

uh..link has changed a bit, and program was updated and compiled into a single (smaller 685k) file. Some info added in the "about" section to explain things a little better. And a zip seemed less intimidating to download for some. Took the 90% un-needed msvbvm60.dll out as well, as most systems should have it already.

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

 

[bcastner]

CableInstaller,

Thanks again.

Best.