In article <6e430aac.0306230119.6d3944ee@posting.google.com>,
fbaralli@... wrote:
> running WinNT4 with ntpd 4 as peer.
You mean client. It should have a server, not a peer line in its ntp.conf.
Peer is strictly for reversible connections.
> Both computers are collecting data from different sources so the need
> to be synchronized with a jitter smaller than 10ms.
Your problem will be NT, not NTP. Unless you are using the special
techniques used by the latest NTP ports to NT (even some early v4 ones may
not have these), and also using them in your application, you should
expect a clock resolution of the order of 20ms. The implemented
clock resolution in NT is a lot less than that in the architectural
specification.
If you can't tolerate more than 10ms ever, NT is far too complex to make
such guarantees, even if you do interpolate clock ticks. |