XP Home and Wireless Access Point - Repost - Help

[Karl Burrows]

One of my clients decided to go out and buy a laptop to use in a remote site
and we are having a terrible time trying to get him connected to a wireless
access point in a very small LAN.

Here's the setup:

NetGear Wireless Access Point - configured to obtain IP automatically from
DSL router. Wireless access is WEP 128-bit encrypted, shared key.

Linksys DSL Router - running DHCP on P to P network with about 4 computers
using 192.168.2.xxx subnet.

I have another computer that we installed in our sales center that is
running off this wireless AP (it has static IP and NetGear PCI wireless card
with "Let Windows manage wireless connections" turned off) and connects with
no problem (using XP Pro). I don't want to setup a static IP or turn off
Windows
management on his laptop or he loses network sniffing elsewhere.

It sees the wireless network and I can enter the shared key and I am told
that I have limited connectivity although I am connected at full speed, but
can not ping anything on the LAN or get on the Internet. If I do assign a
static IP, I am fully registered in the network with no connection issues
noted, but still can not see another other segment/hop. Seems like it can
get to the AP, but not the LAN or Internet. I have double checked the
Linksys settings
and there is nothing unusual in the setup.

I have had tons of problems with XP Home and networks. I don't know what he
tried to do to connect before. I did notice he tried to use the network
wizard and even created VPN connections thinking that was the wireless
connection. I know using the home networking wizard can create all kinds of
problems if it isn't done right or if already done on another computer in
the network (although, all have XP Pro in the LAN). He can connect fine at
home, but as to be expected, no security on the wireless access.

I am worried the TCP/IP stack is corrupt and am hoping someone has a
suggestion on how to troubleshoot without taking the whole network down and
reconfiguring the WEP keys, etc.

Thanks!!

 

[DJ Borell]

One of my clients decided to go out and buy a laptop to use in a remote
site
and we are having a terrible time trying to get him connected to a
wireless
access point in a very small LAN.

No, your TCP/IP stack is not corrupt or you wouldn't be accessing with a
static IP.

This is a DHCP issue. You didn't state which Netgear AP you've got, but my
guess is that it is not forwarding the DHCP request from wireless clients to
the Linksys router. You may have an option to set up a "Relay Agent" on the
AP (it may be called something else.) Best place to check would be the
manual for your AP. My guess is you'll find this issue addressed in the
FAQ.

 

[Karl Burrows]

That makes sense, but even if I setup a static, why won't it connect outside
the AP (showing connected)? It is a NetGear WG602NA 54Mbps Access Point.
The other computer has a static IP, but does have a NetGear wireless PCI
card, so it may be negotiating the connection.

I may just reset the AP and see if I can get the settings right.

One of my clients decided to go out and buy a laptop to use in a remote
site
and we are having a terrible time trying to get him connected to a
wireless
access point in a very small LAN.

No, your TCP/IP stack is not corrupt or you wouldn't be accessing with a
static IP.

This is a DHCP issue. You didn't state which Netgear AP you've got, but my
guess is that it is not forwarding the DHCP request from wireless clients to
the Linksys router. You may have an option to set up a "Relay Agent" on the
AP (it may be called something else.) Best place to check would be the
manual for your AP. My guess is you'll find this issue addressed in the
FAQ.

 

[DJ Borell]

That makes sense, but even if I setup a static, why won't it connect
outside
the AP (showing connected)? It is a NetGear WG602NA 54Mbps Access Point.
The other computer has a static IP, but does have a NetGear wireless PCI
card, so it may be negotiating the connection.

I may just reset the AP and see if I can get the settings right.

Ok...having looked at the manual, it does not appear that this AP has an
explicit setting for DHCP forwarding. I would surmise that ensuring that
the AP receives it's IP config dynamically will automatically cause it to
forward requests (as it does not have a built-in DHCP server, it should be
programmed to do so). Ensuring these options are correct should resolve
your issue.

As far as connecting past the AP, make sure the DHCP options for the AP
(particularly the gateway address, which should be the address of the
router) are correct. Further, each client needs the router as the gateway
address as well. This *should* be applied automatically if the DHCP server
on the router is correctly installed/setup.

Resetting the AP will actually *not* help you as the default settings for
the AP IP address is set to *not* default to DHCP (it uses a static private
address). This is unlikely to be on the same IP/Subnet mask as your
network, so no wireless clients would not be able to connect (exactly what
you have now.)

 

[Karl Burrows]

Sounds like the problem. I'll check it out in the next day or so and let
you know what I find. Thanks for the help!

That makes sense, but even if I setup a static, why won't it connect
outside
the AP (showing connected)? It is a NetGear WG602NA 54Mbps Access Point.
The other computer has a static IP, but does have a NetGear wireless PCI
card, so it may be negotiating the connection.

I may just reset the AP and see if I can get the settings right.

Ok...having looked at the manual, it does not appear that this AP has an
explicit setting for DHCP forwarding. I would surmise that ensuring that
the AP receives it's IP config dynamically will automatically cause it to
forward requests (as it does not have a built-in DHCP server, it should be
programmed to do so). Ensuring these options are correct should resolve
your issue.

As far as connecting past the AP, make sure the DHCP options for the AP
(particularly the gateway address, which should be the address of the
router) are correct. Further, each client needs the router as the gateway
address as well. This *should* be applied automatically if the DHCP server
on the router is correctly installed/setup.

Resetting the AP will actually *not* help you as the default settings for
the AP IP address is set to *not* default to DHCP (it uses a static private
address). This is unlikely to be on the same IP/Subnet mask as your
network, so no wireless clients would not be able to connect (exactly what
you have now.)

 

[DJ Borell]

Sounds like the problem. I'll check it out in the next day or so and let
you know what I find. Thanks for the help!

Glad to help.

 

[DJ Borell]

Sounds like the problem. I'll check it out in the next day or so and let
you know what I find. Thanks for the help!

BTW - On a (mostly) related note, I noticed that your AP does support
WPA-PSK. If your clients are compatible, you should consider running this
as your security base as it is more secure than WEP.