Windows 2000 computer refuses to talk to my wireless network

My router is a Linksys BEFW11S4. I'm trying to get a WUSB11 Wireless USB
Network Adapter on a Windows 2000 machine to talk to the network.

I tested it with my Windows XP laptop and it connected without a hitch. I'm
convinced that a big part of this is the fact that XP has wireless
connectivity built in and that Linksys' WLAN Monitor software is part of why
this won't work on my Win2K machine.

I know this computer can see the router because the Linksys software
correctly shows the router's MAC address, SSID, channel, etc. and lists the
status as "Connected".

I've tried DHCP, but even though the router shows that it assigns the
computer an IP within the DHCP range (192.168.1.106), the computer thinks
it's getting something like 169.254.145.210. What actually happens is that
when I first log on the computer actually WILL have the 192.168.1.106
address, but within minutes will switch to the 169 address.

Then I tried setting a static IP (192.168.1.50) and manually setting the
gateway and DNS servers. Still no luck. I can't even ping the router
(transmit failed, error code 65).

I'm at a loss. Your suggestions are appreciated. Thank you.

For some unknown reason, the Linksys WUSB11 is one of the most finicky Wi-Fi
devices ever made! Don't get me wrong, I like, and use, all Linksys
networking gear, but that particular device has been the topic of many
frustrated post in the newsgroups. Do yourself a favor...get rid of it, and
use anything else!

Bill Crocker


"Duc" <(E-Mail Removed)> wrote in message
news:a4Ddb.12010$(E-Mail Removed)...
> My router is a Linksys BEFW11S4. I'm trying to get a WUSB11 Wireless USB
> Network Adapter on a Windows 2000 machine to talk to the network.
>
> I tested it with my Windows XP laptop and it connected without a hitch.
I'm
> convinced that a big part of this is the fact that XP has wireless
> connectivity built in and that Linksys' WLAN Monitor software is part of
why
> this won't work on my Win2K machine.
>
> I know this computer can see the router because the Linksys software
> correctly shows the router's MAC address, SSID, channel, etc. and lists
the
> status as "Connected".
>
> I've tried DHCP, but even though the router shows that it assigns the
> computer an IP within the DHCP range (192.168.1.106), the computer thinks
> it's getting something like 169.254.145.210. What actually happens is that
> when I first log on the computer actually WILL have the 192.168.1.106
> address, but within minutes will switch to the 169 address.
>
> Then I tried setting a static IP (192.168.1.50) and manually setting the
> gateway and DNS servers. Still no luck. I can't even ping the router
> (transmit failed, error code 65).
>
> I'm at a loss. Your suggestions are appreciated. Thank you.
>
>

"Duc" <(E-Mail Removed)> wrote in
news:a4Ddb.12010$(E-Mail Removed):

> My router is a Linksys BEFW11S4. I'm trying to get a WUSB11 Wireless
> USB Network Adapter on a Windows 2000 machine to talk to the network.
>
> I tested it with my Windows XP laptop and it connected without a
> hitch. I'm convinced that a big part of this is the fact that XP has
> wireless connectivity built in and that Linksys' WLAN Monitor software
> is part of why this won't work on my Win2K machine.

That has nothing to do with the problem.

>
> I know this computer can see the router because the Linksys software
> correctly shows the router's MAC address, SSID, channel, etc. and
> lists the status as "Connected".
>
> I've tried DHCP, but even though the router shows that it assigns the
> computer an IP within the DHCP range (192.168.1.106), the computer
> thinks it's getting something like 169.254.145.210. What actually
> happens is that when I first log on the computer actually WILL have
> the 192.168.1.106 address, but within minutes will switch to the 169
> address.

The 169.xxx IP that the machine is getting is a MS defualt IP being
assigned, because the machine cannot get a vaild IP from the router.

This may be due to equipment defect. But most likely, it's due to the
TCP/IP Stack on the computer is hosed and needs to be rebuilt.

>
> Then I tried setting a static IP (192.168.1.50) and manually setting
> the gateway and DNS servers. Still no luck. I can't even ping the
> router (transmit failed, error code 65).
>
> I'm at a loss. Your suggestions are appreciated. Thank you.
>
>
>

To rebuilt the stack:

1) Use Regedit in the Start\Run Box
2) HKEY_Local_Machine\System\CurrentControlSet\Servic es
3) delete the Winsock and Winsock2 entries
4) NIC's Properties Box delete everything out of the box.
5) Reboot the machine which will rebuild the stack
6) put everything back in the NIC's Properties Box

Nine timws out of ten that corrects the problem.

You may also run into a problem of getting wired and wireless machines to
talk to each other with WEP enabled, but that's another fix if that
happens.

HTH

Duane

Thanks very much for the help. Didn't seem to work for me, though. All
symptoms of the problem still exist.

> To rebuilt the stack:
>
> 1) Use Regedit in the Start\Run Box
> 2) HKEY_Local_Machine\System\CurrentControlSet\Servic es
> 3) delete the Winsock and Winsock2 entries
> 4) NIC's Properties Box delete everything out of the box.
> 5) Reboot the machine which will rebuild the stack
> 6) put everything back in the NIC's Properties Box
>
> Nine timws out of ten that corrects the problem.
>
> You may also run into a problem of getting wired and wireless machines to
> talk to each other with WEP enabled, but that's another fix if that
> happens.
>
> HTH
>
> Duane

"Duc" <(E-Mail Removed)> wrote in
newsYEdb.12048$(E-Mail Removed):

