|Well, if you see a 169.254 address, that kind of invalidates my theory...169.254 means your computer was never able to reach the router - it normally indicates a problem from Layer2 downwards (so, NIC drivers, cabling, or the router itself)|
Can you try to verify connectivity here, from your problem computer, give it the 192.168.0.2 address, as I'd mentioned earlier, then from a Command Prompt window (CMD), try this:
Do you get a REPLY FROM 192.168.0.1?
If so, then it's reaching the netgear
Do you get a REPLY? If so, you're reaching the wireless modem (Everything should work if you can get this step working)
Lastly - how is your network physically wired exactly? Where is the Uplink to the internet?
I assume it's something like:
[wired computer]---[netgear]---[wireless router]---[cable modem]---(INTERNET) is that right?
Also on the netgear - is the uplink (to the wireless) connected via the LAN or the WAN port?? (Try moving it to the LAN port)
Try to post back w/ the answers to the above - if you can't reach 192.168.0.1 from your problem computer, then it's Layer 2 or 1 related from the host to the netgear (check the link lights on the netgear, try a differnet computer on the netgear, replace the cabling, reinstall your drivers, replace the nic, replace the netgear router)
But, if you can HIT 192.168.0.1, but not 192.168.1.1, then the problem lies between the netgear and the wireless router link.