On Sep 24, 11:50 am, Ryan Malayter <[EMAIL PROTECTED]> wrote:

> You can also just mointor from the Windows client, and run the built
> in windows command 'w32tm' in a loop in a batch file and record the
> results for later analysis, but I have no idea how good the data would
> actually be:
>   C:\>w32tm /monitor /computers:0.us.pool.ntp.org


Actually, there's no need for the batch file, w32tm has the
"stripchart" functionality built-in:
C:\>w32tm /stripchart /computer:1.us.pool.ntp.org /period:5 /dataonly
Tracking 1.us.pool.ntp.org [69.16.152.68].
The current time is 9/24/2007 11:55:05 AM (local time).
11:55:05, +00.0013441s
11:55:10, +00.0001709s
11:55:15, +00.0021731s
11:55:20, -00.0003201s
11:55:25, -00.0002975s

This tool is just doing an actual ntp query every period, so it is
probably not the most accurate measure of statistics, but it is
something. This particular server is a Windows 2003 Server SP2 domain
controller with a few tweaks to w32time. As you can see, it does
fairly well in terms of offset, staying within 8 ms of zero typically.

Here is the regiostry configuration, only a few of these paramters are
tweaked from defaults, and some should not be modified at all:

U:\>w32tm /dumpreg /subkey:Parameters

Value Name       Value Type          Value Data
--------------------------------------------------

type             REG_SZ              NTP
ntpserver        REG_SZ              0.us.pool.ntp.org,0x8
1.us.pool.ntp.org,0x8 2.us.pool.ntp.org,0x8
ServiceMain      REG_SZ              SvchostEntry_W32Time
ServiceDll       REG_EXPAND_SZ       C:\WINNT\system32\w32time.dll


U:\>w32tm /dumpreg /subkey:Config

Value Name                Value Type          Value Data
-----------------------------------------------------------

LastClockRate             REG_DWORD           156250
MinClockRate              REG_DWORD           155860
MaxClockRate              REG_DWORD           156640
FrequencyCorrectRate      REG_DWORD           4
PollAdjustFactor          REG_DWORD           5
LargePhaseOffset          REG_DWORD           50000000
SpikeWatchPeriod          REG_DWORD           900
HoldPeriod                REG_DWORD           5
LocalClockDispersion      REG_DWORD           10
EventLogFlags             REG_DWORD           2
PhaseCorrectRate          REG_DWORD           7
MinPollInterval           REG_DWORD           6
MaxPollInterval           REG_DWORD           10
MaxNegPhaseCorrection     REG_DWORD           -1
MaxPosPhaseCorrection     REG_DWORD           -1
UpdateInterval            REG_DWORD           100
AnnounceFlags             REG_DWORD           5
MaxAllowedPhaseOffset     REG_DWORD           300

_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions

Reply via email to