[ntp:questions] Windows built-in SNTP/NTP clients
David L. Mills
mills at udel.edu
Thu Aug 14 17:13:42 UTC 2008
Mea culpa; I didn't mean to blame you. If all you want is to watch
antother NTP server or client, just spark up a configuration and set the
noselect bit. The problem with SNMP clients is that they fail to deal
with the complete set of data types, specifically floating double.
We did a project sevral years ago by implementing an SNMP agent
integrated with a NTP mode-6 agent that worked very well. But, I was not
in a position to maintain it and there were no other volunteers. Harlan
has a project doing that now; he is invited to report progress.
David J Taylor wrote:
> David L. Mills wrote:
>>Neither does Windows implement the mode-6 protocol nor does it conform
>>to the basic protocol. See the reference implementation documentation
>>about Windows issues. Also see the alternative workaround in
>>As the author of rfc1305 I say you misquote me. The mode-6 control and
>>monitoring protocol is an integral component of the specification; the
>>mode-7 protocol is intended as propietary. In any case the mode-6
>>protocol was defined and implmented well before SNMP.
>>An NTP MIB has been implemented by some manufacturers and another
>>proposed by the NTP working group, but neither is supported by the
>>reference implementation. Either MIB might be appropriate for
>>management purposes, but for complete monitoring and performance
>>evalutation the limitations of current SNMP clients make the mode-6
> It was Ryan and not I who wrote about mode-6 - I protest my innocence!
> I continue to recommend the reference implementation for Windows use, and
> I am grateful to those who continue to make a compiled version available.
> It would be good to see even a limited SNMP capability included in NTP -
> for monitoring only, not for control. Offset alone would be enough for
> me, although the ability to reproduce the ntpq -p display would be great.
More information about the questions