[time-nuts] Setting Windows XP clock.
albertson.chris at gmail.com
Sun Jul 13 15:10:28 EDT 2014
I did see some retries going to time.windows.com.
I'd suggest changing to 0.north-america.pool.ntp.org if you live in
It took several seconds to get time form time.windows.com but
0.north-america.pool.ntp.org had no delay.
On Sun, Jul 13, 2014 at 12:00 PM, Hal Murray <hmurray at megapathdsl.net> wrote:
> albertson.chris at gmail.com said:
>> 1) It is set to use an NTP server called "time.windows.com"
>> to set the clock.
>> 3) The above is working as well as it has ever worked.
>> Nothing has changed at Microsoft's end.
> It may be more complicated than that.
> time.windows.com is a cname for time.microsoft.akadns.net
> That's Akami's DNS magic to give you the closest/best server.
> I'm in Silicon Valley. I get either 22.214.171.124 or 126.96.36.199
> 188.8.131.52 only works some of the time. It's not random packet drops. It
> drops out for a while, then recovers.
> 184.108.40.206 is similar, but seems to work more often, at least from my
> hacking of the last few minutes.
> Both IP ranges are assigned to Microsoft. Neither responds to pings.
> You will probably see different results if you are in a different location.
> These are my opinions. I hate spam.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
Redondo Beach, California
More information about the time-nuts