BEFSR41 & WAP54G & WPC55AG on Windows 2000

Everything works fine except, I can not get a windows 2000 machine to
work with my new wireless gear.

My home network is set up with SpeedStream DSL modem for SBC DSL
hooked up to a BEFSR41 Linksys Router (192.168.1.1). From that router
I have 2 PC's (Server 2003 & XP Pro) and a WAP54G Linksys 802.11g
Access Point(192.168.1.10) connected. The WAP54G is connected via the
'UPLINK' port. The Router serves as a PPPoE client for the SBC yahoo,
and as a DHCP server (IP's starting at 192.168.1.200). All my 'wired'
PC's pull in IP addresses, DNS addresses, etc....fine and have no
trouble accessing the internet or each other. They can all access the
WAP54G by it's static IP. I have 2 laptops (XP Pro and 2000 Pro). They
both have the WPC55AG PC card. The XP machine works fine with either
of the cards and the 2000 machine works with neither of them. Meaning,
the XP machine pulls in an IP via DHCP and can access all local
computers along with the internet. The 2000 machine is linking with
the AP (according to the linksys software with strong/excellent
signal), but "can't access the internet". There is a fancy graphic on
their software that illustrates this, and if you've used it you know
what I mean.

On the 2000 machine I have tried manually assigning the IP/Subnet/DNS
with information for my network instead of the default DHCP set up,
but the problem continues (link with AP, not getting to the router). I
have WEP disabled. The only changes I have made to the WAP54G are:
1) the SSID
2) The channel (5 instead of 6) [at 6 the machine wouldn't even sync
with the AP]
3) "G" only signal
4) The IP address to 192.168.1.10 (from 192.168.1.245)
Again, both cards work fine on the XP laptop and both give the same
trouble on the 2000 machine. Has anybody else had a similar problem or
ideas as to what the issue may be?

(E-Mail Removed) (Tito Perez) wrote in
news:(E-Mail Removed) om:

> Everything works fine except, I can not get a windows 2000 machine to
> work with my new wireless gear.
>
> My home network is set up with SpeedStream DSL modem for SBC DSL
> hooked up to a BEFSR41 Linksys Router (192.168.1.1). From that router
> I have 2 PC's (Server 2003 & XP Pro) and a WAP54G Linksys 802.11g
> Access Point(192.168.1.10) connected. The WAP54G is connected via the
> 'UPLINK' port. The Router serves as a PPPoE client for the SBC yahoo,
> and as a DHCP server (IP's starting at 192.168.1.200). All my 'wired'
> PC's pull in IP addresses, DNS addresses, etc....fine and have no
> trouble accessing the internet or each other. They can all access the
> WAP54G by it's static IP. I have 2 laptops (XP Pro and 2000 Pro). They
> both have the WPC55AG PC card. The XP machine works fine with either
> of the cards and the 2000 machine works with neither of them. Meaning,
> the XP machine pulls in an IP via DHCP and can access all local
> computers along with the internet. The 2000 machine is linking with
> the AP (according to the linksys software with strong/excellent
> signal), but "can't access the internet". There is a fancy graphic on
> their software that illustrates this, and if you've used it you know
> what I mean.
>
> On the 2000 machine I have tried manually assigning the IP/Subnet/DNS
> with information for my network instead of the default DHCP set up,
> but the problem continues (link with AP, not getting to the router). I
> have WEP disabled. The only changes I have made to the WAP54G are:
> 1) the SSID
> 2) The channel (5 instead of 6) [at 6 the machine wouldn't even sync
> with the AP]
> 3) "G" only signal
> 4) The IP address to 192.168.1.10 (from 192.168.1.245)
> Again, both cards work fine on the XP laptop and both give the same
> trouble on the 2000 machine. Has anybody else had a similar problem or
> ideas as to what the issue may be?
>

If you let the Win 2K machine get a DHCP IP and it comes back with a
169.xxx IP and *Auto Config*, this could mean that the TCP/IP Stack may
be hosed on the machine. And even if you give a static IP for the machine
to use, the machine cannot do it.

You most likely can access the other machines on the LAN with the
machine, but you cannot access 192.168.1.1 to get to the router's Admin
Screens from the machine.

It's possible that you may have to rebuild the TCP/IP Stack on the
machine. I am not saying that is the problem, but it could be. You can
search Google on how to rebuild the TCP/IP Stack, which is delete the
Winsock and Winsock2 registry entries, uninstall everything out of the
network card's property box, and reboot the machine, which will rebuild
the TCP/IP Stack. You then reinstall everything back in the network card
property box.

HTH

Duane
--
The protection of the machine is a process and not a given!