[ntp:questions] tardisnt unexpected WAN access
mayer at ntp.org
Tue Feb 17 04:21:21 UTC 2009
Mike -- Email Ignored wrote:
> On Tue, 17 Feb 2009 01:35:06 +0000, malayter wrote:
>> On Feb 16, 2009 6:49pm, Mike -- Email Ignored
>> <m_d_berger_1900 at yahoo.com> wrote:
>>> I didn't find an answer to my question there.
>> Tardis is commercial software. Presumably, you paid for it, and you can
>> receive vendor support. The vendor has an email address on thier site
>> for just such an eventuality:
>> support at kaska.demon.co.uk
>> If you can't get help there, I would suggest dropping Tardis entirely,
>> and start using the free Windows Time Service included with Windows XP.
>> Or use the reference implementation ntpd, which is more complicated, but
>> is also more precise and has many more features.
>> Hostorically, this list/newsgroup has genreally been about the network
>> protocol NTP itself, and the reference implementation of that protocol,
>> "ntpd". Other implementations are discussed as well, usually with
>> regards to protocol interoperability. Very few people here seem to use
>> Tardis, especially since Windows Time Service was introduced and
>> included with Windows 2000.
> Thanks for this information; I just e-mailed them. The reason I use
> Tardis is that I found that the WinXP ntp capability ran too
> infrequently, and the time drifted too much. I saw no way to
> change alter the WinXP time capability, and Tardis is a quick and
> easy solution.
If that is the case you are probably better off using the reference
implementation of ntp which disciplines your clock on an ongoing basis
by adjusting the frequency of the clock and not just sets the time. I
can't tell for sure but I believe that Tardis just sets the time and
does not adjust the clock frequency in order for it to remain in synch.
I remember contacting Chris over 10 years ago about Tardis but it was
not about that kind of detail.
More information about the questions