none
W32TM /RESYNC: The computer did not resync because no time data was available

    Question

  • Windows Server 2003 R2 and Windows XP SP3 (All 32-bit)

    Registry Settings for Windows Time
    PDC - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ Type = NTP
    Member clients and non-PDC domain controllers - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ Type = NT5DS

    Getting events below:-

    Event Type:    Warning
    Event Source:    W32Time
    Event Category:    None
    Event ID:    24
    Date:        2/19/2010
    Time:        12:20:54 PM
    User:        N/A
    Computer:    XXX-XX-XX-XXXX
    Description:
    Time Provider NtpClient: No valid response has been received from domain controller XXX-XX-XX-XXXX.xx.xx.xxxxx after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a  new domain controller from which to synchronize.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type:    Error
    Event Source:    W32Time
    Event Category:    None
    Event ID:    29
    Date:        2/19/2010
    Time:        12:20:54 PM
    User:        N/A
    Computer:    XXX-XX-XX-XXXX
    Description:
    The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible.  No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type:    Information
    Event Source:    W32Time
    Event Category:    None
    Event ID:    38
    Date:        2/19/2010
    Time:        12:23:42 PM
    User:        N/A
    Computer:    XXX-XX-XX-XXXX
    Description:
    The time provider NtpClient cannot reach or is currently receiving invalid time data from XXX-XX-XX-XXXX.xx.xx.xxxxx (ntp.d|x.x.x.x:123->x.x.x.x:123).

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

     

    ·         I have tried w32tm /unregister & w32tm /register

    ·         DNS is working fine

    ·         Can ping the time server (PDC) from the clients

    ·         Only seems to have happened since applying the security templates defined in the Microsoft document Windows Server 2003 SP2 R2 Common Criteria Configuration Guide 3.0 which is a requirement in this environment - http://www.microsoft.com/downloads/details.aspx?FamilyId=4F7B6A93-0307-480F-A5AF-A20268CBD7CC&displaylang=en

     

    Does anyone know how to resolve this?

    Friday, February 19, 2010 12:57 PM

Answers

  • I had tried that unsuccessfully but I have now resolved this myself!

    I ran the command  w32tm /config /syncfromflags:domhier /reliable:yes /update on the PDC and then stopped and started the w32time service.

    Now when I run the w32tm /resync command on clients pointing towards the PDC they update successfully.

    Thanks for your help with this anyway guys.

    Jonathan

    Monday, February 22, 2010 10:36 AM

