Hi! You have landed here most probably while searching for solution to your NTP synchronization problem, right? For your comfort, this page is excellent to start with. We’ve provided a list of the most common causes of NTP time sync troubles. Check which one applies yours and follow the proposed steps to make time service successful. We hope you will find these guidelines helpful!
Firewall Port Opening :
NTP Port is UDP 123
Control Panel -> Windows Firewall->Advanced settings. If the firewall is on, one has to enable Inbound and Outbound Rules for “Specific local ports” in our case UDP, port 123.
NTP From Cmdlet
- To make any w32time changes in command line window one has to run cmd program as administrator
- enter the following commands
w32tm /config /manualpeerlist:[server],0x8 /syncfromflags:MANUAL
The actual IP address of the NTP server or its host name must be entered instead of [server].
The flag “0x8” forces w32time not to send “symmetric active” packets but normal “client” requests which the NTP server replies to as usual.Then the following command can be used to immediately make the changes effective:
w32tm /config /update
If this command has completed successfully your system clock has synchronized to the given NTP server. To check it open a Date and Time window (click “time” icon in the lower right corner of the desktop) -> Change date and time settings -> Internet Time. You should see something similar to Figure 6.
Alternatively, the w32time service can be restarted:
net stop w32time
net start w32time
net time /querysntp
can be used to check the configuration. The output should look similar to the line below:
The current SNTP value is:[server],0x8
If the w32time service is restarted it sends immediately a request to the NTP server. Additionally, the command:
can be used to let w32time send a request.
Check if w32time service is running:
Open Run > services.msc>windows time, its started. If want change manual/automatic as per requirement.