• February 23, 2025, 05:09:03 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.

Pages: 1 [2]

Author Topic: DST/NTP time settings - still broken  (Read 18296 times)

bripab007

  • Level 3 Member
  • ***
  • Posts: 104
Re: DST/NTP time settings - still broken
« Reply #15 on: August 31, 2009, 05:57:49 PM »

I've been running 1.08b5 for a week or so now (currently on daylight savings time), and it's syncing to an NTP server on my LAN, and, so far, it's kept perfectly good time.
Logged

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: DST/NTP time settings - still broken
« Reply #16 on: August 31, 2009, 06:07:38 PM »

I upgraded to 108b5, reset the box to defaults, and I think it's actually keeping time now.  I have the latest beta on my DNS-321 now, and it's finally keeping time as well.  I guess even if the account permissions are all screwed up, at least the box can keep time now.  ::)
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

shanek

  • Level 1 Member
  • *
  • Posts: 13
Re: DST/NTP time settings - still broken (fixed 108b5)
« Reply #17 on: September 22, 2009, 12:15:45 AM »

21 days and my dns323 has more or less the correct time.  still pretty stupid that i have to specify the exact dates each year that dst should be in effect, but hey, this is a major step forward!!  =)  =)
Logged

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: DST/NTP time settings - still broken
« Reply #18 on: September 22, 2009, 05:43:08 AM »

Mine keeps the proper time, it's obviously setting itself from the time server.

Specifying the exact dates for start and end of DST isn't that stupid, believe it or not, there are still variations across the country.
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

shanek

  • Level 1 Member
  • *
  • Posts: 13
Re: DST/NTP time settings - still broken
« Reply #19 on: September 22, 2009, 11:01:29 AM »

I have to respectfully disagree.  I have been in this industry for a long time and I configure a lot of devices, anywhere from $50 to $150K in cost, serves, routers, switches, etc.  until the DNS-323, I've never once (at least in the last decade...maybe before...too long ago to remember ;-) had to specific/change the dates every year.  In some cases I specify a time zone, in others, a time zone and starting/ending month/day/time and offset (great flexibility on the later).  An example would be '2nd sunday in march at 2am, 1st sunday in november at 2am, +1 hour'  Point being though, I set it once and don't touch it again until our beloved government starts mucking with the rules for no good reason.
« Last Edit: September 22, 2009, 11:04:58 AM by shanek »
Logged

jasonsbx

  • Level 1 Member
  • *
  • Posts: 24
Re: DST/NTP time settings - still broken
« Reply #20 on: February 07, 2010, 08:44:36 PM »

I have to respectfully disagree.  I have been in this industry for a long time and I configure a lot of devices, anywhere from $50 to $150K in cost, serves, routers, switches, etc.  until the DNS-323, I've never once (at least in the last decade...maybe before...too long ago to remember ;-) had to specific/change the dates every year.  In some cases I specify a time zone, in others, a time zone and starting/ending month/day/time and offset (great flexibility on the later).  An example would be '2nd sunday in march at 2am, 1st sunday in november at 2am, +1 hour'  Point being though, I set it once and don't touch it again until our beloved government starts mucking with the rules for no good reason.

However there are places they do change and this doesn't just go to one country. I'm not sure time servers serve outs DST time but depend on the client to handle that e.g many OS would have something built in to sort it out (lookup zoneinfo). This avoids that mechanism and probably you'll set it once and forget. Pity it doesn't work for the Southern Hemisphere.
Logged

shanek

  • Level 1 Member
  • *
  • Posts: 13
Re: DST/NTP time settings - still broken
« Reply #21 on: February 07, 2010, 10:42:12 PM »

I’m not sure I understand your first sentence…

Correct, time servers don’t send out DST information, but rather rely in the local host to know where it is.  You can check out  Wikipedia if you want for a description of the NTP protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol).

I also don’t understand your statement about  NTP/DST not working in the Southern Hemisphere?  A client that implements these properly will work in any city/state/country in the world.

Logged

jasonsbx

  • Level 1 Member
  • *
  • Posts: 24
Re: DST/NTP time settings - still broken
« Reply #22 on: February 10, 2010, 11:33:07 PM »

I’m not sure I understand your first sentence…

Correct, time servers don’t send out DST information, but rather rely in the local host to know where it is.  You can check out  Wikipedia if you want for a description of the NTP protocol (http://en.wikipedia.org/wiki/Network_Time_Protocol).

I also don’t understand your statement about  NTP/DST not working in the Southern Hemisphere?  A client that implements these properly will work in any city/state/country in the world.


The date you enter is month/date and it appears validation is done on just these two values. Here it means start date is effectively after end date. ie start 26 Sep end in 6 Apr.
Logged

shanek

  • Level 1 Member
  • *
  • Posts: 13
Re: DST/NTP time settings - still broken
« Reply #23 on: February 10, 2010, 11:44:07 PM »


 :(

Oh, I see...

Wow, it's amazing that they can screw it up so badly, isn't it?  Espeically considering that they get it so right in other products!

Logged
Pages: 1 [2]