Paul
Fri Mar 28 05:54:47 PDT 2008
Make sure you are using the w32tm time service, the net time service is
deprecated. Check to make sure your time zones are all set up correctly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;816042
http://64.233.167.104/search?q=cache:kKtQoVi7zcMJ:www.mmmug.co.uk/files/216/download.aspx+windows+w32tm+%22time+service%22+debugging&hl=en&ct=clnk&cd=3&gl=us
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"John" <bechtj@co.delaware.pa.us> wrote in message
news:edmo5sCkIHA.4712@TK2MSFTNGP04.phx.gbl...
> Ok. I set my AD Server up as a Time Server for our Network. If I type in
> net time in command prompt I get back the Current Time at \\SERVER is
> Correct Time.
>
> If I go to a Workstation on my Domain and type in Net Time I get Current
> Time at \\SERVER is ( a hour back then correct time) and then I get a
> message Local Time at \\SERVER is the Correct Time.
>
> Of course the clock gets set to the Current time which is wrong because it
> is a hour behind and all the workstations are a hour behind. What is the
> difference or where is my problem.....between local and current time?
>