D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: zmcmahan on March 14, 2010, 11:16:00 AM
-
I have my time set up to automatically adjust for Dalight Savings Time. Well...needless to say, this did not happen this morning. I have it also set up to take the time from the NTP server. When I set it up to get the time from my computer, it's is correct, but when I got back to the NTP server, it switches back an hour earlier.
Is it possible that the NTP server is not updated for DST yet?
Anyone else run into this?
Firmware 1.08.
-
Yes, I have run into it as well. It seems unlikely that it is an NTP server issue, as I am using an NTP server that is not one of the default choices.
-
Same here. I had to set it manually and disable the NTP server.
-
I'm also in the same boat. All the other devices on my network get their time from the same NTP server, but they're all correct...
-
Since the time on all the Windows machines were updated for me, but the DNS-323 and DNS-321 are not updated, I'd say this is yet another D-Link bug. ::)
Low class but working solution. Set your timezone to one east of you, I'm on the East Coast, and I set it for Atlantic time and saved the settings, not the time is right.
-
NTP requests only serve up GMT.
It is certainly not an NTP issue; this is squarely a Dlink issue. I find that changing the DST date does absolutely nothing noticable :(
FWIW: Keep NTP enabled and disable DST. Simply change the "Time Zone" instead.
Ex. For EST, instead of GMT-5, use GMT-4 to "spring ahead" manually and still use NTP.
-
Ex. For EST, instead of GMT-5, use GMT-4 to "spring ahead" manually and still use NTP.
See previous post. ;)
-
Well...at least I'm not the only one with the problem. Used the poor man's solution of changing time zones and disabling DST. Thanks for all the replys.
-
I have to believe this is a universal issue, at least with 1.08. I've reset to factory defaults and reconfigured, it still doesn't get the correct time.
-
Telnetting seems to indicate the DNS323 uses GMT locally
/ # date
Mon Mar 15 15:18:57 GMT 2010
This should be EDT in my case Mon Mar 15 15:18:57 EDT 2010. (as per my other linux servers)
Did this work in previous releases? I haven't had my unit long enough to go through a time change before.
-
I just checked my NAS and have the same problem as well (1.08, factory defaulted and reconfigured). I am in EST, so -5 and I selected to enable DST and configured it for 03/15 and 11/07, however it hasn't changed the time by an hour yet.
On a side note, configuring the actual day that DST should start and stop isn't entirely accurate, as I believe the rules are (for my location at least) 2nd Sunday of March and First Sunday of November. So, the actual dates will vary each year.
You should use the same method of configuration as you have in the DIR-825 where it picks the day of the week, not the specific date.
-
They should pick any method that works properly. ::)
-
Similar problem from last month....
I am trying to get the setup to recognise daylight saving in Australia (Oct to Apr). If I try to set these dated I get an 'Invalid Date' error response. It seem the setup doesn't like a start date after the end (in terms of mm/dd). I need DST to work from Oct 4 (10/04) to Apr (04/04). Any start dates fromm last year give the error, start dates from this year (01/01) are accpected, but even these don't adjust the time (which stays at UTC, from a time server, plus local timse zone offset).
Just updated to the release v1.08. Same symptoms.
« Last Edit: February 18, 2010, 09:55:52 PM by wjgw »
-
Well, that's not as big an issue as you might think, since the capability doesn't work anyway! At least it doesn't fool you into thinking it might work. :D
-
I've had some weird issue that the night that Daylight Savings occurred, the DNS-323 (on 1.08) did not update its time (just like all of you). But the following morning, when I tried to stream video from it to my PS3, the PS3 locked up. Now it can't stream video without my PS3 locking up when I try to do so from browsing through folders on PS3 (it still works if I stream a video from the "Show All Videos" option).
The only thing that changed between Saturday night (3/13) when it was working, and Sunday morning (3/14) when it began freezing, was Daylight Savings. I also had put in Uncharted 2 for the first time, and it updated the title to 1.06, so I erased the title update, and rebuilt the Hard Drive Database and File System (via the PS3 service menu), and it didn't change anything.
-
I have my time set up to automatically adjust for Dalight Savings Time. Well...needless to say, this did not happen this morning.
Firmware 1.08.
I'm seeing the same issue when viewing time via the GUI however it appears the change did take place as files saved to the DNS323 show the correct time.
-
I just saved a new file on the DNS-323, and it reflects the correct time, but I have the timezone set one off to fix it. So, that's not working here.
-
I just saved a new file on the DNS-323, and it reflects the correct time, but I have the timezone set one off to fix it. So, that's not working here.
What happens when the time is set correctly? Do files show the (same) correct time.
-
I might go back and screw with it when I get the time, right now it's working and displaying the correct time, so I'm leaving well enough alone. Maybe it'll all be fixed in 1.09. :D
-
...right now it's working and displaying the correct time, so I'm leaving well enough alone.
I don't blame you. Like the old saying goes; "If it ain't broke, don't fix it."
-
Hi, I just came across this in a clients DNS-323 logs, "System Time changes to "Current time" ". The user can't seem to access the DNS-323 mapped drive in the morning, till I reboot, and its when the time updates. My question is, can the time affect the user from accessing the drive? Thanks
-
When I updated my DNS-323 to v1.0.9 of the firmware, the time setting screen changed to not have any time server entry, and to require me to manually set the dates that Daylight Savings time starts and stops. So at first glance this looks like a huge reduction in functionality. Especially as now it's not clear how the time is synchronized. Any ideas anyone?