Print

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

[EddieZ]

There must be some set of options that when configured cause this problem.  I tried that address twice with the same results and all the other settings the same.

I guess so. But I think entering an NTP that causes no problems is easier (unless you got too much 'time'  on your hands and persist in keeping the problem).

[mackworth]

Right, but I think the problem is that if there is some element to reproducing this besides just entering a time server, how does one know what a "time server that works" is?  It seems like its going to be more trial and error.  At this point I am just not going to enter one.

[ttmcmurry]

Hey EddieZ --

Yesterday I made the 1.31 jump and for sh*ts and giggles I added pool.ntp.org as my time server.  I've never seen my 655 reboot so frequently and with so much passion!

Fortunately, turning the cable modem off will stop the problem from recurring long enough to change NTP to time.nist.gov.  Its been working ever since.

Very strange indeed.

[EddieZ]

Right, but I think the problem is that if there is some element to reproducing this besides just entering a time server, how does one know what a "time server that works" is?  It seems like its going to be more trial and error.  At this point I am just not going to enter one.

You can use the ones defaulted in the router. Unless you don't trust Dlink to give the exact time  The majority of NTP will work (looking at the choice you have besides the 'pool' ntp's). Just an opinion, but I think you're making an elephant out of a mouse...

It's only there to set the time on the router, and unless you're in a transaction critical environment with timestamping there is any importance to it. But in that case you probably should also not be using a 'soho' DIR655 on the network...

[mackworth]

You can use the ones defaulted in the router. Unless you don't trust Dlink to give the exact time  The majority of NTP will work (looking at the choice you have besides the 'pool' ntp's). Just an opinion, but I think you're making an elephant out of a mouse...

It's only there to set the time on the router, and unless you're in a transaction critical environment with timestamping there is any importance to it. But in that case you probably should also not be using a 'soho' DIR655 on the network...

If you look at my first post, I just said it was annoying...  Not making a elephant out of anything. 

Its just annoying.

[EddieZ]

ok

[gericb]

EddieZ - I take it you are part of D-LINK Technical or Firmware support?  It seems your roll here is poo-poo anyone's topic, comments of issues they have seen. 

Of course you seem to never have the problems yourself, we are all just lame nobs here, and you are the GOD of perfection right?  

A problem is a problem, no matter the degree of the problem, and no matter if you agree it is or not from your perspective, it is to others.  Your down playing of the "issues" as we see it doesn't negate our belief it is a problem, or in fact it's being taken as such. If more than one person see's the problem, can reproduce it, it's a problem.

Part of the reason anyone buys a product it on the belief there will be reliable, logical, continued support of same.  Given for example that the NTP option in the DIR-655 ALLOWS you to put in ANY OTHER NTP's, is reason we SHOULD expect it to work. 

It's not me saying that I don't trust the D-Link ones, but I sure as hell do not trust the M$ ones, and long ago stopped using those.  So if I WANT to use this, I should be able to and not expect to see my router reboot senselessly over and over again...when it is stable before I decide to a server of my choice.

I might be new to this forum, but have 15+ of IT background, both technical and Mgmt, and the things going on with this particular 1.31NA version of the firmware are just buggy, flat out.

Every installation is going to be different, every need and expectation is going to be, and thankfully we do not need to get any approval from you for our varying environments, needs and expectations as you obviously have none yourself.

I have always personally steered IT/consumer purchases away from D-Link products for this very reason, weird, unreliable firmware updates and issues that rarely seem to get resolve.  To that point, they as a company knew the impressions of their hardware and mgmt and have attempted many revamps of products lines, techical staff (having friends on the inside), and winning back customers.

Given the age of this company and presumed experienced product designers, I have FAR LESS issues with Linksys products.  My exposure is 100% post purchase, otherwise there would never be these issues going on and me inquiring is anyone else is experiencing the same things, because I would not be buying them. 

So give it a break, be part of the real soultion, problem determination, because your wonderful rosey world of no problems doesn't exsist for many others, and they are as equally important in their needs to be resolved to their satisfaction.

Thanks! 

[Lycan]

No, EddieZ is NOT part of ANY D-Link staff. However blunt he may be, his point is valid. Now, I understand that more and more people are suffering from problems with the 1.31 firmware as well as it's cousin code on the other models.

We are looking in to the situation with renewed vigor and will do everything within our ability to isolate and correct the issue asap.

I understand that it seems like Eddie and the D-Link mods may not care, this couldn't be farther from the truth. We are constantly monitoring the forums and noting issues that are repeatedly appearing with our customers.

I'm going to lock this thread as it's reached the end of it's usefulness.

-Lycan.