Discussion Locked

Time Serverin DHCP

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Can anyone help me with this - I have added a "004 server option" to the DHCP server setting the IP addess of the time server - this appears OK BUT it appears that the clients are not being updated wth the time of this server so what have I mssed orwhat should i do/check ??

Thanks

5 replies

by timwalsh

Most Microsoft operating systems do not make use of this setting. There is no way for the Clock applications to check their time against a Time Server. The only exception is is Win2K Server with AD. Kerberos authentication uses a time stamp, but it AD servers synchronize their time using time servers found in AD.
There may be certain specialized applications that are time sensitive and require access to a time server and could make use of this setting.
There are numerous shareware/freeware utilities available that will periodically ping the various Atomic Clock Servers around the world and adjust the local computer's time accordingly. Hope this helps.

by does not compute!

Thanks for your reply but the answer give by Micheal gave me the answer I was looking for - thanks anyway for bothering to respond

by rabbit_runner

THe above answer is correct, in that MS does not uitilize the Time server feature of DHCP. However here is a cheap method of setting the time on the workstations that log into a domain.

In your logon script, add the following line...

net time/set \\ /y

This will set the time on each computer that uses the logon script. If you are using a workgroup LAN, then you will need to add this line to a batch file and place it in the startup folder of each computer.

I hope this may help.

by does not compute!

Thanks very much I had seen the net time command but not the /y switch which is obviously what I was missing - thanks again -- Andrew

This discussion is closed to new replies.