Danny Mayer schrieb:
Eugen COCA wrote:
Hi all,
I've tested a W2k3 box time synchronization by setting the server using
the command line:
net time /setsntp:time.usv.ro
net stop w32time
net start w32time
The fact that you had to stop and start the service indicates how badly
the net time interface was written. It doesn't take much to write code
update information in the registry and then notify the service to go
reread it and act accordingly.
Is this possible with ntpd? I mean, applying changes to ntp.conf and
then tell the daemon/service to re-read its configuration file? I would
really love to see such a feature ... :-)
As a result, when checking another server (i.e. time.microsoft.com)
from the list box, I obtain an timeout error messages. Only the server
time.usv.ro works fine. The experiment is the same with any other ntp
server (I've tried many public servers).
Before typing the "net time ..." command all servers from the initial
list (time.microsoft.com; time.nist.gov, etc.) worked fine.
If it was working before why wouldn't it work now? I know, that's a
question for Microsoft.
They are still trying to figure out why it worked ;-)
Best regards,
Heiko
Danny
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
--
Meinberg radio clocks: 25 years of accurate time worldwide
MEINBERG Radio Clocks
www.meinberg.de
Stand alone ntp time servers and radio clocks based on GPS, DCF77 and
IRIG. Rackmount and desktop versions and PCI slot cards.
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
