Network Time Servers – Part 2

Now that I’ve convinced you that syncing your clocks is a good idea, you are probably wondering how to accomplish it. There are actually several ways to accomplish it depending on what kind of clients and servers you have on your network.

Most modern operating systems (Mac OS 8.6 and higher, Windows 2000, Windows XP) have client software built in to be able synchronize to a NTP (Network Time Protocol) Server or an SNTP (Simple Network Time Protocol) Server. There are hundreds of these servers all over the world. Many of these are open to the general public for synchronizing clocks.

The first thing you need to do is to decide on a strategy. If you only have 20 or 30 computers on your network, then all you really need to do is to set you clients to syncronize to one of the public time servers. In most cases, there is already a list of a public time servers in your client software. If you want the most up-to-date list, point your browser to the http://www.ntp.org

If you have more than 20 or 30 clients, or if your firewall blocks SNTP or NTP, then you should set up your own time server inside of your network. I’ll talk about that in my next post.

Let’s talk about how to sync some of your clients.

If you are using Windows 2000 or Windows XP Clients joined to a Windows 2000 domain or Active Directory, you are already syncing your clocks and you didn’t know it! Part of the login process for these clients is to automatically sync their clocks to the clock on the domain controller. That doesn’t leave you out of the woods though! You still should sync the clock on the domain controller to a network time server (use the info in the next paragraph to set that up).

If you don’t have your Windows 2000 or XP clients attached to a domain controller, then you should use the built in NTP client software. The only interface that Microsoft has built for configuring this client (that I’m aware of) is the Group Policy Editor. The simplest way to get to it in either 2000 or XP is to go to the start menu and choose the run command. In the run box, type gpedit.msc. In the gpedit window, choose Local Computer Policy, Computer Configuration, Administrative Templates, System, and finally Windows Time Service. If you look at the instructions inside of that section, it will explain how to set your clients.

UPDATE (12-2-03): One of the people making comments on this article asked about where to find the NTP client in Windows 2000. After doing some research, I’ve discovered I was wrong about NTP clients being included in Windows 2000. It is only in Windows XP and Windows 2003 Server. For you Windows 2000 users, I would suggest NetTime, which is talked about in my Network Time Servers – Part 3 post.

UPDATE (12-3-02): My brother did some checking for me and discovered that Windows 2000 does, in fact, have an NTP client embedded in it, but it is hidden and can only be configured through editing the registry directly. For more information, follow this link: http://www.gudeads.com/english/main-windows-ntp.htm

If you run Macintosh clients, this is even easier. Apple has included NTP and SNTP client software in every operating system since Mac OS 8.6. In OS 8.6 and OS 9 you will find the client software in the Date/Time Control Panel. In Mac OS X you will find it in the Date/Time preference pane. Apple conveniently gives you a list of public servers and everything.

Happy time syncing!

4 People have left comments on this post



» Kerry Shetline said: { Dec 2, 2003 - 09:12:15 }

I’ve noticed that while my computer does indeed sync with our domain time on boot up, the time drifts after a while. I leave my computer on all of the time, and, for instance, even though I’d rebooted Saturday, my time was already off by two full minutes today, three days later.

Rebooting syncs my computer back up again, and I just discovered that I can do this at a command prompt as well:

net time \our_domain_time_server /set /y

What I’m wondering is this: Why should I have to force the issue? Our IT guy (who just left for another job) swore that all of the computers on the domain were not only synched at boot-up, but kept in sync. Actual experience keeps contradicting that assurance, on more computers on our domain than just mine.

» pete_markham said: { Dec 2, 2003 - 02:12:57 }

Kerry,

Your IT Guy is correct. If things are working properly, your clocks should continue to sync auntomatically.

According to Microsoft Knowledge Base article 224799:

“The time server client performs periodic checks.
The client connects to the authenticating domain controller once each “period.”
The initial default period is 45 minutes.
If the time synchronization attempt is successful three consecutive times, then the interval check period is increased to 8 hours. If it is not successful three consecutive times, then it is reset to 45 minutes.”

It is odd that you aren’t seeing the sync behavior.

Here’s a possible solution:

You didn’t mention what your client is – Win2K or WinXP. If it is WinXP, I’d go into gpedit.msc and set you clock to sync to an external time server. If it is Win2K, I’d download a piece of software called NetTime from SourceForge and use that to sync to an external time server. You can force the time between synchronizations to be much shorter.

Good luck!

» Kerry Shetline said: { Dec 3, 2003 - 01:12:36 }

Thanks for the response. This is a WinXP client that I’m using. I’ve just located gpedit.msc file. I’m not sure what to change in here — I know XML, but I don’t see anything clearly related to time in any way. I imagine a bit of Googling might tell me what I need to know.

In any event, our not-yet-replaced IT guy specifically went around asking people NOT to sync to external sources, because he wanted us to all be in sync with the domain time server, not some other time standard.

Then again, because the sync isn’t working, I’d probably be closer to our own domain time server by synching to an external source that I am now, with the way things appear to be broken. Since synching yesterday afteroon, I’m already 53 seconds off.

» Steve McEvoy said: { Jan 5, 2004 - 12:01:21 }

I’ve seen this problem as described on two other networks. Both have AD installed, one is a 2003 server, the other a 2000 Server. All the workstations are Windows XP pro joined to the domain. All the hardware (server and PCs) are new Dells.

The PCs are left on all the time and not logged in/out for long periods. The time drift is significant, minutes per day. Using the net time resync is a band-aid, not a solution.

Left on their own they never seem to resync the time, only when rebooted or logged in-out.

The drift itself is weird, but I wish the PCs would at least notice the drift and resync at least every day.

Thoughts anyone?

Sorry, comments for this entry are closed at this time.