Question: There is no “Internet Time” tab in the date/time dialog box on Windows Server, is it still possible to configure the server to use NTP? If so, how?
Answer: Yes, as far as I know, you have to do this from the command prompt. Here’s how:
net stop w32time w32tm /config /syncfromflags:manual /manualpeerlist:"time-a.nist.gov, time-b.nist.gov, time-c.nist.gov, time-d.nist.gov" w32tm /config /reliable:yes net start w32time
That will configure the time service to sync with the list of servers (time-*.nist.gov in the above example) and it also tells the server that it is a reliable time source that client machines on your domain can sync with. In other words, these steps configure the server as an NTP server in addition to configuring it to sync with Internet time servers. If you do not want that functionality, do not run the following command:
w32tm /config /reliable:yes
If you need to view the NTP configuration, type the following command from a prompt:
w32tm /query /configuration
This produces the following output:
[Configuration] EventLogFlags: 2 (Local) AnnounceFlags: 5 (Local) TimeJumpAuditOffset: 28800 (Local) MinPollInterval: 6 (Local) MaxPollInterval: 10 (Local) MaxNegPhaseCorrection: 172800 (Local) MaxPosPhaseCorrection: 172800 (Local) MaxAllowedPhaseOffset: 300 (Local) FrequencyCorrectRate: 4 (Local) PollAdjustFactor: 5 (Local) LargePhaseOffset: 50000000 (Local) SpikeWatchPeriod: 900 (Local) LocalClockDispersion: 10 (Local) HoldPeriod: 5 (Local) PhaseCorrectRate: 7 (Local) UpdateInterval: 100 (Local) [TimeProviders] NtpClient (Local) DllName: C:\Windows\system32\w32time.dll (Local) Enabled: 1 (Local) InputProvider: 1 (Local) AllowNonstandardModeCombinations: 1 (Local) ResolvePeerBackoffMinutes: 15 (Local) ResolvePeerBackoffMaxTimes: 7 (Local) CompatibilityFlags: 2147483648 (Local) EventLogFlags: 1 (Local) LargeSampleSkew: 3 (Local) SpecialPollInterval: 3600 (Local) Type: NTP (Local) NtpServer: time-a.nist.gov, time-b.nist.gov, time-c.nist.gov, time-d.nist.gov (Local) NtpServer (Local) DllName: C:\Windows\system32\w32time.dll (Local) Enabled: 1 (Local) InputProvider: 0 (Local) AllowNonstandardModeCombinations: 1 (Local) VMICTimeProvider (Local) DllName: C:\Windows\System32\vmictimeprovider.dll (Local) Enabled: 0 (Local)
If you are still having trouble responding to NTP requests after following these steps, make sure that there are no firewalls blocking udp/123. After you’ve checked your firewall, confirm that your NTP server responds by running the following command on a different Windows machine:
w32tm /stripchart /computer:10.0.8.3 /samples:2
w32tm /stripchart /computer:10.0.8.3 /dataonly /samples:2
In the following screenshot, I have run the two commands above, and then on the third execution, I attempt to query a server that does not exist, just so you can see what the output looks like if the client still can’t connect to your NTP server.