I know there are a number of threads on this issue, MANY with easy fixes. However, I have noticed that a few people are having the same issue I am, and it does NOT have a straightforward solution. Unfortunately, these people's posts are getting lost with the other, more simple problems. Here is the deal: I upgraded my Dell e1505 to Win XP Pro SP2. Installed the software for the Dell Internal Wireless 1390 card. Couldn't connect to my wireless network (or any other). Got the "This connection has limited or no connectivity" message, along with a 169.xxx.x.x IP address (which is usually assigned when a PC can't connect to the DHCP server). Signal strength was excellent. A few times, I was able to get the computer to connect to my network, and got assigned a correct IP in the range I had specified. I did an ipconfig side-by-side with my wife's Dell laptop (which was working perfectly). Every piece of information (save the IP, of course) was EXACTLY THE SAME. Tried pinging the router with her PC, got a response with no problem. Tried it with my PC, NO RESPONSE. Connect the laptop via ethernet cable and have no problems. I have tried: - The winsock fix to clean corrupted TCP/IP protocol - The Microsoft registry patching fix (KB8804020) - Many reboots - sfc /scannow - netsh winsock recet - Assigning a static IP to my laptop and reserving it on the router - Windows update - Silly solutions like disabling TCP/IP and re-enabling it, turning off firewalls, resetting the router & cable modem, ipconfig /release then /renew, "repair" wireless connection option, turning off "notify me when connection has limited or no connectivity", Again, the DHCP server seems to work fine with my other laptop (tried rebooting it), and it even sometimes assigns this laptop a correct IP, but I still cannot get any response when pinging the router. Router is running the latest firmware. Any help is MUCH appreciated.

I would think that if you can connect with a cable and have no problems but when you go wireless ten it has to be either the wireless card or the router...reason being that if it was software related it wouldn't matter how you connected it would still be the same cause. Your wife's computer displaying everything identical (except IP) has no problem connecting but you can't even ping your own router suggests that your wireless card has taken a crap. Have you tried a different card? In The Matters Of Style, swim with the current; in matters of principle, Stand Like A Rock

When I get this on my machine(s) it means that the network ssid hasn't been typed in or has got corrupted. It is a security issue