none
Windows 7 workstation fails to synchronize time with Windows Server 2003 DCs

    Question

  • Hello everybody,

    at a customer's site, there are hundreds of Windows XP workstations synchronizing their time perfectly with the Windows Server 2003 Domain Controllers. However, a Windows 7 workstation continuously fails to do so and we could not get it back to work. FYI, here are outputs of w32tm and the w32tm debug log:

    PS H:\> w32tm /query /source
    Local CMOS Clock
    PS H:\> w32tm /query /configuration
    [Konfiguration]
    
    EventLogFlags: 2 (Lokal)
    AnnounceFlags: 10 (Lokal)
    TimeJumpAuditOffset: 28800 (Lokal)
    MinPollInterval: 10 (Lokal)
    MaxPollInterval: 15 (Lokal)
    MaxNegPhaseCorrection: 4294967295 (Lokal)
    MaxPosPhaseCorrection: 4294967295 (Lokal)
    MaxAllowedPhaseOffset: 300 (Lokal)
    
    FrequencyCorrectRate: 4 (Lokal)
    PollAdjustFactor: 5 (Lokal)
    LargePhaseOffset: 50000000 (Lokal)
    SpikeWatchPeriod: 900 (Lokal)
    LocalClockDispersion: 10 (Lokal)
    HoldPeriod: 5 (Lokal)
    PhaseCorrectRate: 1 (Lokal)
    UpdateInterval: 30000 (Lokal)
    
    
    [Zeitanbieter]
    
    NtpClient (Lokal)
    DllName: C:\Windows\system32\w32time.dll (Lokal)
    Enabled: 1 (Lokal)
    InputProvider: 1 (Lokal)
    AllowNonstandardModeCombinations: 1 (Lokal)
    ResolvePeerBackoffMinutes: 15 (Lokal)
    ResolvePeerBackoffMaxTimes: 7 (Lokal)
    CompatibilityFlags: 2147483648 (Lokal)
    EventLogFlags: 1 (Lokal)
    LargeSampleSkew: 3 (Lokal)
    SpecialPollInterval: 3600 (Lokal)
    Type: NTP (Lokal)
    NtpServer: spdc01 spdc02 (Lokal)
    
    VMICTimeProvider (Lokal)
    DllName: C:\Windows\System32\vmictimeprovider.dll (Lokal)
    Enabled: 1 (Lokal)
    InputProvider: 1 (Lokal)
    NtpServer (Lokal)
    DllName: C:\Windows\system32\w32time.dll (Lokal)
    Enabled: 0 (Lokal)
    InputProvider: 0 (Lokal)
    
    PS H:\> w32tm /query /peers
    Anzahl Peers: 2
    
    Peer: spdc01
    Status: Ausstehend
    Verbleibende Zeit: 0.0000000s
    Modus: 0 (Reserviert)
    Stratum: 0 (nicht angegeben)
    PeerAbrufintervall: 0 (nicht angegeben)
    HostAbrufintervall: 0 (nicht angegeben)
    
    Peer: spdc02
    Status: Ausstehend
    Verbleibende Zeit: 0.0000000s
    Modus: 0 (Reserviert)
    Stratum: 0 (nicht angegeben)
    PeerAbrufintervall: 0 (nicht angegeben)
    HostAbrufintervall: 0 (nicht angegeben)
    PS H:\> w32tm /query /status
    Sprungindikator: 3(die letzte Minute umfasst 61 Sekunden)
    Stratum: 0 (nicht angegeben)
    Präzision: -6 (15.625ms pro Tick)
    Stammverzögerung: 0.0000000s
    Stammabweichung: 0.0000000s
    Referenz-ID: 0x00000000 (nicht angegeben)
    Letzte erfolgr. Synchronisierungszeit: nicht angegeben
    Quelle: Local CMOS Clock
    Abrufintervall: 10 (1024s)
    
    PS H:\>

    And here is the w32tm debug log when we execute w32tm /resync:

    149642 09:29:04.3955619s - ---------- Log File Opened -----------------
    149642 09:29:10.4759096s - RPC Caller is CARITAS-SP\Administrator (S-1-5-21-1220945662-1085031214-839522115-500)
    149642 09:29:10.4759096s - RPC Call Attribute is local=1, kernel=0, session=0, authentication=6, protocol=2, OpNum=0
    149642 09:29:10.4759096s - RPC Call - HardResync
    149642 09:29:10.4759096s - W32TmServiceMain: ********** Time Slip Notification **********
    149642 09:29:10.4769097s - ClockDispln TimeSlip:TimeSlip LastUTC:123401 SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0 
    149642 09:29:10.4769097s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
    149642 09:29:10.4769097s - W32TmServiceMain: waiting i16.000s (1024.000s)
    149642 09:29:10.4769097s - PeerPollingThread: PeerListUpdated
    149642 09:29:10.4769097s - PeerPollingThread: waiting forever
    149642 09:29:26.4778249s - W32TmServiceMain: timeout
    149642 09:29:26.4778249s - W32TmServiceMain: waiting 1024.000s
    149642 09:29:32.1961520s - RPC Caller is CARITAS-SP\Administrator (S-1-5-21-1220945662-1085031214-839522115-500)
    149642 09:29:32.1961520s - RPC Call Attribute is local=1, kernel=0, session=0, authentication=6, protocol=2, OpNum=7
    149642 09:29:32.1961520s - RPC Call - Private Log 
    149642 09:29:32.1971520s - ---------- Log File Closed -----------------

    What could we check or do to make the Windows 7 machine synchronize its time with the DCs please?

    Best Regards,


    Stefan Falk
    Thursday, September 16, 2010 10:53 AM

