Tag Info

New answers tagged


From the man page of ntptrace: ntptrace is a perl script that uses the ntpq utility program to follow the chain of NTP servers from a given host back to the primary time source. For ntptrace to work properly, each of these servers must implement the NTP Control and Monitoring Protocol specified in RFC 1305 and enable NTP Mode 6 packets.


Your firewall rules do not permit NTP. The line 0 0 ACCEPT tcp -- br1 * tcp dpt:123 is all very well, but NTP is a UDP service. Change the protocol, and things should get better. Your FORWARD rules are much more relaxed (essentially, permit any any) which is why the host inside the LAN syncs ...


When it start, ntpd check the time difference between your host and the remote NTP servers. If that difference is too big (10-15 mins, typically) it refuse to change anything. When you executed ntpdate you effectively use a one-shot, simpler SNTP implementation that bring your time within milliseconds of what ntpd itself would do. Now, if you restart ntpd ...


It seems that your ntp fail to sync due to excessive jitter / offset I suggest to try a different pool of ntp server near to your country. There is no need to obfuscate the ip in your status because these ip are public and well-documented servers If you machine run under VMware please check also ...


NT5DS Is the client protocol for Windows systems to retrieve time from a DC. Using this on your Windows machines does not prevent you from also enabling the NTP server on your Windows DCs, and configuring your Linux clients to use your DCs as a source of time using the NTP protocol. I configure my DCs using group policy to enable NTP so I can point my ...


The problem with tricking the computers is that, while the clock will appear correct, the actual times stored in the system will be one hour wrong. Eventually you will get a timezone update for your operating system, if it is still supported, and then the time errors will appear. This is how you deal with timezone updates generally (the right way): For ...


It seems as if your Ubuntu machine has some firewall rules blocking incoming NTP traffic. Can you issue the command iptables -F and re-try synching the Windows machine?


The Microsoft best practice for time keeping in a Windows domain is to configure the domain controller holding the PDC emulator role to get its time from a reliable source. By default, the rest of the machines in the domain will automatically sync up with the PDC emulator, either directly or second hand (or third hand, etc.).

Top 50 recent answers are included