Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Windows time service

Answered Windows time service

  • Friday, February 08, 2013 1:05 AM
     
     
    Sign In to Vote
    0
    A windows 2003 server NTP client is configured to synchronize its time with the domain controller every one hour (3600s). However, this production sever is found to have its clock gradually advanced by 8 minutes. Any idea why the windows time service has not sync'ed its time until the windows time service is manually restared? Thanks.
     

All Replies

  • Friday, February 08, 2013 8:02 AM
     
     Answered Has Code
    Sign In to Vote
    1

    Hi,

    Check whether the time is synchronized with the DC

    w32tm /resync

    For more information about WTS, please refer to:

    Windows Time Service Technical Reference
    http://msdn2.microsoft.com/en-us/library/bb608215.aspx

    How to configure the Windows Time Service against a large time offset:
    http://support.microsoft.com/kb/884776/

    Check in the domain will sync time with domain controller and the interval is a dynamic data within the range specified by the following registry:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w32time\Config]

    Value name: MinPollInterval
    Default data: 0000000a (HEX)

    Value name: MaxPollInterval
    Default data: 0000000f (HEX)

    The above indicates the default dynamic interval range is from 2^10 seconds (about 17 mins) to 2^15 seconds (about 9 hours). As the application is very sensitive to the time difference and the default synchronize interval is long, it is possible that the time may be different before the server can synchronize with the time server. If this is the case, you may reduce the MaxPoolInterval value so that clients can synchronize time more frequently; however, please understand that it will introduce more network traffic and more domain controller workload. To check whether time synchronization works, you may run the following command on a problematic client and check whether the time is synchronized with the DC.

    w32tm /resync

    Following link for issue and fix in Windows 2003

    837361:  Kerberos protocol registry entries and KDC configuration keys in Windows Server 2003

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;837361


    Please help and appreciate others by using these features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Waqas

    MS(SPM), MS(E&F),M.Engg, MCP, MCT, MCTS, MCITP, MCSE, MCPD, MCSD, MCDBA , Author
    Twitter: @Waqas_m1
    Linked In: http://www.linkedin.com/in/waqasm1




     
  • Friday, February 08, 2013 8:27 AM
     
     Answered
    Sign In to Vote
    0


    Besides to Waqas's post,  First, set time settings in BIOS and make sure it is correct.

    I suggest you see this useful thread Date Time on Clock always is wrong even after setting it.

    Regards, Ravikumar P

     
  • Friday, February 08, 2013 12:15 PM
     
     
    Sign In to Vote
    1

    Hi,

    Yeah very correct Ravi,Jiyang you should check the BIOS time and do correction there also


    Please help and appreciate others by using these features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Waqas

    MS(SPM), MS(E&F),M.Engg, MCP, MCT, MCTS, MCITP, MCSE, MCPD, MCSD, MCDBA , Author
    Twitter: @Waqas_m1
    Linked In: http://www.linkedin.com/in/waqasm1