IP Renew problem - example of Microsoft Incompetence

[aregal]

One of the PCs on my home network suddenly starting picking up one of those crazy "169.xxx.xxx.xxx" IP addresses, even though my router address starts with "192.xxx.xxx.xxx".

I tried all the usual remedies on XP, including recreating the connection, running the network-wizard, replacing the NIC. Nothing worked.

Started checking forums and found the Microsoft Support solution of deleting WINSOCK entries in the Registry and resetting TCP/IP using "netsh". Of course, nothing.

I don't like running utilities that supposedly "fix" the registry but having spent hours and hours    on the problem I finally downloaded WINSOCKFIX. Hey presto it worked! (I'm sending them a contribution).

Question: why couldn't the incompetent f**kers in Redmond (in my opinion) write such a utility? Of course, a better question is what kind of morons design an OS that allows it's core TCP/IP files to be overwritten?

Thankyou "Microsuck" for having this forum. I love you!

[Refalm]

Have you tried to insert your UTP cable correctly?  
And btw, no one is able to hack you if you show your internal network addresses. If you show us the rest of 169.*, it will be very helpful.

Welcome to our forum anyway, but please don't ask anymore questions about Windows, because we actually want to to switch to something like Linux ( ) or Mac OS X ( )  

[Werre]

The 169.-address means winshit's dhcp client was unable to contact the dhcp server.

[Refalm]

quote:Werre: The 169.-address means winshit's dhcp client was unable to contact the dhcp server.

It could also mean that there isn't a cable connected  

[WMD]

Know what's funny?  The actual 169 IP block (the 169.139 actually) is owned by my school district.