Re: keeping the clock syncronised for clients

Payal Rathod wrote:

> Hi all,
> I syncronise my Linux box's clock with,
> # ./sntpclock <ip of NTP server> | ./clockadd
> 
> I would like all my windows clients to have the same time as the Linux
> box. What should I do for such a case?

<URL:http://www.boulder.nist.gov/timefreq/service/its.htm> contains 
links to NIST's time synchronizing software.

Windows XP and Server 2003 have built-in support for synchronization, 
but you may not like how infrequently it updates itself, and if you have 
a really poor clock, it will drift.

I like using NetTime <URL:http://nettime.sourceforge.net/>. It's 
freeware, can run invisibly, and lets you customize which servers to use 
and when to contact them.

You can also try to port clockspeed to .NET, but I had limited success 
manipulating Windows's understanding of timezones. It only has 
per-minute granularity.

Assuming you've followed one of these solutions, you can sync all the 
Windows and Linux machines to the same third party NTP server. If you're 
using "./sntpclock <ip of NTP server>" to sync your Linux machine, you 
should set your Windows systems to the same IP address. This is probably 
the easiest solution for you.


Toby