The error is:

  ERROR_TIMEOUT                                                 winerror.h
# This operation returned because the timeout period expired.

It means it can't contact pool.ntp.org. 

For say "one minute" disable the windows firewall. See if you can do the 
"resync rediscover". If it works, turn back on the windows firewall, and enable 
the exceptions in the firewall that someone disabled.

If it doesn't work, then it's upstream. Whether your local firewall/router or 
your ISP.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Jimmy Tran
Sent: Friday, February 3, 2017 6:46 PM
To: [email protected]
Subject: RE: [NTSysADM] RE: can't set NTP time source on PDC

Sorry, I was using a different app, not telnet that was querying udp. I guess 
wireshark is the next step. Thanks for the tip.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Kurt Buff
Sent: Friday, February 3, 2017 3:39 PM
To: ntsysadm <[email protected]>
Subject: Re: [NTSysADM] RE: can't set NTP time source on PDC

Um, telnet only works over TCP, not UDP. I don't think you were testing what 
you thought you were testing.

You could try this:
https://github.com/besimorhino/powercat
if you want to test UDP

Or, more likely (if you don't want to install Wireshark on your
machine) you could use the trace functionality in netsh to verify what packets 
are sent and received:
https://technet.microsoft.com/en-us/library/dd878517(v=ws.10).aspx

Kurt

On Fri, Feb 3, 2017 at 3:13 PM, Jimmy Tran <[email protected]> wrote:
> I get errors when I run that: 15:05:47 error: 0x800705B4. I did check 
> that I can telnet into pool.ntp.org on port 123 UDP so the firewall 
> isn’t blocking it.
>
>
>
> I’m at a loss…..
>
>
>
>
>
>
>
> From: [email protected]
> [mailto:[email protected]]
> On Behalf Of Charles F Sullivan
> Sent: Friday, February 3, 2017 8:36 AM
> To: [email protected]
> Subject: RE: [NTSysADM] RE: can't set NTP time source on PDC
>
>
>
> Good point. To that end, what happens if you try “w32tm /stripchart 
> /computer:pool.ntp.org” from the PDC?
>
>
>
> From: [email protected]
> [mailto:[email protected]]
> On Behalf Of Michael B. Smith
> Sent: Friday, February 3, 2017 11:23 AM
> To: [email protected]
> Subject: [NTSysADM] RE: can't set NTP time source on PDC
>
>
>
> That sounds like a firewall issue. And probably not the Windows firewall.
>
>
>
> From: [email protected]
> [mailto:[email protected]]
> On Behalf Of Jimmy Tran
> Sent: Friday, February 3, 2017 10:50 AM
> To: [email protected]
> Subject: [NTSysADM] RE: can't set NTP time source on PDC
>
>
>
> 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-bri
> ef-history-of-time-ok-ok-let-s-go-with-quot-an-introduction-to-the-win
> dows-time-service-quot.aspx
>
>
>
>
>
> From: [email protected]
> [mailto:[email protected]]
> On Behalf Of Jimmy Tran
> Sent: Thursday, February 2, 2017 9:11 AM
> To: [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


Reply via email to