Page 1 of 1
System Date and Time Problem
Posted: Thu Nov 17, 2011 8:53 am
by ranjan
Dear All,
My mikrotik router OS 5.6 is always showing date and time somewhere in 1970s
And after all setting it to automatic for ASIA/Kolkata or setting it to Manual it is not getting corrected.
Once I set date and time then after reboot it again goes in 1970 Jan 01 and all the timings are getting disturbed.
So please help me shortout this problem.
Thanks in advance.
Re: System Date and Time Problem
Posted: Thu Nov 17, 2011 11:07 am
by pospanko
RB doesn't have battery to keep date and time so only way to have it right is to use NTP client to synchronize your RB against NTP server (Or you could always set it up manually
)
Re: System Date and Time Problem
Posted: Thu Nov 17, 2011 11:31 am
by ranjan
RB doesn't have battery to keep date and time so only way to have it right is to use NTP client to synchronize your RB against NTP server (Or you could always set it up manually
)
Thanks for the answer but can you please tell me how to setup NTP client and server for RB 450G with OS 5.6?
Re: System Date and Time Problem
Posted: Fri Nov 18, 2011 12:30 am
by Iaco
To enable the NTP client from console:
/system ntp client set enabled=yes mode=unicast primary-ntp=pool.ntp.org
Iaco
Re: System Date and Time Problem
Posted: Fri Nov 18, 2011 5:32 am
by ranjan
To enable the NTP client from console:
/system ntp client set enabled=yes mode=unicast primary-ntp=pool.ntp.org
Iaco
I have tried the console code but its not working.
I am getting error.
"invalid value for arguement IPV6-address"
So please tell me how to define server and client step by step..
Thanks in advance.
Re: System Date and Time Problem
Posted: Fri Nov 18, 2011 6:05 am
by tjc
Re: System Date and Time Problem
Posted: Wed May 28, 2014 6:30 pm
by cdsJerry
Is this still true in version 6.13? We have to write a script to get the time?
I see there's a SNTP Client window but it only seems to want an IP. It won't accept a domain. Is that normal for RouterOS? The IP for pool.ntp.org changes. Seems like it should resolve the domain name rather than require an IP.