If you're getting a 169.* IP address then you're DHCP service is working as expected
Not entirely true... for example, at home, I use a 10. address. Most routers use a 192.168.* out of the box.
If that replies then we know it's on the software level(IE is to blame)
Or Norton Internet Security. Or IP filtering.
Other than that, your advise was pretty good.
Here are the steps that I would take, personally:
0) TURN OFF AND GET RID OF NORTON INTERNET SECURITY
1) Clear your temporary internet files in IE
2) In your Cache Size setting, if it's anything above 50, turn it down to 50. Many people have their temporary internet files storage size turned up so high that the computer spends more time sifting through old pages than actually connecting to get a page.
3) Try going to www.purple.com
4) If that doesn't work, go to a command prompt (Start --> Run --> CMD) and type ipconfig /flushdns
5) Try www.purple.com
6) If it still doesn't work, from the command prompt do a netsh winsock reset
7) reboot (you will have to after #6) --- in fact, do a complete shutdown and start back up. This will reset your wireless card. Just a simple restart doesn't always bring wireless cards out of sleep mode.
8) If you still have no joy, then it's time to dig deeper. In your command prompt, do a ping 126.96.36.199
9) If that doesn't work, double-check your wireless settings in your router, make sure DHCP is working properly, try a different wireless device to make sure it works, etc. If it DOES work, then try ping www.google.com
10) If pinging www.google.com
works, then your IP address and DNS settings are OK. If #9 works, but #10 doesn't, then you have a DHCP problem. Try opening your browser to http://188.8.131.52
If google comes up in your browser, then your browser is fine, but your DNS is broken. Check those settings.
11) If you can ping www.google.com
but it still doesn't come up in your browser, then ask yourself "How fast is 'page cannot be displayed' coming up?" If it is saying that instantly, then double check (in IE) Tools --> Internet Options --> Connections --> Lan Settings. Make sure that "Use a proxy server" is NOT checked. The only thing that SHOULD be checked there is "Automatically detect settings" (the first box)
12) Additionally, under the Tools --> Internet Options --> Connections tab, either "Never dial a connection" or "Dial whenever there is no network connection present" should be checked. If it is set to "Always dial a connection", it won't connect wirelessly.
13) Check your windows firewall. Try turning it off and see if your problem goes away.
14) If you haven't done step #0, you just spent all this time only to find that Norton Internet Security was the culprit. ;)
I do wireless support for hotels. People who call the 800 number to reach me are *usually* resolved within 5 minutes. 9 times out of 10, clearing the temporary internet files, doing an ipconfig /flushdns and making sure they are NOT running Norton's Internet Security (note: this is not the same as Norton Anti-Virus) solves the problem.
Just my 2¢
-Cole's Law: Shredded cabbage