Brown, Ken F. wrote: > > The NTP.CONF file for the 3 time servers (with GPS devices) have lines > similar to below (different com ports involved): > > server 127.127.1.0 #allow synchronization with local > clock > fudge 127.127.1.0 stratum 12 refid LOCAL
Delete these two lines, especially from the machine with no GPS source, but also from the others unless and until you fully understand what they and have a specific reason for adding them. The local clocks on the machines with the reference clocks are probably not your current problem. That on the fourth machine might be part of it. If you still feel you need local clocks, you should use a more recent ntpd and make at least the first three machines orphan mode, instead, and, if not orphan mode, set the fourth machine at least two stratums further from the root. > > # connected to COM1 - use 127.127.29.1 > # connected to COM2 - use 127.127.29.2 > server 127.127.29.2 prefer > fudge 127.127.29.2 stratum 0 According to the documentation, there should be a fudge time1, although this will create a systematic error, resulting in all being in error by the same amount. I would advise calibrating time1, as Windows time keeping is poor, and you may need additional compensation for Windows. You don't need to use prefer on the fourth machine, unless a specific one of the three machines really is preferred; an un-preferred local clock is only used when there are no external sources. > > #And then have the following 'peer' statements: > > peer time.localdomain.com prefer iburst There should be at most one preferred source, and in this case, if you user prefer at all, that should be the reference clock. This probably is your main problem. I'm not certain, but I think that the prefers might also compromise the external servers, although they may already be compromised by the failure to correctly fudge out the systematic time error form the Pallisades. > peer time2.localdomain.com prefer iburst > peer time3.localdomain.com prefer iburst > Server time4.localdomain.com time4 should not be listed in this configuration at all, and time4 should have server lines for the others. (You may need to use peer everywhere if you want to include time 4 in a 4 way orphan configuration, but I'm not sure what benefit you would get from that.) > > #(and the peer line is commented out if it is itself - i.e. if this is > the ntp.conf file > #from time2, then the time2 peer line is commented out) > > #There are additional 'server' lines to internet time sources, like: > > #server 69.25.27.172 #ntp1.connectiv.com > server 129.6.15.29 #time-b.nist.gov > server 129.6.15.28 #time-a.nist.gov > #server 66.92.68.246 #time.keneli.org > #server 209.51.161.238 #clock.nyc.he.net > > #And they are slightly different on all 3 'peer' servers (to hit > different internet time sources) _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
