D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: slade8200 on December 05, 2014, 01:31:59 PM

Title: Time constantly getting off
Post by: slade8200 on December 05, 2014, 01:31:59 PM
My router's (hardware B1) time is always incorrect.  I set it, then check back in a few weeks and it will be incorrect again.  I'm not sure if it did this with the old 2.03 firmware.  Any thoughts?
Title: Re: Time constantly getting off
Post by: FurryNutz on December 05, 2014, 01:37:30 PM
http://forums.dlink.com/index.php?topic=59527.0 (http://forums.dlink.com/index.php?topic=59527.0)
Title: Re: Time constantly getting off
Post by: slade8200 on December 06, 2014, 08:20:24 AM
What was the solution there?  Just use NTP and correct with the DST offsets?
Title: Re: Time constantly getting off
Post by: FurryNutz on December 06, 2014, 10:40:44 AM
Set manual time sync and offset. Mines set for my Time Zone, offset +30 and enable DST.

Unfortunately, this bug is not going to be fixed.  :-\
Title: Re: Time constantly getting off
Post by: fzappa on December 09, 2014, 02:51:25 PM
What was the solution there?  Just use NTP and correct with the DST offsets?
The thread he linked to was mine. Issue still exists and it continues to wander off. I was just adjusting mine again and came here to see if there was possibly more on the problem.
Title: Re: Time constantly getting off
Post by: FurryNutz on December 09, 2014, 03:56:34 PM
Unfortunately, I think we've seen the last of FW updates for the 655.  :-\
Title: Re: Time constantly getting off
Post by: fzappa on January 06, 2015, 12:41:29 PM
Did you PM this user about the beta version?
Title: Re: Time constantly getting off
Post by: FurryNutz on January 06, 2015, 12:51:16 PM
Try this?
http://forums.dlink.com/index.php?topic=59527.msg247336#msg247336 (http://forums.dlink.com/index.php?topic=59527.msg247336#msg247336)
Seem to fix the time issue.

Let us know if it works for you...

My router's (hardware B1) time is always incorrect.  I set it, then check back in a few weeks and it will be incorrect again.  I'm not sure if it did this with the old 2.03 firmware.  Any thoughts?