Configure a Local NTP Server
Devices rely on an internet time server and a clock source, such as a GPS satellite, to synchronize time across devices. However, in an offline scenario where devices are not connected to the internet, time synchronization must be achieved using a local Network Time Protocol (NTP) server.
If you require a local NTP server:
- Check with your IT team. An NTP server may already be provisioned.
- If an NTP server is not already available, create a Windows-based NTP server by following the steps below.
- A Windows server running Windows 7, 8, or 10 is required. Procedures listed on this page have been tested using Windows 10. Other Windows versions may have a slightly different workflow.
- You must have Administrator privileges to configure the Windows server.
- Requires a basic understanding of Windows registry. Caution should be used when updating the registry.
To configure a local NTP Server, you will need to do the following:
- Step 1: Configure Windows Time Service
- Step 2: Update Windows Registry to Create Local NTP Service
- Step 3: Update Windows Registry to Configure Time Provider
- Step 4: Update Windows Registry to Configure Announce Flags
- Step 5: Start Local Windows NTP Time Service
To jump to a specific section, refer to the Table of Contents on the right side and click the corresponding step.
To configure the Windows Time Service:
- In the File Explorer, navigate to: Control Panel\System and Security\Administrative Tools.
- Double-click Services. Alternatively, enter services.msc in the Windows Run dialog (Windows Key + R).
In the Services list, right-click Windows Time and click Stop. The Windows Time service may already be stopped. In this case, skip this step and proceed to the steps below.
To create a local NTP service:
- Launch Windows Run (Windows Key + R).
- Enter regedit and click OK.
- Navigate to the registry key: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters. If you don't see LocalNTP REG_DWORD in the list, continue with the following steps. If you do see it, keep the Registry Editor open and proceed to the next task.
Right-click in the Registry Editor, select New, select DWORD, and enter LocalNTP (note that this name is case sensitive).
- Double-click LocalNTP, change the Value data to 1, select a Base of Hexadecimal, and click OK.
- Keep the Registry Editor open for the next task.
To configure the time provider:
- Navigate to the registry key: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders
Select NtpServer, double-click Enabled, change the Value Data to 1, select a Base of Hexadecimal, and click OK.
- Close the Registry Editor.
To configure the announce flags:
- Navigate to the registry key: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
Double-click AnnounceFlags, change the Value data to 5, select a Base of Hexadecimal, and click OK.
-
To start the local Windows NTP Time Service:
- In the File Explorer, navigate to: Control Panel\System and Security\Administrative Tools.
- Double-click Services.
- In the Services list, right-click Windows Time and select Properties.
In the Windows Time Properties (Local Computer) dialog box, select a Startup type of Automatic, click Start for Service status, and click OK.
The local NTP Time Server configuration is now complete. You can now synchronize the time of other computers and devices on your local network.
In order for devices on your local network to communicate with this new local time server, you must know the IP address of the Windows NTP Time Server.
To synchronize the time on devices:
- On the Windows server that you just configured as an NTP server, go to the Windows Command Prompt, enter: ipconfig.
- Locate the IP address of the NTP server.
- Go to either the Litmus Edge Web UI or the Terminal User Interface (TUI) and enter the address of the local NTP server.
- To use the Litmus Edge Web UI, update the NTP Servers. See Configure DNS/NTP Servers to learn more.
To use the TUI, update the Configure Time setting. See Access the Terminal User Interface to learn more.