[bigorange310]

Wireless networking in Windows has me whipped. I'm trying to add a desktop running WinXP to an existing wireless network. The computer finds the network, says it's connected and the signal is very good, but there is "limited or no connectivity."

(Actually, that same message seems to crop up a lot).

There was a previous thread on this site, which was responded to by a moderator who suggested resetting winsock settings using the Command window. That worked for the previous poster. Didn't work for me.

When I try the "Repair" function offered, it gets as far as refreshing my IP address, spends a while, says it has a new address but it still can't connect.

Linksys WRT300N router connected to a cable modem, other computers connecting fine.

Netgear USB wireless adapter.

[Couriant]

usually i find the wep/wpa information is incorrect.

for troubleshooting purposes I would suggest disabling the security on your router so your laptop can connect without any restrictions.

[JohnWill]

Try a wired connection and see if it will connect that way. I think that Couriant is probably correct, this is usually MAC filtering or incorrect encryption keys.

[Couriant]

I had this problem today myself at work. Even though I have been using the wireless before, it found the wifi but did not get any DHCP. It was due to the distance and other factors (the building, how many walls between me and the router/wireless access point) because in other places of the building I got the DHCP.

So if you have any interference then it could be causing the lag for DHCP.