Re: w2k DC time off by 12 hours
- From: "John John (MVP)" <audetweld@xxxxxxxxxxx>
- Date: Tue, 05 May 2009 09:23:15 -0300
Hmmm... What about the Time Zones? Are both machines in the same zone? If both machines are in the same zone the information at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation should be indentical. You could copy the key and values from the PDC to srv2.
John
msnews.microsoft.com wrote:
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@xxxxxxxxxxxxxxxxxxxxxxxProbably 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
- Follow-Ups:
- Re: w2k DC time off by 12 hours
- From: msnews.microsoft.com
- Re: w2k DC time off by 12 hours
- From: msnews.microsoft.com
- Re: w2k DC time off by 12 hours
- References:
- w2k DC time off by 12 hours
- From: msnews.microsoft.com
- Re: w2k DC time off by 12 hours
- From: John John (MVP)
- Re: w2k DC time off by 12 hours
- From: msnews.microsoft.com
- w2k DC time off by 12 hours
- Prev by Date: W32TM on W2K SP4?
- Next by Date: Re: W32TM on W2K SP4?
- Previous by thread: Re: w2k DC time off by 12 hours
- Next by thread: Re: w2k DC time off by 12 hours
- Index(es):
Relevant Pages
|