SNTP Client can't sync time

andy2010 · Fri Jan 27, 2012 3:19 am

Hello,

i can't get a SXT 5HnD to sync the time with our Windows 2008 R2 DC/NTP Server.

my config:
[admin@sxt_bauer] /system ntp client> export
# jan/02/1970 00:34:23 by RouterOS 5.12
# software id = E85M-V9K9
#
/system ntp client
set enabled=yes mode=unicast primary-ntp=192.168.40.5 secondary-ntp=0.0.0.0

debug logging shows always:
00:35:42 ntp,debug,packet sending to 192.168.40.5 NTP packet (48 bytes)
00:35:42 ntp,debug,packet VN=4
00:35:42 ntp,debug,packet Mode=3 (Client)
00:35:42 ntp,debug,packet TransmitTimestamp=83abd85eed423d92
00:35:42 ntp,debug Wait for 16 seconds before sending next message

My topology is like this

NTP-Server 192.168.40.5 <-> Other Router 192.168.40.253 and 192.168.41.253 <-> SXT 192.168.41.250

I setup static and OSPF routing, ping works fine. Via Packet Sniffer on the SXT i see that a packet is beeing sent, but on the "Other Router" i don't receive anything.
I disabled all Firewall/NAT Rules.

Regards

Andy

omega-00 · Fri Jan 27, 2012 4:00 pm

You need to look at the network connectivity itself.

Can 192.168.41.250 ping 192.168.40.5 currently? If not then it's likely either 192.168.41.250 doesn't know how to route to 192.168.40.5 OR that 192.168.40.5 doesn't know how to route back to 192.168.41.250 (hint, each should be passing via its closest respective address on the middle router).

andy2010 · Fri Jan 27, 2012 10:12 pm

You need to look at the network connectivity itself.

Can 192.168.41.250 ping 192.168.40.5 currently? If not then it's likely either 192.168.41.250 doesn't know how to route to 192.168.40.5 OR that 192.168.40.5 doesn't know how to route back to 192.168.41.250 (hint, each should be passing via its closest respective address on the middle router).

Ping from 192.168.41.250 (=ether1 interface) to 192.168.40.5 is possible

[root@sxt_bauer] > ping address=192.168.40.5 interface=ether1
HOST SIZE TTL TIME STATUS
192.168.40.5 56 127 0ms
192.168.40.5 56 127 0ms
192.168.40.5 56 127 1ms

[root@sxt_bauer] > /tool traceroute 192.168.40.5
# ADDRESS RT1 RT2 RT3 STATUS
1 192.168.41.253 2ms 1ms 0ms
2 192.168.40.5 2ms 1ms 1ms

Sun Jan 29, 2012 3:20 am

Odd - I'm getting the same! (RB493G v5.5) Except mine is trying to talk to another MT, an RB1100 on v5.5 E.g.

NTP.png

andy2010 · Mon Jan 30, 2012 1:05 am

Odd - I'm getting the same! (RB493G v5.5) Except mine is trying to talk to another MT, an RB1100 on v5.5 E.g.
NTP.png

your log says "ignoring received NTP Packet", but i don't receive any packet at all

i also tried a different ntp server (Debian, Source: ntp (1:4.2.6.p2+dfsg-1) Version: 1:4.2.6.p2+dfsg-1+b1) but same result:

