Richard B. Gilbert wrote:
> David J Taylor wrote:
>> Richard B. Gilbert wrote:
>> []
>>> Have you considered reinstalling Windows XP?
>>
>> No, because this is a Vista testbed, and the objective is to get NTP
>> working here as well as it does on all the other Windows PC systems
>> (NT4, 2000, XP e
David J Taylor wrote:
> Richard B. Gilbert wrote:
> []
>> Have you considered reinstalling Windows XP?
>
> No, because this is a Vista testbed, and the objective is to get NTP
> working here as well as it does on all the other Windows PC systems (NT4,
> 2000, XP etc.).
>
> David
>
>
My cond
Steve Kostecke <[EMAIL PROTECTED]> writes:
>On 2008-06-17, Anton Persson A <[EMAIL PROTECTED]> wrote:
>> The poll interval is 64 to 1024, seconds. ntpd starts up, locks on
>> target, stays synchronized for a while, then we pull the plug.
>What are you trying to prove by "pulling the plug"?
>> T
Richard B. Gilbert wrote:
[]
> Have you considered reinstalling Windows XP?
No, because this is a Vista testbed, and the objective is to get NTP
working here as well as it does on all the other Windows PC systems (NT4,
2000, XP etc.).
David
___
que
Hal Murray wrote:
> [drift > 500 ppm]
>
>> It's almost certainly a hardware problem. Ntpd is telling you that the
>> clock is gaining, or losing, more than about 43 seconds (500 parts per
>> million) per day. 500 PPM is the maximum that ntpd can handle.
>
> It could easily be a software screw
David J Taylor wrote:
> David Woolley wrote:
>> David J Taylor wrote:
>>> Yesterday I undated my Windows Vista system to Service Pack 1, and
>>> whilst NTP initially appeared to work correctly, it soon developed
>>> an oscillating state. See:
>>>
>>> http://www.satsignal.eu/ntp/NTP-on-Windows-Vi
David Woolley wrote:
> David J Taylor wrote:
>> Yesterday I undated my Windows Vista system to Service Pack 1, and
>> whilst NTP initially appeared to work correctly, it soon developed
>> an oscillating state. See:
>>
>> http://www.satsignal.eu/ntp/NTP-on-Windows-Vista.html
>
> They look like da
David Woolley wrote:
[]
> Can I just confirm that this system is connected to its time sources
> only by ethernet, and that that ethernet has low latency drivers?
I meant to comment that it has no special Ethernet drivers, just what
comes with Windows Vista. But as the steps are sometimes 50msec
[drift > 500 ppm]
>It's almost certainly a hardware problem. Ntpd is telling you that the
>clock is gaining, or losing, more than about 43 seconds (500 parts per
>million) per day. 500 PPM is the maximum that ntpd can handle.
It could easily be a software screwup.
Unless you know it works on
David J Taylor wrote:
> Yesterday I undated my Windows Vista system to Service Pack 1, and whilst
> NTP initially appeared to work correctly, it soon developed an oscillating
> state. See:
>
> http://www.satsignal.eu/ntp/NTP-on-Windows-Vista.html
They look like damped oscillations, so the qu
Yesterday I undated my Windows Vista system to Service Pack 1, and whilst
NTP initially appeared to work correctly, it soon developed an oscillating
state. See:
http://www.satsignal.eu/ntp/NTP-on-Windows-Vista.html
Could one of the NTP experts suggest why initial stability should
degenerate
11 matches
Mail list logo
