• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1841
  • Last Modified:

Win 32 Time

I have configured the XP PC to synchronize every 30 minutes. But I have a problem with w32time instead of sychronizing every 30mins it now synchronizes every 17mins.

Below is the configuration I have done:

a) Configure NTP Server Reference Source
•      HKEY_LOCAL_MACHINE – SOFTWARE – Microsoft – Windows – CurrentVersion – DateTime – Servers
•      Name =1,
•      Type=REG_SZ, Data = IP for ntpserver_source1, , IP for ntpserver_source2, IP for ntpserver_source3

b) Configure w32time to synch every 30 minutes
•      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32Time\TimeProviders\NTPClient
•      Locate SpecialPollInterval DWORD value
•      Select Decimal as the base and change the value data to 1800 (30 min x 60 sec = 1800)

Any ideas? Thank You in advance.
1 Solution
It is possible that if on a domain there is a group policy or local policy.
It is also possible there is a scheduled task

The below URL may also be useful.


Pete LongTechnical ConsultantCommented:
Setting Domain Time

There a number of time service refinements in Server 2003 but the following will work on 2K as well. For continuity make the PDC Emulator the time server (in a 2003 domain it’s the time server by default)

First arm yourself with the names of TWO external time servers see the lists below

A List of the Simple Network Time Protocol Time Servers That Are Available on the Internet
Public NTP Primary (stratum 1) Time Servers

Now you have two server names you need to find out two things

Is the server up?
What’s its IP address?

I’m in the UK so I use ntp1.pipex.net and ntp2a.mss.ac.uk

To answer the two questions above simply tracert to the server names (obviously you need DNS to be working first)

For example
tracert ntp2a.mcc.ac.uk

Tracing route to maverick.mcc.ac.uk []
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms

<loads of hops deleted>

29    24 ms    25 ms    22 ms  maverick.mcc.ac.uk []

Trace complete.

Using this method I now know the two IP addresses for those two time servers
Are and

You need to know that information to allow your “Time Server” out to those IP addresses on your firewall NOTE you need to allow UDP Port 123 to those IP addresses for SNTP to work.

On the server issue the following command.

net time /setsntp:"ntp1.pipex.net ntp2a.mcc.ac.uk"

to ensure the command was successful issue the following

net time /querysntp

If you have a large complex network you can create local time servers in different locations (to cut down traffic etc) by editing the following registry key:
In HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\W32 Time\Parameters, find the REG_DWORD subkey called LocalNTP. Change the subkey value from 0 to 1. After you restart Windows Time Service, your Win2K system will function as an SNTP server.


Your clients in a 2K and XP environment should slowly start getting the correct time (if they struggle you can issue the following command on them)

net time /setsntp:<IP address of your time server>

********If all that's too much Hassle*********

Set your server to atomic time using third party software



You can really tie yourself in knots with Win32time.  Try downloading this tardis2000: http://www.kaska.demon.co.uk/tardis.htm

It's a great app and I use it to sync in excess of 300 machines on our office network.

If you need to sync more than one machine - use tardis on the server and K9 on each client PC running as a service.

Let me know how you get on.


Featured Post


Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now