D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: Andacanavar on July 21, 2009, 09:50:43 PM
-
I have a DIR-615 that is not responding to hard resets. It was working fine for about a week and then stopped handing out IP's to wireless clients. I attempted a powercycle and when the router came back up the wireless light was no longer on and it was no longer handing out IP's to ethernet clients. The power light is solid, internet light lights up when connected to my modem and flashes intermittently, and the ethernet lights light up in response to connecting clients. I have attempted to hard reset the router to no avail. I also tried statically assigning 192.168.0.120 to my NIC to see if I could access the router config but that doesn't work either. It's almost as if the default ip address and range for the LAN on my router have changed and DHCP was turned off. Anyone else have this issue? Anyone been able to fix this? It is hardware version A1 Firmware version 1.10.
-
When you reset the router did you do it with the power on and hold the button down for at least 10 seconds? Also wait about 30 seconds before you try to connect to the status page after the reset.
-
I did have the power on while attempting to reset it. I tried several times, all attempts with the power on and holding down the reset button for varying lengths of time. First for 10 seconds and then kept increasing the amount of time by 10 seconds up until 1 minute. I have also waited several minutes before attempting to access the status page. Doesn't seem to make a difference. The router never even flashes to indicate that a reset has even taken place.
-
How hard are you pushing on the button. I have a DI-704P and I have to push fairly hard to get it to reset. It's hard to tell if the button is actually moving when I push it. On the other hand my DIR-655 only requires a light touch to reset it. ???
-
I can actually feel the button depress when I am resetting it. It's also not showing up in my arp table when I statically assign my ip to 192.168.0.120. Any other ideas? Thanks in advance.
-
Sounds like it has died. Is still under warrenty?
-
That's what I was thinking. Oh well. It is not, sadly, under warranty. I picked it up from a garage sale for $15 and it only worked for about a week. Oh well. Thanks again for the suggestions.
-
Perhaps a solution yet?
I've had a similar/identical problem. I used the reset button, I turned off the power and I used a toothpick in the hard reset switch (the little hole on the far right at the back. No effect.
I did it a couple of times more. No reaction. I waited an hour or so, forgot about it and thought I'd test it once more just to be sure and: hey presto! contact at http://192.168.0.1 from the browser
curious thing though: it seems to still have retained my old password and username instead of resetting it.
I've not been able to login withthe factory "admin" as username and a blank password
-
I had that with a 635 once, just couldn't load any firmware, it found its way to a bin!
-
I think I got mine half a year or a year ago, and now it did the same thing this guy is saying. the last time I had a problem with a router, I hard reset it and it came back.
so I tried the same, reset and went back into admin page and it default back to original blank password and I enter my wep again and change password. now it is still not working, it say my firmware is up to date. any suggestions? here is my output below on ipconfig..
C:\Documents and Settings\Administrator>IPCONFIG /all
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Etheter
Physical Address. . . . . . . . . : 00-13-D3-13-6B-DA
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
C:\Documents and Settings\Administrator>ping 192.168.0.101
Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Reply from 192.168.0.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\Administrator>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-
interesting for me,thanks
-
cssangeles, did you get the router going again?
The info you provided shows the router is connecting normally to the PC. The next thing to do is log in to the router at 192.168.0.1 and go to the status page. Post the results and perhaps someone can help you get the connection to the internet going - I assume that is the problem ("not working" isn't very specific ;-)
Also, provide your hardware version and the firmware version. My router said the firmware was up to date when it very clearly was not.