D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: selectortone on October 03, 2013, 03:49:51 AM

Title: System Time Problem
Post by: selectortone on October 03, 2013, 03:49:51 AM
Hello,

I have had my DNS-320 (B model) for a couple of weeks now and so far everything has been working great except for the system time. I've set it several times but when I come back to the DNS-320 later I find that the time has jumped ahead an hour.

I'm in the UK,Time Zone is set to  "(GMT) Dublin, Edinburgh, Lisbon, London" and I've tried setting the time both manually and from my computer.

Each time I reset the time I can see that the time has been modified in Recent Activities on the Home Page, but when I come back to the unit later the time has jumped forward an hour again.

edit:

I think the time is getting reset overnight - if I look in the log files I see an entry at 3:30am each day: "System Time Is Updated By RTC."


 
Title: Re: System Time Problem
Post by: selectortone on October 06, 2013, 03:56:15 AM
Well, this is driving me nuts. It behaved itself for two days, then this morning I logged in and it's jumped ahead by one hour again.

I'd be very grateful for some help with this.
Title: Re: System Time Problem
Post by: hoppo1 on October 07, 2013, 12:42:20 AM
What firmware you on? there was a problem a while back with this fixed by an update - http://forums.dlink.com/index.php?topic=38650.0 (http://forums.dlink.com/index.php?topic=38650.0)
Title: Re: System Time Problem
Post by: selectortone on October 07, 2013, 05:03:19 AM
I have the newer type B unit - firmware is V1.00, which i believe is current.

Thanks for that link, that is exactly the problem I am having. How do I make D-Link aware of this -- it looks like they need to fix it again for the 'B' hardware.
Title: Re: System Time Problem
Post by: selectortone on October 14, 2013, 07:44:05 AM
For UK users with B hardware units, this problem has now been confirmed by D-Link tech support:

"Dear customer,

We can now confirm this issue and we will report it to our developers.
This needs to be fixed in a future firmware."