cpri
2008-07-08, 05:30 AM CDT
Hello,
I have the following setup.
My server runs a batch script to backup the data. When this is done it calls the ntp server to get the exact time
ntpdate 0.nl.pool.ntp.org
followed by the command to set the hardware clock
hwclock --systohc
My local windows machines they call for the right time when they boot
net time \\odsrv0001 /set /y
(odsrv0001 is the name of the server.)
The problem is after a few weeks my local machine are a few minutes ahead.
When I call the hwclock or the normal clock on my server I get the right time.
But when my local machine calls the time server it gets a time a few minutes ahead.
I have call (manually) on the server
ntpdate 0.nl.pool.ntp.org
to set the time the right again (this should be taken care of in my backuo script but somehow it doesn't work). (The script is running I checked)
Can somebody help me out so that all the local machines get the right time ??
I have the following setup.
My server runs a batch script to backup the data. When this is done it calls the ntp server to get the exact time
ntpdate 0.nl.pool.ntp.org
followed by the command to set the hardware clock
hwclock --systohc
My local windows machines they call for the right time when they boot
net time \\odsrv0001 /set /y
(odsrv0001 is the name of the server.)
The problem is after a few weeks my local machine are a few minutes ahead.
When I call the hwclock or the normal clock on my server I get the right time.
But when my local machine calls the time server it gets a time a few minutes ahead.
I have call (manually) on the server
ntpdate 0.nl.pool.ntp.org
to set the time the right again (this should be taken care of in my backuo script but somehow it doesn't work). (The script is running I checked)
Can somebody help me out so that all the local machines get the right time ??