Hi and thanks for the replies,
something strange is going on here. You are getting "destination host unreachable" yet it's saying it has received 4 packets. Do you have any static routes for the 169.xxx.xxx.xxx addresses going through another router/server anything at all?
Nope, the computer is only connected to the router. Nothing else that could interfear.
First step, disconnect all ethernet cords from the dir-655 other than the one leading to the computer having the problem and make sure this ethernet cord is NOT in the "internet" (gray) port! This will eliminate possible issues if it's infact the router or your computer and not another device. Do a hard reset of the router again (because I dont know what you've done to it). And make sure you hold in that button until all lights go off then come back on again.
Like before - only the cable between the computer and router is connected. I tried holding the reset down for almost one minute, but it does not respond like you describe it should. Power and the connected LAN port just stays on. According to the manual the Status led should blink when router is ready. It does not light at all.
Second step:
Disable all firewalls! I can't tell you how many calls a day @ tech support I received where issues like this was caused by a firewall denying ALL traffic.
Then disable/enable your connection or "repair" or ipconfig /release ipconfig /renew. You choose. But do an ipconfig and make sure you have a valid ip address and make sure it shows the ip address of the gateway. Then see if you can get to the default gateway in the internet browser.
If not then try giving your adapter a static ip address like 192.168.0.2 for example, and see if you can access the config page.
Try uninstalling the drivers and reinstalling them.
check connection as before.
Tried all that. Letting Vista repair the connection. Disable firewall. Try to give the computer a static IP.
Luckily I have a spare router (not as advanced as the DIR and no wifi) and plugging that in gave me immediately Internet access. This problem started from a working setup running for 2 months. I did not add any new devices recently.