Time.windows.com is an extremely unreliable time source. I have seen timeouts when using that for weeks at a time, followed by one or two of successful updates, then several more weeks of timeouts. Pool.ntp.org is extremely reliable. I have never seen a sync request time out since switching to that source.
-----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Thursday, March 25, 2010 10:23 AM To: NT System Admin Issues Subject: Re: NTP, VM's, and domains... Oh My! On Thu, Mar 25, 2010 at 11:06 AM, Michael Tellson <[email protected]> wrote: > And never user time.windows.com (the default). Why not? I don't currently have anything using time.windows.com except a few stand-alone PCs at side clients, so it doesn't really matter to me, but I'm curious. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
