Nishiki Sport, Downtube IXNS, 1950's MMB3 Russian Folding Bike, MTB
Calling all computer geeks: Full signal, can't connect wirelessly. Argh!
Nothing like spending a few days away fixing computers...
In the midst of cleaning up my Dad's 3 year old laptop with Win XP SP1 and three years worth of security updates to be installed something is stopping it from connecting wirelessly. Full signal, can't release ("No operation can be performed on Local Area Connection while it has its media disconnected") or renew ("this operation failed as no adapter is in the state permissible for this operation") or repair ("The following steps of the repair operation failed: Renewing the IP address") the IP address. Keep getting that 169.254.x.x IP address when I do a ipconfig /all.
I'm uninstalling Norton (also three years old) since when I was connecting with the external drive it kept prompting about connecting to the interwebs and I told it to eff off. I think it's mad at me. Another thought is that one of the updates did something but there were almost 30 of them and would rather not try out each one if I can avoid it.
Next steps after Norton's off (it's doing a check disk now for reasons unknown) is to try to plug in the ethernet cable from the desktop, but after that I'm pretty fresh out of ideas. Been googlin all night and morning and don't see any other possibilities.
My H just fixed our wireless with a very similar problem. Said there was a signal but could get no connection. What finally worked was simply resetting the router on the router box itself as opposed to resetting via the software. Two months of trying to fix the damn thing and this morning he finally looked a the box itself and went, "huh, wonder what would happen if i used this reset button." Wallah! I have a connection again....
It sounds like software provided by your computer manufacturer may be fighting for control for your wireless adapter with the Windows Wireless Zero Configuration Service. See if http://support.microsoft.com/kb/871122 helps
EDIT: I see the problem has been solved, so this obviously wasn't the issue. However, I have seen this occur with other machines, particularly Dell laptops.