I don't know why microsoft was not able to fix that in the last decade, because this can be a real pain in the neck, especially if one has to rely on exact time keeping.
Anyway today I've found this link:
Configure a manual time source for a selected client computer
In essence it explains two things:
- How to test if another computer (on the LAN) can be used as time server:
w32tm /stripchart /computer:target /samples:n /dataonly
where target is the name or IP of the time server and n the number of times to query it - How to set another computer (on the LAN) as time server:
w32tm /config /manualpeerlist:peers /syncfromflags:manual /update
Actually it is set up as peer and does not appear in the list of servers (in the property of the clock), but
w32tm /query /peers
lists it, if the call to w32tm /config succeeded. Note that it must be run as administrator!
peers may contain a list of names/IP addresses in a quotes string with space as deliminator (e.g. "time1 time2 time3")
As time server I use a linux box with openntpd (does not listen to connections by default, so make sure to enable that in /etc/openntpd if you want to see it).
Now I'll have to see if it actually works...
Keine Kommentare:
Kommentar veröffentlichen