Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[PatrickGC]

Does resetting the factory defaults in the router actually reset everything and clear the non-volatile memory?  This question relates to another post here that I have in regards to using the built in DDNS client which in my case is TZO.

After reading a fair number of posts, both here and at an other discussion board DSL Reports it is unclear whether memory really gets flushed out or not when the device is reset.  The result being that the router starts misbehaving over time due to these pieces of junk left in memory.  In my case, the router has gone from working perfectly for almost a year to various seemingly unrelated errors.  The first being a daylight savings Time issue and now the DDNS client not working.

Some of the suggestions for clearing memory are downright frightening.  One posting [not on this board] suggests repeatedly disconnecting the power abruptly while holding down the reset button.  To me that sounds dangerous with the results more likely being damaged circuits.

Patrick

PS:The TZO representative is fairly certain that I have a bad client in the router.  I don't see how that's possible, it has been working for such a long time and across two firmware versions.
Firmware is 1.33 NA & Hardware is A4.

[summerstormpictures]

Short answer: No. That comes from me asking this directly to a tech support guy at D-Link.

I'd get on the phone and plead your case for a replacement/RMA. I was outside the warranty period but the 1.33NA firmware upgrade effectively ''bricked'' my 655, which was the conclusion the tech reached after performing about a half-hour's worth of troubleshooting with me. The final thing we did together on the phone was to back-install an earlier firmware. This made things worse and at that point he set up the RMA to replace/exchange. I'm expecting it to arrive tomorrow--although I don't know what I'm getting. I tell you what though, if it comes with the original shipping firmware in the 1.X range. I'm not going to upgrade it, that's for sure. Every firmware upgrade since then has been nothing but ''carp'' if you get my meaning. Nothing but a slew of ''hey we're not responsible'' betas that didn't work, followed by a so called ''working'' firmware that didn't work.

I'm also going to sell it after making sure it ''works''--for whatever I can get--and then apply the money toward a router from reliable company that doesn't load up their router with ''carp'' that has no business being on it and that I didn't pay for, and that doesn't compromise security.

For a router that was so highly touted by various geek gurus a couple years back, this thing has been nothing but trouble from day one. I should have listened to my inner voice and taken it right back to Best Buy. Could have, would have, should have...

Sadly enough, when the folks at Revision3 gave it rave reviews, I passed the news along.  I recommended the 655 to three friends of mine--two Mac users and one PC/Windows user. Now, two years out, none of the three of my recommend-ees use it anymore. The two Mac users; one took it back within weeks--he must have heard my inner voice--and decided that dealing the problems with the Airport Extreme were better than the problems with the DIR-655. The second bricked theirs and it eventually ended up in his box of cables and other ''carp'' in the garage. The PC/Windows guy RMA-d his a year or so back and when he got the new one, he didn't even open the box because he'd already gotten a different router. It's still sitting on his shelf next to old software. He says he keeps it as his emergency back-up--for when his router fails--which it hasn't. Now that I've joined the group, that's a ''four-peat fail'' in my book. Great going D-Link.

[PatrickGC]

Hi Summerstormpictur:

That really is unfortunate that the router doesn't do a complete and thorough wipe.  The problems might be due to just a few bits out of place somewhere in the non-volatile memory.  A true reset would give the router a completely fresh start and everyone would be happy.  This is where we need some enterprising programmer out there to write a killer utility something that would take the router as far back as it can go.

OK, this product is on a timeline then.  I won't be able to invest the hours in research on a new router until the latter half of April.  Consumer hardware is really beginning to anger me.  This is the fourth router in about two years than I have tried.  Have to admit though it's the best one of the four.  They all seem to have glitches that one form or another, or are so limited [especially if you get them from the ISP] as to be ridiculous.

For the time being however I have developed a rather goofy workaround using a software implemented DDNS client.  It appears to use a completely different method of "pushing" the information to TZO then the router.  Leaving the possibility that the problem does indeed lie somewhere else on the Internet.  I know the owner of the store I purchased most of the computer hardware from, so I'm going to talk really nicely to him and see we can arrange an extended "try before you buy" deal on some routers.

Patrick