Re: w2k DC time off by 12 hours

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I can set the time / date properly on srv2. At the next sync period for
srv2, the time on srv2 changes from PM to
AM.... or from AM to PM - it jumps 12 hours.




"John John (MVP)" <audetweld@xxxxxxxxxxx> wrote in message
news:OoiQU%23NzJHA.5728@xxxxxxxxxxxxxxxxxxxxxxx
Probably a stupid suggestion but it sounds like the AM/PM might be wrong
on one of the machines, exactly 12 hour difference...

John

msnews.microsoft.com wrote:
have 2 w2k servers, sp4.
srv1 is PDC ( holds all roles) and is set to sync with NTP server.
srv2 is problem. every time srv2 syncs time, it goes off by 12 hours.
srv2 date and time zone setting are correct. srv2 thinks PDC is offline,
which is not true.
suggestions ? thanks


.



Relevant Pages

  • Re: w2k DC time off by 12 hours
    ... srv1 is PDC and is set to sync with NTP server. ... every time srv2 syncs time, it goes off by 12 hours. ...
    (microsoft.public.win2000.general)
  • Re: w2k DC time off by 12 hours
    ... Therefore you have to install the support\tools\suptools.msi from the 2000 installation disk, ... srv1 is PDC and is set to sync with NTP server. ... srv2 is problem. ... every time srv2 syncs time, ...
    (microsoft.public.win2000.general)
  • Re: w2k DC time off by 12 hours
    ... srv1 - reg info ... dcdiag output - run from srv2 ... srv1 is PDC and is set to sync with NTP server. ...
    (microsoft.public.win2000.general)
  • w2k DC time off by 12 hours
    ... srv1 is PDC and is set to sync with NTP server. ... every time srv2 syncs time, it goes off by 12 hours. ...
    (microsoft.public.win2000.general)