• February 23, 2025, 08:13:11 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: System clock not synced, and very slow  (Read 9677 times)

gasoline

  • Level 1 Member
  • *
  • Posts: 4
System clock not synced, and very slow
« on: August 18, 2009, 12:39:06 PM »
I just bought this router and I love it. However I can't set the right time (I need right time for schedules etc). When I think it with my PC time it gives the right time, but days later it's hours, even days behind.

What is going wrong. Anybody any idea?
Logged

MrC

  • Guest
Re: System clock not synced, and very slow
« Reply #1 on: August 18, 2009, 07:32:09 PM »
It appears that NTP time synch does not work correctly.  It certainly doesn't sync with any LAN-based NTP server.

The clock also sets itself back to the previous time you'd selected if you change any settings on the Time page.  It needs instead to set the time only when one clicks a Set Time button, and not on each Save Settings.
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: System clock not synced, and very slow
« Reply #2 on: August 19, 2009, 10:21:25 AM »
We do not support the use of LAN side NTP. We never claimed that we did.
Logged

MrC

  • Guest
Re: System clock not synced, and very slow
« Reply #3 on: August 19, 2009, 04:39:56 PM »
Quote from: Lycan on August 19, 2009, 10:21:25 AM
We do not support the use of LAN side NTP. We never claimed that we did.

This is a silly, defensive response.  There is simply no reason why this can't be supported.  There hasn't been a valid, worthy response yet that indicates why this arbitrary restriction exists.  That the router is named such-and-such, is is poor reason.
Logged

Syaoran

  • Level 3 Member
  • ***
  • Posts: 192
Re: System clock not synced, and very slow
« Reply #4 on: August 20, 2009, 01:56:12 AM »
Quote from: MrC on August 19, 2009, 04:39:56 PM
This is a silly, defensive response.  There is simply no reason why this can't be supported.  There hasn't been a valid, worthy response yet that indicates why this arbitrary restriction exists.  That the router is named such-and-such, is is poor reason.

I think there's really only one answer to why it's not supported.  Laziness! 
Logged

platt63

  • Level 1 Member
  • *
  • Posts: 15
Re: System clock not synced, and very slow
« Reply #5 on: August 20, 2009, 02:55:38 AM »
gasoline,

What are your settings in "Tools | Time" ?
Logged

gasoline

  • Level 1 Member
  • *
  • Posts: 4
Re: System clock not synced, and very slow
« Reply #6 on: August 25, 2009, 08:20:41 AM »
Quote from: platt63 on August 20, 2009, 02:55:38 AM
gasoline,

What are your settings in "Tools | Time" ?

I'v managed to solve the problem.

When I sync the time than everything works o.k. But I was testing several other settings. When you change other settings (not related to time) the router jumpes to another time. Hours or even days earlier. But when I sync the time with my PC and than save settings and than log out than the time is running fine.

So in short, when I change setting the last thing  I do is go to the time setting, Sync and save and then log-out.
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: System clock not synced, and very slow
« Reply #7 on: August 25, 2009, 09:13:07 AM »
We offer a public time server. It will properly sync your router to the time zone specified. There's no need for us to support LAN side time servers.
We DO NOT support the use of LAN side NTP servers on ANY of our home class products. It has NOTHING to do with laziness. It has everything to do with the products intended functionality and deployment.

Logged

DIR-855 :-(

  • Level 2 Member
  • **
  • Posts: 34
Re: System clock not synced, and very slow
« Reply #8 on: August 25, 2009, 03:54:14 PM »
I bet it has everything to do with DLink not being in tune with their customers and their expectations.

While I can see that not many SOHO setups would have an internal NTP server, I can't see why you would block the service coming from an internal location to perform the sync. Why on Earth would you want to go to the effort of not allowing this.

The only reason DLink have their own NTP server is because they were sued by NTP.org for abuse as it was not set up for companies to build into their products. This was a free service for users and if they choose to use ntp.org on their router, then fine, but not for companies like DLink to market their products with it.
« Last Edit: August 25, 2009, 07:25:29 PM by whoisnader »
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: System clock not synced, and very slow
« Reply #9 on: August 26, 2009, 08:28:26 AM »
1) The reason for the NTP servers exsistance doesn't change it's purpose. To provide you with NTP.

2) Using a LAN side NTP server is most definetly not a SOHO application. We build firewalls that will give you that functionality.
Logged

DIR-855 :-(

  • Level 2 Member
  • **
  • Posts: 34
Re: System clock not synced, and very slow
« Reply #10 on: August 26, 2009, 03:27:11 PM »
Quote from: Lycan on August 26, 2009, 08:28:26 AM
2) Using a LAN side NTP server is most definetly not a SOHO application. We build firewalls that will give you that functionality.

Man you really have no clue. Unless Gasoline has a large enterprise running off a DIR-855, then he is proof that it can be a SOHO application. Who decided to make you in charge of what is and isn't a SOHO application.
« Last Edit: August 26, 2009, 03:30:12 PM by whoisnader »
Logged

MrC

  • Guest
Re: System clock not synced, and very slow
« Reply #11 on: August 26, 2009, 04:03:28 PM »
Quote from: Lycan on August 26, 2009, 08:28:26 AM

2) Using a LAN side NTP server is most definetly not a SOHO application. We build firewalls that will give you that functionality.

You are quite simply, completely wrong and misinformed.  MANY Small Office and Home Offices use Windows Server or Linux server setups, which *already include* NTP services.  NTP traffic is reduced by having one high stratum server provide for lower stratum small office clients.  You really need to get a better handle on what SOHO means, and how such environments are configured.  Even more so, some good Customer Service training might be in your cards.
Logged

Lycan

  • Administrator
  • Level 15 Member
  • *
  • Posts: 5335
Re: System clock not synced, and very slow
« Reply #12 on: September 02, 2009, 09:47:06 AM »
Customer Service has nothing to do with D-Link's SOHO policy. We never claimed support for LAN side NTP servers.
Simply because people are using them DOESN'T make it SOHO.
People use all sorts of enterprise level equipment in SOHO deployments, when you do that you cause compatiblity issues with true SOHO equipment.

D-Link recommends that if you need a FIREWALL that allows for deep custom configuration you purchase a FIREWALL, not a home class SOHO router.

That being said this conversation is WAY off OP topic and I'm going to lock it.

If someone has something useful for the OP and would like to post it, PM me and I'll unlock the thread.

-Lycan
Logged