How is your home network configured? Have you assigned static IPs or do you use a local DHCP range of addresses?
a 169.x.x.x ip indicates that your NIC has not grabbed a valid IP... so if you use static IPs make sure the connection is set with the correct static IP. Generally, if you are set with static IPs, and you end up with a 169.x.x.x it means your connection has failed before it reaches the CPU (bad patch cable/router port/router/cable/modem in that order)
However, if you use DHCP, a 169.x.x.x would normally indicate a failure for the machine to obtain a valid IP from the DHCP service. Since your other comp is working fine, the router is most likely not the problem if this is the case.
Since your IP is now 0.0.0.0, check out this article: http://support.microsoft.com/kb/822123
1. DHCP Service not running.
2. Duplicate IP address on the network.
3. Bad NIC card drivers.
4. Defective NIC hardware.
1. Check Control Panel, Administrative Tools, Services. The DHCP Client service should be Started and its Startup Type should be Automatic.
2. Turn off ALL of the computers and other network connected devices, restart (power cycle) the router, then restart all the computers and other network devices.
3. Check for upgraded drivers and/or reload the Network drivers.
4. Replace the Network Interface Card.
You can also try resetting your protocol stacks.
Go Start--->Run then type CMD and press enter. Type the following commands (in bold) into the Dos prompt that opens.
Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log
Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog
Give all that a shot. none of it should have any bad consequences if it doesn't fix the problem. If all else fails, try swapping out your known working computer's NIC with the bad one.. if it works, buy a new NIC