Answers

  • Hi,

     

    Do you have any other Windows 7 PC that has the correct time?

     

    Please make sure the Windows Time service is started.

     

    Click start, type services and press Enter. Locate and double click on the Windows time service to open its properties. Make sure the Service status is started and the  startup type is set to  Manual.

     

    Also you can disable and enable the Windows Time service to check the result.

     

    To troubleshoot this issue, please refer to Windows Time Service Tools and Settings, pay attention to the following command\settings:

     

    w32tm /resync

     

    Enable Windows NTP Client here.

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, September 21, 2010 7:47 AM

All replies

  • Hi,

     

    Thanks for posting in Microsoft TechNet forums.

     

    From your description, I understand that Windows 7 workstation fails to synchronize time with Windows Server 2003 DCs while

     

    NTP and SNTP use User Datagram Protocol (UDP) port 123 on time servers. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP or NTP servers.

     

    Please disable your firewall/antivirus software to test.

     

    Meanwhile, please refer to the following article and check if any solution applies to your situation:

     

    http://social.technet.microsoft.com/Forums/en/itprovistasetup/thread/d9c65d89-4691-4212-8991-616f01183d70

     

    http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx

     

    Best Regards

    Magon Liu

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Friday, September 17, 2010 9:09 AM
  • Hello Magon,

    Thank you for your answer. To be clear: The problem is not that the DC wouldn't synchronize with the Internet, but that a Windows 7 workstation doesn't synchronize with the DC. The DCs have no firewall active.

    I have re-run dcdiag for each DC, and every test passes.

    Can I somehow check that the workstation actually tries to synchronize with a DC? That line makes me a bit wondering:

    PS H:\> w32tm /query /source
    Local CMOS Clock

    Best Regards


    Stefan Falk
    Monday, September 20, 2010 9:40 AM
  • Hi,

     

    Do you have any other Windows 7 PC that has the correct time?

     

    Please make sure the Windows Time service is started.

     

    Click start, type services and press Enter. Locate and double click on the Windows time service to open its properties. Make sure the Service status is started and the  startup type is set to  Manual.

     

    Also you can disable and enable the Windows Time service to check the result.

     

    To troubleshoot this issue, please refer to Windows Time Service Tools and Settings, pay attention to the following command\settings:

     

    w32tm /resync

     

    Enable Windows NTP Client here.

     

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, September 21, 2010 7:47 AM
  • Hi,

     

    Thanks for posting in Microsoft TechNet forums.

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Best Regards

    Magon Liu

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, September 28, 2010 2:34 AM