Re: NTP client on Windows platform provides less accurate results then on the UNIX or Linux. Why?
- From: mayer@xxxxxxxxxxx (Danny Mayer)
- Date: Sun, 2 Apr 2006 03:43:10 GMT
Ry wrote:
How often are these boxes restarted? NTP seems to take a 8 hours or
more to really "settle". If you're rebooting the Windows machines
frequently (and you *should* be at least once per month to get MS
security patches),
Why? There is very rarely a need to reboot a Windows machine. 99% of all
hotfixes should not require a reboot. I probably reboot once every 3
months. Only badly written installers require reboots.
NTP will always perform worse in comparison with a
Linux box that is always on.
Most people running NTP on Windows would disagree with you.
If your hardware has any power-management features enabled (Intel
SpeedStep, AMD CoolNQuiet, etc.), that would do it. Others may have
mentioned disabling ACPI in the BIOS, but you will also want to
checkDevice Manager to make sure you don't have speed-throttling "CPU
drivers" or other "system devices" installed or activated.
That's almost unavoidable and is not just Windows.
Finally, the WinXP firewall or other software firewall could be adding
small delays if it is enabled and CPU utilization isn't genreally low.
So could any host-based intrustion prevention, anti-spyware, or
antivirus software that scans live network connectios for threats
(e.g.Symantec Client Security). Also make sure the multimedia timers
are enabled during setup of NTPd.
All systems have firewalls, routers, switches, etc. There's no real
difference here.
Danny
_______________________________________________
questions mailing list
questions@xxxxxxxxxxxxxxxxx
https://lists.ntp.isc.org/mailman/listinfo/questions
.
- Follow-Ups:
- Prev by Date: Re: How broadcast working?
- Next by Date: Re: offset values from ntpq and ntptrace
- Previous by thread: Re: How broadcast working?
- Next by thread: Re: NTP client on Windows platform provides less accurate results then on the UNIX or Linux. Why?
- Index(es):
Relevant Pages
|