shanenin Posted April 13, 2007 Report Share Posted April 13, 2007 (edited) I have not been successfully able to sync my time on any of my windows machines a couple of weeks. This includes many client machines also. I get this error "An error occurred while synchronizing with time.windows.com" . This also happens if I choose "time.nist.gov". It is more of an annoyance, but I am baffeled to why it is happening. I do have a router, but I get the same problem when I connect my laptop directly into the cable modem. I will see what google turns up.since bypassing the router does not help, and all machines behave this way, I am leaning towards charter, my isp, being the problem.I do have some errors in my event log that said the time source was not available. I find it unlikely the windows.time.com along with time.nist.gov have been down for several weeks. Edited April 13, 2007 by shanenin Quote Link to post Share on other sites
mikex Posted April 13, 2007 Report Share Posted April 13, 2007 (edited) Are the machine updated, and do they have the 2007 DST patch?Mmine auto sync'ed at 9:33 this morning. Edited April 13, 2007 by mikex Quote Link to post Share on other sites
shanenin Posted April 13, 2007 Author Report Share Posted April 13, 2007 Three of my machines, plus all of my client machines fully patched. Quote Link to post Share on other sites
TheTerrorist_75 Posted April 13, 2007 Report Share Posted April 13, 2007 I get the same on my computer plus clients. All are fully updated. Quote Link to post Share on other sites
shanenin Posted April 13, 2007 Author Report Share Posted April 13, 2007 I get the same on my computer plus clients. All are fully updated.Do you know how long you have not been able to sync? Quote Link to post Share on other sites
TheTerrorist_75 Posted April 13, 2007 Report Share Posted April 13, 2007 I noticed it last week on a client's computer. I just tried mine. I have even change the time server. It could be my firewall blocks it. I usually pay no attention because my time always stays dead on. The only thing I haven't checked since the DST update is my Bios time. Quote Link to post Share on other sites
Falcon1986 Posted April 13, 2007 Report Share Posted April 13, 2007 Yes, this happens to me too sometimes when I try to manually synchronize.From a Neowin Forums thread, I found that using another time server works. They suggested the following:time-a.nist.gov (Maryland)time-b.nist.gov (Maryland)time-a.timefreq.bldrdoc.gov (Colorado)time-b.timefreq.bldrdoc.gov (Colorado)time-nw.nist.gov (Washington)utcnist.colorado.edu (Colorado)I tried the UCLA one and it worked perfectly: tick.ucla.eduJust copy/paste the server link into the "Server" field and click "Update Now" (Windows Date & Time Properties). It should be retained in the list the next time you go to manually synchronize. Quote Link to post Share on other sites
shanenin Posted April 13, 2007 Author Report Share Posted April 13, 2007 Thanks, adding a different server works, but I am still curious to why the others fail, in particular, time.windows.com. Quote Link to post Share on other sites
Falcon1986 Posted April 13, 2007 Report Share Posted April 13, 2007 Being the default server set in Windows it could be that it is too busy at the moment handling synchronizing requests. Quote Link to post Share on other sites
shanenin Posted April 13, 2007 Author Report Share Posted April 13, 2007 that may be, but after several weeks, you think they could increase the size of the server to be sufficient. Quote Link to post Share on other sites
Falcon1986 Posted April 13, 2007 Report Share Posted April 13, 2007 That's M$ for you... Quote Link to post Share on other sites
TheTerrorist_75 Posted April 13, 2007 Report Share Posted April 13, 2007 (edited) I added nist1-ny.WiTime.net and rebooted. The time syncronized with no problem during the reboot.I got rid of the original two time servers and added the following manually to the registry.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DateTime\ServersCreate the new string values.0 ntp.nasa.gov1 time-a.nist.gov2 time-b.nist.gov3 nist1-ny.WiTime.net4 time.twc.weather.com Edited April 13, 2007 by TheTerrorist_75 Quote Link to post Share on other sites
sethook Posted April 14, 2007 Report Share Posted April 14, 2007 Added info..... Quote Link to post Share on other sites
jcl Posted April 14, 2007 Report Share Posted April 14, 2007 Thanks, adding a different server works, but I am still curious to why the others fail, in particular, time.windows.com.time.windows.com is broken. Really broken. It's over 100 seconds off. The Windows NTP client should refuse to synchronize with it.time.nist.gov just takes forever to respond. It's probably overloaded.Everyone should be using the pool. The pool is your friend. Quote Link to post Share on other sites
shanenin Posted April 14, 2007 Author Report Share Posted April 14, 2007 Thanks, adding a different server works, but I am still curious to why the others fail, in particular, time.windows.com.time.windows.com is broken. Really broken. It's over 100 seconds off. The Windows NTP client should refuse to synchronize with it.time.nist.gov just takes forever to respond. It's probably overloaded.Everyone should be using the pool. The pool is your friend.You would think it would be an easy fix. Quote Link to post Share on other sites
jcl Posted April 14, 2007 Report Share Posted April 14, 2007 You would think it would be an easy fix.*shrug* No one seems to know what's happening with time.windows.com. The service is hosted by Akamai; it's possible that Microsoft can't fix it. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.