Comments on: Hotfix Lets W32time Sync with Very High Precision NTP Servers

By: Rick

Rick — Thu, 29 May 2008 07:20:46 +0000

Mark, we haven’t applied the update so I don’t know what caused the errors all of a sudden. I did check to see that we have “later” versions of the hotfix files. Since I added the /update to the config statement it is working fine. Thanks.

By: Mark Berry

Mark Berry — Fri, 23 May 2008 08:54:53 +0000

Rick, have you applied the hotfix? If the servers you are using recently upgraded to very high precision, that could explain the sudden errors.

By: Rick

Rick — Fri, 23 May 2008 08:16:09 +0000

Just an update. I addeed /update to the command…

w32tm /config /manualpeerlist:”206.112.100.146,0×8 69.25.96.13,0×8″ /syncfromflags:MANUAL /reliable:yes /update

and it works better now.

By: Rick

Rick — Fri, 23 May 2008 05:55:29 +0000

I am also getting events 38 and 47 with many different time servers on my 2003 server. This just started happening last week. I tried using…

w32tm /config /manualpeerlist:”206.112.100.146,0×8 69.25.96.13,0×8″ /syncfromflags:MANUAL /reliable:yes

which is the last setting you are using Mark with IPs instead of names. Now, when I do a resync, I get “the computer did not resync because no time data was available. I have used IPs before so it’s not that. What has changed the past week or so?

By: Mark Berry

Mark Berry — Tue, 13 May 2008 09:27:16 +0000

A few times this past week, a server has been reporting that it couldn’t get time from nist1.symmetricom.com (W32Time Warning Event ID 47). I found this helpful link of which servers are busy:

http://tf.nist.gov/tf-cgi/servers.cgi

nist1.symmetricom.com is not listed as busy, but the other server mentioned in the original article, time-b.timefreq.bldrdoc.gov, is listed as VERY busy. I also see that there is a server in Los Angeles, even closer to my San Diego location. So I’m changing my time servers using these commands:

w32tm /config /manualpeerlist:”nist1-la.WiTime.net,0×8 nist1.symmetricom.com,0×8″ /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

By: Mark Berry

Mark Berry — Wed, 07 Nov 2007 14:28:54 +0000

Thanks for that link. In this context, “very high precision” just means any server with a precision less than -30 (since it’s negative, a value less than -30, e.g. -31, indicates higher precision). Probably more likely in the NIST/Level 1 servers, but theoretically any server could return very high precision.

By: pcr

pcr — Wed, 07 Nov 2007 00:49:56 +0000

I’m not sure if “very high precision” translates to the Level 1 and Level 2 servers. At any rate, here’s a long list of servers.

http://support.microsoft.com/kb/262680