Vista networking woes

I was sitting quietly leveling my rogue in Felwood on Saturday night, when all of a sudden WoW grinds to a halt and "Disconnected" screen pops up. Good thing I just finished that escort quest, otherwise I'd be really pissed. WoW servers do go down once in a while, so I just tried to re-connect - no luck. Hmmmm, quick Alt-Tab uncovers the problem - network icon got a yellow triangle on it. I'm on wireless connection (desktop is downstairs, router is upstairs and no desire to drag cables all the way), so I figured quick disconnect/reconnect ought to fix the problem. Yeah, right. Three attempts to reconnect/resolve issue later I gave up and went to bed (plus it was after 1 AM, so I didn't feel like thinking too much).
Next day - problem persists. Removed wireless card from the device manager, reboot - same thing. Once in a while it just refuses to authenticate, although I KNOW the key is right. Once in a while it authenticates, but still remains limited. Frustration sets in. Cris shows up and points me to the subnet mask (255.255.0.0). Tells me a horror story about how he had to reformat Vista that ran into this problem at his office. Damn, I really don't want to do it (Full WoW reinstall IS a bitch that takes forever and CDs I got are.... OLD, pre-BC). Plus I don't have any backups, so I'll need to go buy external HD or something. Argghhhh... Brand new Vista box not even two months old, half dead.
As always - Google to the rescue. After browsing few search results I start to grasp the picture. Auto IP assignment when DHCP fails is the culprit. For some reason my box failed to obtain new IP address from DHCP and got it auto assigned. And for some other reason - when you got auto assigned IP address on Vista/XP - it's next to impossible to get rid of it. Tried few things I found here and there - didn't work. Flushed all the caches I could think of in netsh. Started messing with the router - no authentication/WEP authentication/WSA authentication - no effect, except now Linux box doesn't want to get on the network. Tried static IP assignment - no dice, router shows that my box should have 169.254.x. address, although box is configured to have static 192.x.x.x address. And there is no way to change it in the router (router configuration is another story on its own, what a piece of crappy interface). Attempts to delete interface through netsh failed as well. Finally in frustration I got my old router (thank god for various pieces of equipment laying around) and set up second wireless network. Attempt to connect - same thing. It was almost midnight, so I quit for the day.

Results so far:

• One almost brand new Vista system half dead.
• One Linux Ubuntu not being able to connect to the network after switching security options and no obvious way to specify new security type (although I have an idea what might be the problem there).

From what I can tell so far - Vista "caches" network interfaces in its registry and never lets them go. Those are invisible (don't show in netsh or network list) and unaccessible. Deleting/disabling adapters doesn't have any effect - interfaces persist. I have two wireless interfaces there (my wireless card driver somehow changed GUID during driver update, so now I have Wireless Network Interface somewhere which I can't see it or access and Wireless Network Interface 2 the one that got stuck with auto assigned IP) and whole bunch of Ethernet ones (found them in the registry), but only active ones (tied to an active driver GUID) are visible.
Autoconfigured IP is somehow associated with the interface, so there are couple of things I gonna try tonight:
get rid of interfaces or force my card to change its GUID. ... or just buy new damn wireless card.

The saga continues...

Too funny

From the AFP:

"And, again, we would urge restraint on the part of the Russian government and urge them to consider the effects of their actions on the overall stability of the region," Casey said.

That's State Department deputy spokesman Tom Casey.

Rice said it is extremely important that Russia respects "the territorial integrity and sovereignty of Georgia," adding that she would raise the issue with Russian Foreign Minister Sergei Lavrov.

And that's US Secretary of State Condoleezza Rice.

One can only wonder why they weren't concerned with "stability of the region" or "territorial integrity and sovereignty" when they rushed to acknowledge independence of Kosovo. Probably because Balkans is such stable region... Wait, no, it isn't. Maybe because Kosovo has much stronger claims? No, that's not it either. Oh, I know, it's "do as I say and not what I do" foreign policy. Must be really hating Serbs, to jump into this Balkan mess... again. I'm not sure what did Serbs do to them, to piss them off that much. I really don't buy "protecting region stability". Well, I understand that Bill needed a war to get nation's mind off Zippergate, but c'mon people - there is no oil there, why US still kicks Serbs and cuddles with Albanians? After all same "terrorists" that fight in Afghanistan now were helping their muslim brother in Bosnia and Kosovo. And I'm 150% sure Serbs are not muslims. So what gives? Enemy of my enemy is my friend, even though he is my enemy elsewhere?

Of course if US didn't rush it would be Russia's turn to look silly, defending Serb territorial integrity and supporting Abkhazia in their struggle against Georgia (not the US state mind you). I say they should declare independence and Russia should acknowledge them. Hell, why not? Basques will be next, maybe be French and Dutch parts of Belgium and before you know it we'll have a tons of little city-states in Europe.

Now THAT is stability.