No announcement yet.

W32tm Time sync errors, should I be worried?

  • Filter
  • Time
  • Show
Clear All
new posts

  • W32tm Time sync errors, should I be worried?

    Yesterday I updated the (or so I thought I was) the time service on the PDC for our domain. I chose "" since they use a pool of internet time servers and thought it be the best choice.

    I ran this command (w32tm /config /manualpeerlist:”” /reliable:yes /update) on my PDC, but now I'm getting these errors in EM:
    __________________________________________________ _______________

    Event Type: Warning
    Event Source: W32Time
    Event Category: None
    Event ID: 36
    Date: 3/20/2015
    Time: 9:34:01 AM
    User: N/A
    Computer: SERVER-2003
    The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. Monitor the system events displayed in the Event Viewer to make sure that a more serious problem does not exist.

    For more information, see Help and Support Center at
    __________________________________________________ _______________

    Although I can say that the time has been dead on ever since I ran that command. Is this something I can ignore? Just worried about these errors.

  • #2
    Re: W32tm Time sync errors, should I be worried?

    You missed a switch from your command: /syncfromflags:MANUAL should be included when you specify a /manualpeerlist entry. As far as 'issues', so long as your domain clients can update their time from your DC, you should be OK. But where your clients are trying to access public sites using SSL, as an example, sometimes those don't work if your time sync is off by more than a margin. That margin is, I think, down to the web site's admin.

    By all means, search the Petri site for other articles about 'w32tm' and I'm certain you'll find quite a few. As an example, there's
    ''. While the original question asked there was more wide-reaching than yours, there are links to MS articles which should clear up any confusion you may have about how time works in an MS domain.
    MSCA (2003/XP), Security+, CCNA

    ** Remember: credit where credit is due, and reputation points as appropriate **