Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
nikolas.e

Senior Member
Registered:
Posts: 102
Reply with quote  #1 
i remember i have asked this question old times but since i cant look to old posts (New Forum) i will have to ask again


When a DC holding the PDC role (One Domain in the forest) syncs its time with a NTP Server, The Time that it is been synced between the DC and NTP is the UTC time correct? Windows O/S only handles the Time zone that is selected on the system and displayed to us.

Can anyone verify that this info is correct? Thank you


I will  add an example 

UTC Time 1:00 PM
Athens Time Zone : UTC+2:00
Domain controller display time based on UTC sync and Timezone should be 3:00 PM

__________________
Just call me the 1000Questionsguy
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #2 
From what I understand, that is correct. Domain controllers use UTC but local time is what is displayed to the user based on regional settings.

Use of UTC is necessary since many organizations span time zones.
0
cspanburgh

Avatar / Picture

Senior Member
Registered:
Posts: 188
Reply with quote  #3 
Good to know.    thanks.  We need to build up answers here.
__________________
Curt Spanburgh
0
nikolas.e

Senior Member
Registered:
Posts: 102
Reply with quote  #4 
Quote:
Originally Posted by DM-AVAL
From what I understand, that is correct. Domain controllers use UTC but local time is what is displayed to the user based on regional settings.

Use of UTC is necessary since many organizations span time zones.



Thank you for your answer.

__________________
Just call me the 1000Questionsguy
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 130
Reply with quote  #5 
FYI.
I recently had a problem with the external NTP server we use.  The NTP server was suddenly 1 day ahead.
While I was throubleshooting it, I found two interesting registry keys :
HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection and MaxNegPhaseCorrection

If set to 300 (decimal in seconds, that's 5 min) the NTP client (the PDCe) will not sync with the NTP server if that server is more than 5 minutes ahead of or behind previous time.  If the time jump is more that 5 minutes, we can presume that the NTP server has a problem and the NTP client shouldn't sync.

__________________
Pieter Demeulemeester
0
nikolas.e

Senior Member
Registered:
Posts: 102
Reply with quote  #6 
Quote:
Originally Posted by Pieter
FYI.
I recently had a problem with the external NTP server we use.  The NTP server was suddenly 1 day ahead.
While I was throubleshooting it, I found two interesting registry keys :
HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection and MaxNegPhaseCorrection

If set to 300 (decimal in seconds, that's 5 min) the NTP client (the PDCe) will not sync with the NTP server if that server is more than 5 minutes ahead of or behind previous time.  If the time jump is more that 5 minutes, we can presume that the NTP server has a problem and the NTP client shouldn't sync.


Pieter so your forest root domain PDC received incorrect time from the NTP Server and every system in your network synced hierarchy  the wrong time? What was your first steps to resolve this? Switch to different NTP Server?

__________________
Just call me the 1000Questionsguy
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 130
Reply with quote  #7 
>> What was your first steps to resolve this? Switch to different NTP Server?                 
Yes, well I changed the NTP server to a non-existing NTP source (made a typo) and corrected the time on the PDCe manually. Then stop/start Time server and "w32tm /resync" on the DC's and afterwards on the member servers.

__________________
Pieter Demeulemeester
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation: