Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I had a hard time using NTP, and tried to find out what the issues were.
It appears that NTP works needs symetrical delays on the network. If the up/down delays become assymetrical, this ends up with an error :
example of NTP queries against a stratum 1 server :
no network traffic :
Reference ID: TS-2
Root Delay: 0 ms
Root Dispersion: 1,7242431640625 ms
Round Trip Delay: 35,1391 ms
Local Clock Offset: 2,92545 ms
heavy download:
Reference ID: TS-2
Root Delay: 0 ms
Root Dispersion: 1,89208984375 ms
Round Trip Delay: 108,8157 ms
Local Clock Offset: -32,88685 ms
heavy upload :
Reference ID: TS-2
Root Delay: 0 ms
Root Dispersion: 2,1209716796875 ms
Round Trip Delay: 66,39 ms
Local Clock Offset: 18,5578 ms
So depending on your network traffic during the queries, your local offset estimation can vary a lot , and NTPV4's feedback loop will go crazy.
If you want to start/stop the service, you need to run the monitor as administrator.
Just in case, here is my conf file :
# ref-clock drivers
server 127.127.22.1 minpoll 4 # PPS - serialpps.sys
server 127.127.20.1 minpoll 4 mode 18 prefer # NMEA serial port, 16 = 9600 baud, 2 = $GPGGA
# Other servers
server 0.fr.pool.ntp.org minpoll 10
server 1.fr.pool.ntp.org minpoll 10
server 2.fr.pool.ntp.org minpoll 10
server 3.fr.pool.ntp.org minpoll 10
###########################################################
#Section insert by NTP Time Server Monitor 20/12/2011