Announcement

Collapse
No announcement yet.

W32tm is not updating the clock

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • W32tm is not updating the clock

    Hello Team,

    I need a set of eyes to see why my Windows 7 clients clock is not working.
    I'm running windows 2008r2 on my PDC emulator. I set my PDC server to sync with external time source.
    It's working fine, and other member DCs also sync to this PDC server just the way it suppose to be.

    the problem is on the windows 7 clients that I'm testing. I use GPO to update the time on the client. GPO applied correctly. I am able to run w32tm /resync on the client. and do the /query /status successfully update to the PDC server. BUT the clock remain the same. It's won't change to match the PDC server clock.

    *********************************************
    Here is the result on the client

    C:\....>w32tm /query /status
    Leap Indicator: 0(no warning)
    Stratum: 5 (secondary reference - syncd by (S)NTP)
    Precision: -6 (15.625ms per tick)
    Root Delay: 0.0312500s
    Root Dispersion: 16.0100000s
    ReferenceId: 0xAC1E030C (source IP: 172.30.3.12)
    Last Successful Sync Time: 9/9/2013 3:04:05 PM
    Source: InternalNPT.mydomain.local
    Poll Interval: 10 (1024s)
    ********************************************

    Client config
    ********************************
    C:\....>w32tm /query /configuration
    [Configuration]
    EventLogFlags: 2 (Local)
    AnnounceFlags: 5 (Local)
    TimeJumpAuditOffset: 28800 (Local)
    MinPollInterval: 10 (Local)
    MaxPollInterval: 15 (Local)
    MaxNegPhaseCorrection: 4294967295 (Local)
    MaxPosPhaseCorrection: 4294967295 (Local)
    MaxAllowedPhaseOffset: 300 (Local)
    FrequencyCorrectRate: 4 (Local)
    PollAdjustFactor: 5 (Local)
    LargePhaseOffset: 50000000 (Local)
    SpikeWatchPeriod: 900 (Local)
    LocalClockDispersion: 10 (Local)
    HoldPeriod: 5 (Local)
    PhaseCorrectRate: 1 (Local)
    UpdateInterval: 30000 (Local)

    [TimeProviders]
    NtpClient (Local)
    DllName: C:\windows\system32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    CrossSiteSyncFlags: 1 (Policy)
    AllowNonstandardModeCombinations: 1 (Local)
    ResolvePeerBackoffMinutes: 15 (Policy)
    ResolvePeerBackoffMaxTimes: 7 (Policy)
    CompatibilityFlags: 2147483648 (Local)
    EventLogFlags: 0 (Policy)
    LargeSampleSkew: 3 (Local)
    SpecialPollInterval: 3600 (Policy)
    Type: NT5DS (Policy)
    VMICTimeProvider (Local)
    DllName: C:\windows\System32\vmictimeprovider.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    NtpServer (Local)
    DllName: C:\windows\system32\w32time.DLL (Local)
    Enabled: 0 (Local)
    InputProvider: 0 (Local)

    ***************************
    has anyone experience a simular issue?

    Thanks,
    HN

  • #2
    Re: W32tm is not updating the clock

    Configure a client computer for automatic domain time synchronization

    can you update the time manually? if so, then i would relook at the policy you have in place...

    you must have domain admin rights to update the time remotely, or local admin at the box.
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: W32tm is not updating the clock

      Originally posted by James Haynes View Post
      Configure a client computer for automatic domain time synchronization

      can you update the time manually? if so, then i would relook at the policy you have in place...

      you must have domain admin rights to update the time remotely, or local admin at the box.

      I ran w32tm update on client using my domain admin crendiential. "The command completed successfully. but the clock still not change.

      I also give user temporary local admin rights and run the w32tm command. but the clock also wont change.

      I'm sure what Im doing wrong.. I have my test environment and the clients working fine.

      Comment


      • #4
        Re: W32tm is not updating the clock

        What is the time difference between your clients and servers?

        Comment


        • #5
          Re: W32tm is not updating the clock

          Originally posted by wullieb1 View Post
          What is the time difference between your clients and servers?
          Well, I'm testing the synchronization between the clients and PDC (internal time server). I rolled the PDC time back/forward for a few mins. then turn the manual update on the client with /sync command using the domain admin.

          The command executed successfully and the /source pointed to the correct PDC server. but the clock on the client is not change to match the PDC clock.

          in my test environment the clients react to the exact clock as the PDC where the clients are pointed too.

          All the settings exactly the same between the testing and production environment.

          I have spend a lots of time and read many many articles on line but I keep spinning my wheels. so I wonder if anyone has run into this issues as I do.

          Thanks,
          HN

          Comment


          • #6
            Re: W32tm is not updating the clock

            Your clients should automatically sync time with the PDC emulator. This is by design. It is however allowed a time skew of 5 mins, Kerberos.

            On your affected clients reset the time service to defaults:

            Open a command prompt

            net stop w32time
            w32tm /unregister
            w32tm /register
            net start w32time

            Taken from here

            http://technet.microsoft.com/en-us/l...(v=WS.10).aspx

            Comment


            • #7
              Re: W32tm is not updating the clock

              Originally posted by wullieb1 View Post
              Your clients should automatically sync time with the PDC emulator. This is by design. It is however allowed a time skew of 5 mins, Kerberos.

              On your affected clients reset the time service to defaults:

              Open a command prompt

              net stop w32time
              w32tm /unregister
              w32tm /register
              net start w32time

              Taken from here

              http://technet.microsoft.com/en-us/l...(v=WS.10).aspx
              This is the issue that I'm having.. try to sync the time between the client and PDC.



              Let say.. the current time is 11:45PM.

              On the PDC is 11:45PM and Client is ~11:45PM



              1. I changed my PDC back to 11:42PM for testing purpose to see the client and PDC clock sync.



              I also reboot clients many times.. still no effects..



              Scenario 1:

              On my windows 7 client.

              1. I logon as Domain admins.

              2. I ran w32tm /resync or /resync /update

              .... Command executed sussessfully

              The client clock still say ~11:45

              3. I ran w32tm /query /status on the client.

              ... it said client update successfully from PDC. but clock still wont change to match PDC.



              Scenario 2:

              On my windows 7 client.

              1. I logon as Domain admins.

              I do the following:

              net stop w32time

              w32tm /unregister

              w32tm /register

              net start w32time

              2. I ran w32tm /resync or /resync /update

              .... Command executed sussessfully

              The client clock still say ~11:45

              3. I ran w32tm /query /status on the client.

              ... it said client update successfully from PDC. but clock still wont change to match PDC.



              on the test environment..

              everytime I execute /resync on the client. The client clock changed to match the PDC clock.



              I'm welcome any ideas or anything to try.



              Thanks,

              HN
              Last edited by Humannetwork; 10th September 2013, 04:37.

              Comment


              • #8
                Re: W32tm is not updating the clock

                Remove the GPO and restest.

                Comment


                • #9
                  Re: W32tm is not updating the clock

                  Originally posted by wullieb1 View Post
                  Remove the GPO and restest.
                  I have some PC in the test GPO OU and some not in the testing GPO OU..
                  They all reacted the same.. pointed to the correct source but clock remain unchange

                  Comment


                  • #10
                    Re: W32tm is not updating the clock

                    Update:

                    After I've spent a bit more of thinking, and more reading.. I think my NTP environment is working as expected.

                    all my clients are pointing to the correct DOMHIER.
                    instead of reset the PDCe time.. I reset the client local time then I resync again.
                    The client clock changed with a few seconds difference with PDCe.

                    SO I think it is working.

                    I appreciate everyone inputs.. I valued each of everyone of your inputs.

                    Thanks,
                    HN

                    Comment

                    Working...
                    X