yes... as above. To add: If the client "associates" to the WiFi router/AP, but cannot obtain an IP address ("limited or no connectivity in Windows"), then there's a mismatch in the encryption mode/key in the client and in the WiFi router.
I suggest: In router, disable encryption all together, temporarily. Then see if clients will associate and get an IP address and access the Web. If so, then we can focus on where the encryption issue is... by next enabling WEP 128 encryption on the router - not WPA. Older PCs may support only WEP128. If this works, you could leave it here. Don't leave encryption OFF of course.
You could also succeed with WEP128 then try WPA with the client - if it doesn't work, fall back to WEP.
Unless the router is in a dorm, WEP128 is good enough. WEP's encryption key on the client is a PITA. Have to enter hexadecimal digits (26 digits if WEP128) - rather than a password phrase. Some people use some clever hexadecimal such as "0D0E0A0D0B0E0E0F" (see the dead beef in that?). Extend that idea to 26 digits. Include something unique like amidst the digits.
In any case, be sure to change the SSID
Broadcast SSID (NETGEAR)
to something non-generic, like your initials or dog's name.
Using a generic like NETGEAR will cause many problems.
So neither client is prompting you to enter the security key?
Are you sure you applied/saved the security settings on the WNR2000?
Yes. I did have to manually enter the Key on both PC to get them to work.[/quote]
Unless you have a good reason, you should be using WPA2 AES security. You actually need to use this if you want to support link rates > 54 Mbps (802.11g speeds) with 802.11n clients.
I'm not going to get into a p!ssing contest about what encryption is better. The router is literally located in "the back woods" so someone breaking in is highly unlikely (closest neighbor is 1,500' away).
I did not mention it, but neither machine could connect when encryption was turned off on the router and "Connect even if network is not broadcasting" was turned off on the PC.