[ntp:questions] time.windows.com

Evandro Menezes evandro at mailinator.com
Wed Oct 10 03:41:42 UTC 2007

On Oct 9, 6:42 pm, "David L. Mills" <mi... at udel.edu> wrote:

> Goaded by an earlier comment that the Windows default time server
> time.windows.com was flawed, I cranked up an association and here's what
> happened. First, it now does the client/server protocol correctly.
> Second, the packet drop rate is over 50 percent(!). Third, it is not a
> primary serer; it chimes a primary server at MIT synchronized by CDMA.
> Fourth, the roundtrip delay from Delaware is over 150 ms, which as the
> net flies is further than Alaska. The time is not too bad, about +-7 ms
> with jitter occasionally over 200 ms(!).

I myself gave up using it.  It often ends being tagged as a false

State	Remote		Refid	Stratum	Type		When	Poll	Reach	Delay	Offset	Jitter
x	time.windows.com		bonehed.lcs.mit.edu	2	Unicast server	182	64	134
114.799	48.332	4.480

Pathetic.  It beats me why NIST even lists it.


More information about the questions mailing list