• July 16, 2025, 05:55:39 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: Installemd 1.21 firmware, loaded old settings, router turned into a brick  (Read 9591 times)

corporate666

  • Level 1 Member
  • *
  • Posts: 4

Well, it seems like a brick at least.

I noticed my internet connection seemed slow, and since I was lazy to go to the router to reboot, I logged into the admin console to click "reboot".  While I was in there, I figured I'd check for software updates, and I noticed there was a new firmware.  So I upgraded the router.  It said I should save settings since they may be lost, so I did.  I upgrade the firmware, SSID is back to dlink, open network, everything working OK.  I go in, reload the settings, reboot the router, still OK.  Connected to the internet, everything fine.

Couple of minutes later, I can't connect to the internet.  I try to go into the admin console of the router, I can't get in.  I *do* see my SSID listed (not generic 'dlink'), and when I try to connect, it says "local access only".

I rebooted the router by unplugging it and waiting a moment.  No difference.

I tried pushing the reset button, no difference.

I tried holding reset down for a while, after 10 seconds or do, the lights flickered off then on.  I noticed this reset the router and the SSID was back to 'dlink' with no security.  But the problem persists, I can connect to the network, but it says "local access only".  I cannot get to the admin console.

It's not my PC that is the problem, I don't think... I am sure everyone says this, but I do have a high technical level, I have an MCSE and was a network admin for some years... anyway, I have numerous devices, laptops, desktops, mobile WiFi phones and none of them will connect.  One PC is wired, it also will not connect, same problem.

Are there any suggestions?  I suppose I could hook up a USB cable and use the dlink software to try to... well, I dunno... what?  Downgrade to an older firmware?  Or should I just try to get dlink to RMA this thing?  Or is there anything else I should try?

I am disappointed to say the least.  I've had 2 x Netgear routers and 2 Linksys routers that have all failed after various lifespans over the past few years.  I bit the bullet and paid $200 for this thing, figuring a "high end" router would be better.  I ended up buying five of these, two for my work, one for home, one for my brother and one for sister.  I am really hoping this is solvable because I expected DLink to be top of the line, but we shall see how this plays out.

And in case someone raised an eyebrow at the # of failures - me too.  But I am not doing anything to kill these.  They are sitting in my basement on a server rack - it's not hot, nor dusty, nor damp, and it's on a good surge supressor, so I have no idea why I can't get a router that works.
« Last Edit: April 01, 2009, 09:59:00 PM by corporate666 »
Logged

RamItMan

  • Level 1 Member
  • *
  • Posts: 5

Had the same problem a week or so ago. Wound up deleting the connection off the computer and rebuilding it and everything has been fine since. Don't think it's not the computer just because it looks like a router problem.
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494

restore to facory defaults and configure the router amnually. Should fix it.
Logged
DIR-655 H/W: A2 FW: 1.33

corporate666

  • Level 1 Member
  • *
  • Posts: 4

Had the same problem a week or so ago. Wound up deleting the connection off the computer and rebuilding it and everything has been fine since. Don't think it's not the computer just because it looks like a router problem.

It's not that, considering it doesn't work on 3 laptops, 1 desktop and 1 mobile device.
Logged

corporate666

  • Level 1 Member
  • *
  • Posts: 4

restore to facory defaults and configure the router amnually. Should fix it.

When I hold the reset button in for 20 seconds or so, am I not resetting it to factory defaults?

I've done that and I still can't get into the web admin console.
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335

Can you ping the routers IP? Does it offer DHCP?
Logged

corporate666

  • Level 1 Member
  • *
  • Posts: 4

It seemed to give me an IP at one point yesterday... maybe I was mistaken.

Anyway, I took the router to work today with the intention of using the USB cable to reconfigure it with the software, but I couldn't find a suitable USB cable.

So I brought it home again, powered it up... I can see the network (the SSID).  If I connect, it says "local access only".  And to answer your questions, no I cannot ping the router, nor does it give me a DHCP address.

Sounds like the thing is toast, huh?

Thanks for your help.
Logged

EddieZ

  • Level 10 Member
  • *****
  • Posts: 2494

If you can get in, reset to default or flash with 1.22beta and do not use saved config. Just configure the box manually.
Logged
DIR-655 H/W: A2 FW: 1.33

Arvald

  • Level 3 Member
  • ***
  • Posts: 108

It seemed to give me an IP at one point yesterday... maybe I was mistaken.

Anyway, I took the router to work today with the intention of using the USB cable to reconfigure it with the software, but I couldn't find a suitable USB cable.

So I brought it home again, powered it up... I can see the network (the SSID).  If I connect, it says "local access only".  And to answer your questions, no I cannot ping the router, nor does it give me a DHCP address.

Sounds like the thing is toast, huh?

Thanks for your help.
sounds like the option for wireless admin got turn to wired admin only.
are you running 100% wireless or do you have a PC that you can wire to it to connect?

I may be barking up the wrong tree but that is the "local access only" message.
Logged

lotacus

  • Level 4 Member
  • ****
  • Posts: 450

ipconfig?
Logged

vaz

  • Level 2 Member
  • **
  • Posts: 38

Half the stuff he is saying sounds like it's a fix-able issue and the other half makes it sound like the issue is not fix-able. You can see the ssid, but you don't get an address. The only time that I had this problem is when I set the mac table to deny all computers on the list, on accident. That was an easy fix though, just hold the reset button down to get factory settings. If a router is bricked, you don't get an ssid. A bricked router is supposed to offer the same functionality as a brick you build a structure with and they don't give out ssid's. I've had my fair share of problems with the dir-655 and had to rma one for rapid and uncontrollable resetting, so it doesn't surprise me that it would do some odd things, if it's really working the way you describe, I would try and rma it, but the descriptions of your symptoms sounds like they can be solved with normal troubleshooting.
Logged