Topic 'System Clocks Incorrect After Jan 1st' in forum 'Wireless Service Providers' - dslreports.com

Re: System Clocks Incorrect After Jan 1st

Wed, 16 Jan 2013 12:52:08 EDT

xlteks_com posted : I just used some other servers and they are working now. Thanks anyways guys. Have a good one.

Re: System Clocks Incorrect After Jan 1st

Wed, 16 Jan 2013 12:45:24 EDT

xlteks_com posted : Ok thanks, I wonder why the ntp server is not reachable. I tried pinging 66.152.175.36 and 192.43.244.18 and the pings are timing out.

Can anyone else ping these?

Re: System Clocks Incorrect After Jan 1st

Wed, 16 Jan 2013 12:42:09 EDT

xlteks_com posted : Am I the only one that is having issues with the system clock? I even tried removing the primary server and inputting the secondary server in its place and no change. It seems that it is not updating.

Does anyone know how to force the ntp client to update? I can't figure it out.

Thanks.

Re: System Clocks Incorrect After Jan 1st

Tue, 15 Jan 2013 09:41:38 EDT

xlteks_com posted : [att=1]

Re: System Clocks Incorrect After Jan 1st

Tue, 15 Jan 2013 08:33:31 EDT

xlteks_com posted : I noticed that even my devices that do not have 5.20 on them still have incorrect dates and times. I am going to remove the primary ntp client and see if only the secondary client yields an accurate time.

I did notice one of my devices that has 5.11 on it has the correct date/time.

This is puzzling. Any suggestions would be helpful.

Thanks.

Re: System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 19:21:10 EDT

Inssomniak posted :

said by viperm:

We are running 6.0 I mean I could put another ntp server but once again it converts it to an IP instead of keeping the FQDN and if that IP goes stale or bad same thing you would get no time updates.

FYI I mean pool.ntp.org not (poo) hahaha

Im afraid to run 6.0 :) At least on any core routers. I do have it on an AP for a test, seems OK, as an AP. (no routing)
--
OptionsDSL Wireless Internet
»www.optionsdsl.ca

Re: System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 19:20:06 EDT

viperm posted : We are running 6.0 I mean I could put another ntp server but once again it converts it to an IP instead of keeping the FQDN and if that IP goes stale or bad same thing you would get no time updates.

FYI I mean pool.ntp.org not (poo) hahaha

Re: System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 19:17:05 EDT

Inssomniak posted :

said by viperm:

I have not noticed on the 3 devices out there? I do wish I could figure out why TIk does not keep the name of poo.net.org instead of converting it to an ip?

Any ideas on how to prevent that what happens if that IP fails for some reason?

It quits getting time.

There is a bug in 5.20 That breaks NTP client if you happen to be running that.
--
OptionsDSL Wireless Internet
»www.optionsdsl.ca

Re: System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 19:13:54 EDT

viperm posted : I have not noticed on the 3 devices out there? I do wish I could figure out why TIk does not keep the name of poo.net.org instead of converting it to an ip?

Any ideas on how to prevent that what happens if that IP fails for some reason?

Re: System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 15:54:05 EDT

shorthairedp posted : Probably not related, but I noticed a few devices I had pool.ntp.org as the ntp for were a day ahead for a couple of days

System Clocks Incorrect After Jan 1st

Mon, 14 Jan 2013 13:18:51 EDT

xlteks_com posted : I was wondering if anyone has experienced system clock problems with Mikrotik after Jan 1st. All of my devices have different dates and times now.

Does anyone have new servers that will set the clocks to the right date and time?

Thanks in advance.

Here is the output code from my current settings:

/system ntp client
set enabled=yes mode=unicast primary-ntp=192.43.244.18 secondary-ntp=\
66.152.175.36
/system clock
set time-zone-name=CST6CDT
/system clock manual
set dst-delta=+00:00 dst-end="jan/01/1970 00:00:00" dst-start=\
"jan/01/1970 00:00:00" time-zone=+00:00