> Thanks very much for the help. Didn't seem to work for me, though. All
> symptoms of the problem still exist.
>
>> To rebuilt the stack:
>>
>> 1) Use Regedit in the Start\Run Box
>> 2) HKEY_Local_Machine\System\CurrentControlSet\Servic es
>> 3) delete the Winsock and Winsock2 entries
>> 4) NIC's Properties Box delete everything out of the box.
>> 5) Reboot the machine which will rebuild the stack
>> 6) put everything back in the NIC's Properties Box
>>
>> Nine timws out of ten that corrects the problem.
>>
>> You may also run into a problem of getting wired and wireless
>> machines to talk to each other with WEP enabled, but that's another
>> fix if that happens.
>>
>> HTH
>>
>> Duane
>
>
>

Then it may be as the other poster has stated. That the card is defective
or buggy and the machine cannot get an IP from the router, because the
card is not working properly. Take the card back and get another one.

Duane

On Sun, 28 Sep 2003 15:25:58 GMT, Duc spoketh

>My router is a Linksys BEFW11S4. I'm trying to get a WUSB11 Wireless USB
>Network Adapter on a Windows 2000 machine to talk to the network.
>
>I tested it with my Windows XP laptop and it connected without a hitch. I'm
>convinced that a big part of this is the fact that XP has wireless
>connectivity built in and that Linksys' WLAN Monitor software is part of why
>this won't work on my Win2K machine.
>
>I know this computer can see the router because the Linksys software
>correctly shows the router's MAC address, SSID, channel, etc. and lists the
>status as "Connected".
>
>I've tried DHCP, but even though the router shows that it assigns the
>computer an IP within the DHCP range (192.168.1.106), the computer thinks
>it's getting something like 169.254.145.210. What actually happens is that
>when I first log on the computer actually WILL have the 192.168.1.106
>address, but within minutes will switch to the 169 address.
>
>Then I tried setting a static IP (192.168.1.50) and manually setting the
>gateway and DNS servers. Still no luck. I can't even ping the router
>(transmit failed, error code 65).
>
>I'm at a loss. Your suggestions are appreciated. Thank you.
>


If you're using WEP (and you should), try to give the W2K machine a
static IP address...


Lars M. Hansen
www.hansenonline.net

> If you're using WEP (and you should), try to give the W2K machine a
> static IP address...

I do use WEP and I did try a static IP.

I'm on the phone with a friend who has a very similar problem to mine. Is
there an issue with using Windows 2000 to connect to wireless networks? Her
card is a PCI Netgear MA311.

Now you'll help 2 of us if you can figure something out. Thanks again to all
who have helped.

On Sun, 28 Sep 2003 20:00:57 GMT, Duc spoketh

>> If you're using WEP (and you should), try to give the W2K machine a
>> static IP address...
>
>I do use WEP and I did try a static IP.
>
>I'm on the phone with a friend who has a very similar problem to mine. Is
>there an issue with using Windows 2000 to connect to wireless networks? Her
>card is a PCI Netgear MA311.
>
>Now you'll help 2 of us if you can figure something out. Thanks again to all
>who have helped.
>

I'm on a W2K laptop connected wirelessly right now. There are no general
issues with wireless and Windows 2000.

Trouble-shooting steps:

- Double-check your WEP keys to ensure that they are in fact identical.
- Double-check your MAC addresses to ensure that they are correct.
- Double-check your SSIDt to ensure that they are identical.
- Disable WEP to check if you can connect without it.
- Update the drivers for the network adapter.


Lars M. Hansen
www.hansenonline.net

"Duc" <(E-Mail Removed)> wrote in
news:Z5Hdb.10122$(E-Mail Removed):

>> If you're using WEP (and you should), try to give the W2K machine a
>> static IP address...
>
> I do use WEP and I did try a static IP.
>
> I'm on the phone with a friend who has a very similar problem to mine.
> Is there an issue with using Windows 2000 to connect to wireless
> networks? Her card is a PCI Netgear MA311.
>
> Now you'll help 2 of us if you can figure something out. Thanks again
> to all who have helped.
>
>

I can only speak on the problem I had in getting wired and wireless
machines to communicate using WEP on 11S4 V1 router. I had to switch to
NWlink NetBIOS protocol on the machines.

Duane

Get IPCFG.EXE and see if you can renew the IP. Most likely it will tell you
it can't find the DHCP server. Give it a while and try again. Also try a
fixed IP and see what ipcfg.exe shows. How is the signal strength? Are you
certain the channels are the same on both the linksys and the Win2K comp.

"Duc" <(E-Mail Removed)> wrote in message
news:a4Ddb.12010$(E-Mail Removed)...
> My router is a Linksys BEFW11S4. I'm trying to get a WUSB11 Wireless USB
> Network Adapter on a Windows 2000 machine to talk to the network.
>
> I tested it with my Windows XP laptop and it connected without a hitch.
I'm
> convinced that a big part of this is the fact that XP has wireless
> connectivity built in and that Linksys' WLAN Monitor software is part of
why
> this won't work on my Win2K machine.
>
> I know this computer can see the router because the Linksys software
> correctly shows the router's MAC address, SSID, channel, etc. and lists
the
> status as "Connected".
>
> I've tried DHCP, but even though the router shows that it assigns the
> computer an IP within the DHCP range (192.168.1.106), the computer thinks
> it's getting something like 169.254.145.210. What actually happens is that
> when I first log on the computer actually WILL have the 192.168.1.106
> address, but within minutes will switch to the 169 address.
>
> Then I tried setting a static IP (192.168.1.50) and manually setting the
> gateway and DNS servers. Still no luck. I can't even ping the router
> (transmit failed, error code 65).
>
> I'm at a loss. Your suggestions are appreciated. Thank you.
>
>