Google provides a free public NTP (Network Time Protocol) server that you can use to synchronise time on Windows 10, Windows 11 and Windows Server. This guide covers how to configure Google’s NTP server on individual machines, via Group Policy across your entire domain, and using PowerShell for bulk configuration.
Google Public NTP Server Address
Google’s public NTP server address is:
time.google.comGoogle also provides numbered servers if you need multiple NTP sources:
- time1.google.com
- time2.google.com
- time3.google.com
- time4.google.com
Google Public NTP uses leap-smeared time — a technology that smoothly handles leap seconds without disruptive clock adjustments. Their NTP infrastructure is backed by atomic clocks in data centres worldwide.
Configure Google NTP on Windows 10 and Windows 11
- Open Command Prompt as Administrator
- Run the following commands:
w32tm /config /manualpeerlist:"time.google.com" /syncfromflags:manual /reliable:YES /update
net stop w32tm
net start w32tm
w32tm /resync /forceVerify the configuration is working:
w32tm /query /statusConfigure Google NTP via PowerShell
# Configure Google NTP server via PowerShell
Set-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Services\W32Time\Parameters" -Name "NtpServer" -Value "time.google.com,0x1"
Set-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Services\W32Time\Parameters" -Name "Type" -Value "NTP"
Restart-Service W32Time
w32tm /resync /force
w32tm /query /statusConfigure Google NTP via Group Policy (Domain Environments)
For enterprise environments, configure NTP via Group Policy to push the setting to all domain-joined machines automatically.
- Open Group Policy Management Console
- Create or edit a GPO linked to your domain or target OU
- Navigate to Computer Configuration → Administrative Templates → System → Windows Time Service → Time Providers
- Enable Configure Windows NTP Client
- Set NtpServer to
time.google.com,0x1 - Set Type to NTP
- Enable Enable Windows NTP Client
- Click OK and close Group Policy Editor
Configure Google NTP on Windows Server
For Windows Server — particularly domain controllers — time synchronisation is critical for Kerberos authentication. Configure the PDC Emulator domain controller to sync with Google NTP, and all other domain members will sync from it automatically.
# Run on PDC Emulator domain controller only
w32tm /config /manualpeerlist:"time.google.com time1.google.com time2.google.com" /syncfromflags:manual /reliable:YES /update
net stop w32tm
net start w32tm
w32tm /resync /forceVerify NTP Synchronisation
After configuring Google NTP, verify it is working correctly:
# Check current NTP configuration
w32tm /query /configuration
# Check sync status
w32tm /query /status
# Check NTP peers
w32tm /query /peersThe output should show time.google.com as the NTP source and a low offset value (under 1 second).
Frequently Asked Questions
Is Google Public NTP free to use?
Yes — Google Public NTP is completely free for anyone to use. There are no usage limits or registration requirements. Simply point your NTP client to time.google.com.
Should I use Google NTP instead of pool.ntp.org?
Both are reliable options. Google NTP has the advantage of leap-smeared time handling which avoids the clock jump that can occur at leap second events. For enterprise environments either is suitable, though Google NTP is backed by a more robust infrastructure.
Why is accurate time important in a domain environment?
Kerberos authentication — used by Active Directory — requires that all domain members have clocks within 5 minutes of each other. If clocks drift beyond this threshold, users will be unable to authenticate and log in. This is why NTP configuration is critical in domain environments.
Can I use Google NTP on non-Windows devices?
Yes — Google NTP works on any device that supports NTP including Linux, macOS, network switches, routers and IoT devices. Simply set time.google.com as your NTP server in the device settings.
My time is still wrong after configuring Google NTP — what do I do?
Check that the Windows Time service is running: net start w32tm. Then force a resync: w32tm /resync /force. If the issue persists check that UDP port 123 is not blocked by your firewall, as NTP uses UDP 123 for communication.
About The Author
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.