K
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. I don't want to setup a static IP or turn off Windows
management 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. 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!!
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. I don't want to setup a static IP or turn off Windows
management 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. 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!!