Print

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

[mackworth]

The only way to put the monkey solely on Dlinks shoulder is when you know for sure that the NTP's causing the issue (why them?) are not the source of the issue in any way. Why are those specific servers causing it? I have NTP's that don't work at all in Windows and others work perfectly fine. Is that Microsofts problem?

So if you want a PRO approach on this issue, you gather more info before pointing fingers to the "usual suspect". Whether it is Dlink, Linksys or Eminent is really not important to me, if you do not come up with POC, eveidence etc you're not an IT pro, but only a n00b. 

I see your point, and generally its a good one, but I think its somewhat off base here.

And no that isn't Microsoft's problem, but if you can enter an address from NTP and have it reboot windows continuously, I think there is a Microsoft problem here.

[hfournier]

I just ran into this same issue...

I had NTP enabled and set to the DLink server (ntp1.dlink.com). Today is Nov 1 and the end DST (in Canada), so I checked the router to see if it had the correct time (I have problems before). It didn't. It had gone back 2 hours instead of 1. I unchecked DST and clicked Save, but it had no effect. I tried a different offset, no effect. I disabled NTP, copied my computer's time (which appeared correctly), but when I hit Save, it went back to the same incorrect time. Nothing I tried could get the correct time to appear. Then I thought of trying a different NTP server. I entered time.nrc.ca and the router immediately went into endless reboots. I did a reset and reconfigured it and then came here.

I read the other thread mentioned by mackworth and it was closed by Lycan who stated: "We are looking in to the situation with renewed vigor and will do everything within our ability to isolate and correct the issue asap." That was posted in May and it's now November, so what exactly does ASAP mean in D-Link terms?

DIR-655
A2
1.32NA

[EddieZ]

I read the other thread mentioned by mackworth and it was closed by Lycan who stated: "We are looking in to the situation with renewed vigor and will do everything within our ability to isolate and correct the issue asap." That was posted in May and it's now November, so what exactly does ASAP mean in D-Link terms?

DIR-655
A2
1.32NA

Before it goes EOL. 

[bluenote]

The fact that using a different NTP server works, is kind of a side issue here.

The main issue is that there's unexpected behaviour from NTP servers that can reboot the router
in an endless loop.  Sorry, but that's crappy programming.  Demonized can blame it on everyone else all he wants, but a router shouldn't reboot when it gets unexpected packets.

Whether or not other crappy home retail routers are at the same level of genius programming, that doesn't mean that its acceptable.

[benben911]

Router: DIR-655 Rev C
Version: 1.31 NA and 1.32 NA

HI all,

I am encountering the exact same issue for the client about the reboot. The initial problem is the Time keeps getting off. It leads to the problem that some PCs are not able to log on when the Access Control rule is on.

I also tried the ca.pool.ntp.org which leads to the router keep rebooting. You won't able to revive it without a master reset. It happens on both Dir655 1.31NA and 1.32NA.

Personally, I think this problem is not tolerated. It is ok to provide a work around solution. However, it is no where easy to find in their support site. Secondly, TIME configuration affects a lot of setting for this router. This router is aiming for small business or home user. For Port Forwarding, Application rule which relies on the Scheduling feature will NOT be functioning at all.

I really hope DLINK can get this fixed as soon as possible. Even if there is a need for a work around or need to be aware condition about the next firmware. Please definitely put it down into the Release note.

Thanks.

[Cobra]

Use one of the NTP servers Windows uses other than time.windows.com

[ironic77]

I read the other thread mentioned by mackworth and it was closed by Lycan who stated: "We are looking in to the situation with renewed vigor and will do everything within our ability to isolate and correct the issue asap." That was posted in May and it's now November, so what exactly does ASAP mean in D-Link terms?

I am beginning to think they're busy cranking out new routers with more features people won't use like routers with touch screens on them and parental filters and all sorts of other stuff.  I mean I know features sell products, but reliability is what keeps people coming back.  If you don't have reliability, people will stop buying your products no matter what features they have.  I realize it is tough to stand out in the business D-Link is in, but really, I'll pay more money if I can just find a decent gig-E router that doesn't have to be reset constantly.  I don't need a touch screen because it sits in a closet.  Maybe they figure if you have to look at it a lot because you have to go into the closet to reset it all the time?