06:38:32 ntp,debug,packet sending to 192.168.40.5 NTP packet (48 bytes)
06:38:32 ntp,debug,packet     VN=4
06:38:32 ntp,debug,packet     Mode=3 (Client)
06:38:32 ntp,debug,packet    TransmitTimestamp=83aed068a970e6f2
06:38:32 ntp,debug Wait for 16 seconds before sending next message
06:38:48 ntp,debug Wait for 16 seconds before sending next message
06:39:04 ntp,debug,packet sending to 192.168.40.4 NTP packet (48 bytes)
06:39:04 ntp,debug,packet     VN=4
06:39:04 ntp,debug,packet     Mode=3 (Client)
06:39:04 ntp,debug,packet    TransmitTimestamp=83aed088a7bc3c5b
06:39:04 ntp,debug Wait for 16 seconds before sending next message
06:39:20 ntp,debug Wait for 16 seconds before sending next message
06:39:36 ntp,debug,packet sending to 192.168.40.5 NTP packet (48 bytes)
06:39:36 ntp,debug,packet     VN=4
06:39:36 ntp,debug,packet     Mode=3 (Client)
06:39:36 ntp,debug,packet    TransmitTimestamp=83aed0a8a7b99d45
06:39:36 ntp,debug Wait for 16 seconds before sending next message
06:39:52 ntp,debug Wait for 16 seconds before sending next message
06:40:08 ntp,debug,packet sending to 192.168.40.4 NTP packet (48 bytes)
06:40:08 ntp,debug,packet     VN=4
06:40:08 ntp,debug,packet     Mode=3 (Client)
06:40:08 ntp,debug,packet    TransmitTimestamp=83aed0c8a7d5fdcd
06:40:08 ntp,debug Wait for 16 seconds before sending next message
06:40:24 ntp,debug Wait for 16 seconds before sending next message
06:40:40 ntp,debug,packet sending to 192.168.40.5 NTP packet (48 bytes)
06:40:40 ntp,debug,packet     VN=4
06:40:40 ntp,debug,packet     Mode=3 (Client)
06:40:40 ntp,debug,packet    TransmitTimestamp=83aed0e8a9357603
06:40:40 ntp,debug Wait for 16 seconds before sending next message
06:40:56 ntp,debug Wait for 16 seconds before sending next message
06:41:12 ntp,debug,packet sending to 192.168.40.4 NTP packet (48 bytes)
06:41:12 ntp,debug,packet     VN=4
06:41:12 ntp,debug,packet     Mode=3 (Client)
06:41:12 ntp,debug,packet    TransmitTimestamp=83aed108a7863bee
06:41:12 ntp,debug Wait for 16 seconds before sending next message
06:41:28 ntp,debug Wait for 16 seconds before sending next message
06:41:44 ntp,debug,packet sending to 192.168.40.5 NTP packet (48 bytes)
06:41:44 ntp,debug,packet     VN=4
06:41:44 ntp,debug,packet     Mode=3 (Client)
06:41:44 ntp,debug,packet    TransmitTimestamp=83aed128a8476f2a
06:41:44 ntp,debug Wait for 16 seconds before sending next message

if i use 192.168.40.5 as dns-server

[root@sxt_bauer] /ip dns> print
                servers: 192.168.40.5
  allow-remote-requests: yes
    max-udp-packet-size: 512
             cache-size: 2048KiB
          cache-max-ttl: 1w
             cache-used: 9KiB

and query my SXT for an address, it's working. so udp communication between that hosts definitly works.

Mon Jan 30, 2012 1:22 am

In my case, I pretty much think this is a bug, as the error message is that the client is getting a message from the server that the time is not synchronised, when it is!

For you, if you're using a Microsoft server, there are some tweaks you have to make in the Registry. Search the forums, there are references on what to change.

andy2010 · Mon Jan 30, 2012 1:28 am

For you, if you're using a Microsoft server, there are some tweaks you have to make in the Registry. Search the forums, there are references on what to change.

I already checked this. My HP Procurve Switch, some OpenWRT-Router and my iPhone NTP Client working very well with either the Microsoft NTP Server and the Debian one.

Mon Jan 30, 2012 1:30 am

then, bottom line.. run packet sniff and analyse data with wireshark, something is going wrong here, if you think there is nothing blocking it, why is it not getting reply?

changeip · Mon Jan 30, 2012 4:03 am

it a stratum problem im guessing. RouterOS wont use a Microsoft stratum value - too high.

Mon Jan 30, 2012 4:11 am

This guy says he is not even getting a return packet from the server? So the client is not even seeing any reply?

andy2010 · Wed Feb 01, 2012 11:26 pm

i also tried it with some public server, but i just gave it up. no packet arrives at the next hop address. i don't know whats wrong with my network.

i will use another SXT in a different network and with it's own internet connection to sync the time with a public ntp server while providing them to the other devices.

SNTP Client can't sync time

SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Re: SNTP Client can't sync time

Who is online