• July 16, 2025, 05:09:29 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Think my router died....  (Read 6367 times)

THXTEX

  • Level 1 Member
  • *
  • Posts: 3
Think my router died....
« on: April 11, 2009, 04:54:39 AM »

Hi,

My DIR-655 has been running for a month now without any problems with the latest beta. This morning I suddenly could not access the internet. Everything else looked OK (other devices).

I have now disconnected the router from the internet and made a reset. The router is only connected with a computer using a cable, but i can not access the adminpage (192.168.0.1) - it's like it does not exist. Vista shows that cable is connected and the router also displays everything as being OK, but the computers IP is not 192.168.x.x - which it should be if it was given by the routers DHCP. (Have tried repair config)

Any suggestions?
« Last Edit: April 11, 2009, 04:57:38 AM by THXTEX »
Logged

lotacus

  • Level 4 Member
  • ****
  • Posts: 450
Re: Think my router died....
« Reply #1 on: April 11, 2009, 10:44:55 AM »

what IP address does it have?
Logged

THXTEX

  • Level 1 Member
  • *
  • Posts: 3
Re: Think my router died....
« Reply #2 on: April 11, 2009, 01:34:19 PM »

169.254.85.149 - Probably defined by Vista.

Here the router is only connected to the router by cable - nothing else is plugged in. I have tried several cables and have switched off power in 10 sec. before. But as you can see the router is not found.
Code: [Select]
C:\Users\XXXXXX>ping 192.168.0.1

Pinger 192.168.0.1 med 32 byte data:
Svar fra 169.254.85.149: Modtagervært ikke tilgængelig.
Svar fra 169.254.85.149: Modtagervært ikke tilgængelig.
Svar fra 169.254.85.149: Modtagervært ikke tilgængelig.
Svar fra 169.254.85.149: Modtagervært ikke tilgængelig.

Ping-statistikker for 192.168.0.1:
    Pakker: Sendt = 4, modtaget = 4, tabt = 0 (0% tab),

I managed to get access to the adminpage after the router had been turned off for half an hour and I had done a reset on the router by pressing reset for 30 sec. I clicked around in the GUI and turned off the graphical code on loginscreen and reset the router. After that I was not able to enter the admin screen again.
Logged

Reinvented

  • Level 4 Member
  • ****
  • Posts: 437
Re: Think my router died....
« Reply #3 on: April 11, 2009, 01:39:58 PM »

Yeah...that 169 address is a private address range meaning that it's not connecting properly.

So...reset again to factory defaults, and try again.
Logged

lotacus

  • Level 4 Member
  • ****
  • Posts: 450
Re: Think my router died....
« Reply #4 on: April 11, 2009, 03:40:22 PM »

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?

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.

Second step:

Disable all firewalls! I can't tell you how many calls a day @ tech support I recieved 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.

If not then

Try uninstalling the drivers and reinstalling them.
check connection as before.






« Last Edit: April 11, 2009, 04:00:12 PM by lotacus »
Logged

THXTEX

  • Level 1 Member
  • *
  • Posts: 3
Re: Think my router died....
« Reply #5 on: April 11, 2009, 05:00:54 PM »

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.
Logged