Re: Automatically setting a PC's time

["rb_ziggy" <richard.boreham@xxxxxxxxxxxx>]

Thanks all - the Windows Time Service takes the prize - curiously
useful utility.  Just set it up one command (net time... as described
below), start the service (and set to automatic start) and that seems
to be it.  Done it on two PCs and they are now in perfect harmony!

Thanks also for the ntp1.ja.net link. This was where I'd struggled as
I'd found the Janet site: http://www.ja.net/ntp/ The guff there
seemed to indicate that this was a closed group service.  However, it
works fine!

Met the criteria for simplicity and cost effectiveness too.  Great
for Win2K & above.

Maybe a FAQ?

Regards

Richard

--- In ukha_d@xxxxxxx, "John B" <home-automation@j...>
wrote:
> > It's a fairly standard thing in most Unixes (NFS is highly
dependant on
> > accurate time for encrypted connections to work properly).  I'd
be very
> > surprised if there wasn't a nice simple NTP client for Windows,
but I
> > suspect that, like very nearly everything else, it would be
nagware at
> > best, bloody expensive at worst.
>
> Windows 2000 and above all include an NTP client, called the
Windows Time service (w32time).
>
> > As far as time servers go, I tend to use ntp1.ja.net as my NTP
server.
>
> In which case, using your above NTP server as an example, you'd go
to a command prompt and type:
>
> net time /setsntp:ntp1.ja.net
>
> The Windows Time service can also act as an NTP time server, so you
can have all your client PCs sync up to the time server, then have
the time server sync to an external NTP source like ntp1.ja.net.
>
> Never had any issues with the time service - just set and forget.
>
> Also, if you are on Blueyonder broadband (same may be true for NTL)
your UBR (first hop in a traceroute) acts as an NTP server.
>
> HTH,
>
> John