General discussion



By tim.williams ·
Hi there

I want to know if there is a way to set our server to update everyones clocks when they are on the LAN?



This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

One solution

by CharlieSpencer In reply to Time

Assuming Windows, if you're not interested in exact-to-the-second accuracy throughout the day, stick a NET TIME statement in the login scripts. I'm sure other network OSs have a similar statement to set the client time. This will set the time whenever a user logs in.

Collapse -

more verbose please

by Tink! In reply to One solution

Could you elaborate please? Show the exact NET TIME statement. I'd be interested in this too. Note: I have never actually written a login script.

Collapse -


by CharlieSpencer In reply to more verbose please

NET TIME \\timeserver /SET

Where timeserver is the name of the computer you have set up as your "master clock".

Collapse -

What is the environment?

by Cactus Pete In reply to Time

A lot depends on what servers you have (in what roles), what NOS, and what client OS...

For a WinServ 2003 AD environment, just have your XP clients set to

NET TIME /setsntp:

and make sure that the "Windows Time" service is running.

Basically, NET TIME should be set to nothing (so it automatically picks up your AD time). Many XP installations have the SNTP server set to which is likely blocked by your firewall. You can check by running

NET TIME /querysntp

I don't set our policies here, so I'm not 100% sure, but I expect you can set this at the policy level for your domain.

Also, set your root domain controller to point to the closest public NTP server out there (make sure you open port 123 for that server on your firewall).

There is a LOT of documentation for various environments out there on the web...

Collapse -

Active Directory Time

by BFilmFan In reply to What is the environment?

Time in Active Directory is set by the PDC Emulator. All other systems query the PDCE for the correct time. In multiple domain forests, the root domain PDCE manages time across the forest.

As noted earlier, W32Time is controlled by values set in registry subkey HKEY LOCAL MACHINE\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters.

Windows 2000-based servers have a default "Type" REG_SZ value of "Nt5DS" for "Domain hierarchy based synchronization", which means that when a Windows 2000 workstation starts up on a network (not local), the Net Logon service looks for a domain controller that can authenticate and synchronize time with a domain controller in its own domain.

To set an external time source for your PDCE, you could use the following NTP resources listed at

Note that UDP Port 123 must be open to synchronize with an external time source.

Collapse -

Good Idea

by tim.williams In reply to Active Directory Time

Hi Guys

Thanks for your ideas, they are great suggestions, however I forgot to mention we dont log onto the server with logon scripts, we dont use a domian, just a workgroup, so not sure how I could do this?


Collapse -

NTP, this is the basis of all other time setting

by stress junkie In reply to Time

You should have a look at this page about Network Time Protocol. It would answer a lot of questions for you. Windows has their own software to do this as the other posts have indicated. I just thought that if you understood the basic principles you would be better able to understand the answers being proposed.

Collapse -


by tim.williams In reply to NTP, this is the basis of ...

Hi Stress Junkie

I have downloaded the NTP file from the site you gave me, do I just install it on our server now?


Related Discussions

Related Forums