[ntp:questions] Re: ntp client: keep all servers at startup

mayer mayer at gis.net
Sat Jun 18 02:13:58 UTC 2005

----- Original Message Follows -----
> * Martin Burnicki <martin.burnicki at meinberg.de>
> | Which operating system are you running?
> The final install will run on Windows 2000, not sure whether the
> machines have the latest service packs.
> | Which version of NTP are you running?
> Binary NTP distribution ntp-4.2.0a.
> | Are there some messages in the syslog after NTP has started?
> Nothing but the usual startup messages.
> | Under WinNT there's a bug that the NTP service is unable to mobilize
> | an associaton for a NTP server if that server is not online when the
> | client starts up: http://bugs.ntp.isc.org/show_bug.cgi?id=450
> This sounds as if ntpd does not work correctly on NT even if the
> server is reachable.  This is not the problem here.  If the server is
> reachable at client startup, ntp works ok.  It's only when the client
> is started _before_ the server that the client does not reconsider the
> server.

That bug was specific to NT 4.0 from what Heiko says. There is a Windows
handle issue that I'm working on (see bug #451) but I'm not sure whether
or not it affects this. I understand the bug #451 problem and I'm
researching possible solutions but it won't be simple.


> But as I said, there are work-arounds, and the problem is currently
> low-priority.
> Thanks
> R'
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions

More information about the questions mailing list