All replies

  • Hi,

    Try this on the domain controller (PDC) http://technet.microsoft.com/en-us/library/cc786897(WS.10).aspx

    Eg:  w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org" /syncfromflags:manual /reliable:yes /update

    Try this on Windows XP client  http://technet.microsoft.com/en-us/library/cc758905(WS.10).aspx

    Eg:  w32tm /config /syncfromflags:domhier /update

           net stop w32time && net start w32time

    Compare the Domain Controller (PDC) Registry again this  http://support.microsoft.com/default.aspx/kb/816042
    Hope you find the info useful
    Saturday, February 20, 2010 9:27 PM
  • Hi - thanks for your response.

    I am unable to complete your first suggestion as the environment is air-gapped and thus has no access to an Internet NTP source.

    I have tried the suggestion for the client and this did not work. Still get the same error message when trying to resync the time and the time remains offset from the PDC.

    I'm not 100% sure on the PDC should be configured in an environment where there is no access to an NTP server and no internal hardware clock - any ideas?

    Jonathan
    Monday, February 22, 2010 9:32 AM
  • Hi,

    Have you tried the following steps in the article below:

    How to configure an authoritative time server in Windows Server
    http://support.microsoft.com/default.aspx/kb/816042

    "To configure the PDC master without using an external time source, change the announce flag on the PDC master. The PDC master is the server that holds the forest root PDC master role for the domain. This configuration forces the PDC master to announce itself as a reliable time source and uses the built-in complementary metal oxide semiconductor (CMOS) clock. To configure the PDC master by using an internal hardware clock, follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
    3. In the right pane, right-click AnnounceFlags, and then click Modify.
    4. In Edit DWORD Value, type A in the Value data box, and then click OK.
    5. Quit Registry Editor.
    6. At the command prompt, type the following command to restart the Windows Time service, and then press ENTER:
    net stop w32time && net start w32time
    "
    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, February 22, 2010 10:19 AM
    Moderator
  • I had tried that unsuccessfully but I have now resolved this myself!

    I ran the command  w32tm /config /syncfromflags:domhier /reliable:yes /update on the PDC and then stopped and started the w32time service.

    Now when I run the w32tm /resync command on clients pointing towards the PDC they update successfully.

    Thanks for your help with this anyway guys.

    Jonathan

    Monday, February 22, 2010 10:36 AM
  • Glad to hear you have resolved the problem. If you have more questions in the future, you’re welcomed to this forum.

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, February 23, 2010 10:57 AM
    Moderator
  • HI,

    I have a network behind a TMG server on which I have opened port 123.  I have two W2008R2 servers with which I am trying to syncronise time with a reliable source.

    On the main domain controller I have setup the reg entries to use a ntp server (I even used the 'fixit' to set the NTP server to ntp.xxx.xxx.xxx,0x1) using the specified url of our provider.  I have stopped and started the services and 'w32tm /config /update' and 'w32tm /resync /nowait' both say they complete successfully.  But the time does not syncronise.

    I have tried w32tm /stripchart /computer:ntp.xxx.xxx.xxx /samples:4 /dataonly and it tracks the ntp server and reports I am -12.4543528 seconds out (I put it out of sync to test it to sync).

    However the TMG server does not show any log entry for the resync it only show the entries for the stripchart which makes me think it is not even asking the ntp server for the resync time!!

    Tried the same on the other W2008R2 server and get the same result.

    Looked on Google and it mentioned a hotfix on R2 SP1 - tried this and it said it was not applicable for this system

    config is (ntp server url changed to xx's

    [Configuration]
    EventLogFlags: 2 (Local)
    AnnounceFlags: 5 (Local)
    TimeJumpAuditOffset: 28800 (Local)
    MinPollInterval: 6 (Local)
    MaxPollInterval: 10 (Local)
    MaxNegPhaseCorrection: 3600 (Local)
    MaxPosPhaseCorrection: 3600 (Local)
    MaxAllowedPhaseOffset: 300 (Local)

    FrequencyCorrectRate: 4 (Local)
    PollAdjustFactor: 5 (Local)
    LargePhaseOffset: 50000000 (Local)
    SpikeWatchPeriod: 900 (Local)
    LocalClockDispersion: 10 (Local)
    HoldPeriod: 5 (Local)
    PhaseCorrectRate: 7 (Local)
    UpdateInterval: 100 (Local)


    [TimeProviders]
    NtpClient (Local)
    DllName: C:\Windows\system32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    AllowNonstandardModeCombinations: 1 (Local)
    ResolvePeerBackoffMinutes: 15 (Local)
    ResolvePeerBackoffMaxTimes: 7 (Local)
    CompatibilityFlags: 2147483648 (Local)
    EventLogFlags: 1 (Local)
    LargeSampleSkew: 3 (Local)
    SpecialPollInterval: 900 (Local)
    Type: NTP (Local)
    NtpServer: ntp.xxx.xxx.xxx,0x1 (Local)

    NtpServer (Local)
    DllName: C:\Windows\system32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 0 (Local)
    AllowNonstandardModeCombinations: 1 (Local)

    VMICTimeProvider (Local)
    DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)

     

    Thursday, October 25, 2012 2:09 PM
  • Tried 0x5 , 0x1 and 0xA as flags no change as per:-

    If an authoritative time server that is configured to use an AnnounceFlag value of 0x5 and to synchronize with an upstream time server at a fixed interval that is specified in SpecialPollInterval, a client server may not correctly synchronize with the authoritative time server after the authoritative time server restarts. Therefore, if you configure your authoritative time server to synchronize with an upstream NTP server at a fixed interval that is specified in SpecialPollInterval, set the AnnounceFlag value to 0xA instead of 0x5.

    It just does not ask for the time!

    Friday, October 26, 2012 12:09 PM