When I setup our gateway Cisco router to use our Mikrotik as an NTP server it does not seem to work.
On Cisco:
ntp server 12.x.x.x
show association
~12.x.x.x 0.0.0.0 16 - 64 0 0.0 0.00 16000.
Why does it not work? When I use any IP out of pool.ntp.org they all work.
If Mikrotik supported an in production DS3 card perhaps I would not need to use a Cisco as a gateway router anyway.
Matt
Is your MT board configured to be a ntp server?
Is the ntp package enabled at all?
If that is all OK check the ´broadcast/multycast/manycast´ settings.
My Mt server works fine, but OK, I have no Cisco box requesting… 
Off course, check connectivity to the MT box for the Cisco. 
Rudy
The things I’ve seen wrong with NTP on MT:
1 - the stratum is too high for most other ntp clients to accept it.
2 - the reply packet is coming back from the wrong IP.
Check both of the above using packet sniffer to validate what’s being sent / received. Most likely it’s a case of the reply ntp packet is being sent with a src-address that wasn’t asked for so the cisco is just ignoring the response. To fix this you can usually enter a dst-nat rule for udp/123 with action=redirect (I think that works).
Sam
Hi Sam,
What is ¨stratum¨? This is a new term for me?
Rudy
Andrew,
That’s been very much appreciated! 
With the knowledge I now learned I can actually ask you what you mean with :
1 - the stratum is too high for most other ntp clients to accept it.
Is there a limit build in time server (client) function that does not allow a time signal be accepted from the ntp server?
Is so, where does the client compare the time signal with? With its internal clock?
Even if my clients (all MT) are years behind (when they come out of the box, or after a reset) they pickup the signal from my MT ntp server within 30 secs. usually after connected to the network whereafter the new proper time is set.
So I don’t understand your remark regarding the stratum beeing to big?
Or is it because his Cisco box might have too much difference of the time from the ftp server compared to his own internal clock? I know that for instance Windows doesn’t accept an automatic ntp server time update if the difference with the internal system clock is too big. On MT ros is doesn’t make a difference, on Cisco I haven’t got a clue.
rgds.
rudy
Stratum doesnt have anything to do with how far off the clock is and if it should accept it or not… it’s based on it’s knowledge of how accurate it thinks it is. So, a GPS signal pulling time sync from the sky should be considered a stratum 0 or 1. If one system pulls that time and provides it to others it should then increment that value, and on down the line. Windows in some circumstances only trusts stratum 2 or lower. Cisco is probably the same way. The only way to know what your issue is is by turning on debug logging on the cisco and see what it doesn’t like. It should tell you in detail.
Sam
Hi Sam,
I’m trying to understand how it works. Actually I have no problems.
By saying that some operationg systems are probably looking at the stratum this means the stratum level is incorporated in the time protocol?
How can units otherwise know the stratum?
And MT doesn’t care about the stratum or is not looking at it?
Probably does windows not look at the stratum as well but as a security test just doesn’t accept automatic time updates of the system if the system time and the time of a time server are too far apart. This is then indeed another routine.
rgds.
Rudy
Hello frens
as far as i used my centralized AAA as NTP server too, for supply all my RBs and Workstations with local IP address or Local DNS until now is great.... i started with Mikrotik's from v2.9.9 and now stable in v2.9.49 for all my router machines.
