It looks like the problem I’m running into is when I run “w32tm /resync /rediscover”. It gives me the error “The computer did not resync because no time data was available”, even after I follow the standard documentation to set the NTP server and to restart services. Event log shows it’s trying to connect to pool.ntp.org but it doesn’t receive a response.
When I do this from my local PC it works. Perhaps there is something blocking it at the client site? Question is what…. Any thoughts? From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, February 2, 2017 3:08 PM To: [email protected] Subject: [NTSysADM] RE: can't set NTP time source on PDC This is my old, but still valid, blog post on this topic: http://theessentialexchange.com/blogs/michael/archive/2010/01/29/a-brief-history-of-time-ok-ok-let-s-go-with-quot-an-introduction-to-the-windows-time-service-quot.aspx From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jimmy Tran Sent: Thursday, February 2, 2017 9:11 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] can't set NTP time source on PDC Hi Guys, I’ve been having trouble changing the Windows time source to any outside NTP server. It is current set to local but the time is off so I wanted to set it to an outside time source. When I run “w32tm /query /status”, it shows (source name: “LOCL”). So now I run “w32tm /config /syncfromflags:manual /manualpeerlist:pool.ntp.org /reliable:yes /update” and it completes successfully. I’ll restart the time service and do a query again but it still shows LOCL. I am doing this on the PDC on the domain. I’ve tried a reboot and even unregistering w32tm but nothing helps. I’m out of ideas. Thanks, JT
