Announcement

Collapse
No announcement yet.

Authoritative time server not getting external time

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

  • Authoritative time server not getting external time

    Hello,

    I am being plagued by a problem with my PDC (domain controller).

    I followed the instructions from MS on setting up an authoritative time server, step by step, and when I run w32tm /resync i get a message: The computer did not resync because no time data was available.

    In checking this message, sites say it's because there is no external source to get time from. I have set 3 different servers in the registry.

    I have turned on logging, see below.

    Below is the log from a W32Time server stop and restart and then a w32tm /resync right after the start up.

    I haven't been able to find anything in the registry that i missed from the KB articles.

    I also found a reference to a group policy setting that may affect it, and those are set to "not configured".

    Any help would be appreciated.

    Mark

    149236 20:22:35.2031250s - Service shutdown initiated with exit code: 0.
    149236 20:22:35.2343750s - ClockDisciplineThread: hShutDownEvent signaled. Exiting.
    149236 20:22:35.2343750s - Exiting ServiceShutdown
    149236 20:22:35.2343750s - ---------- Log File Closed -----------------
    149236 20:22:36.2812500s - ---------- Log File Opened -----------------
    149236 20:22:36.2812500s - Entered W32TmServiceMain W2K3SP1
    149236 20:22:36.2812500s - CurSpc:15625000ns BaseSpc:15625000ns SyncToCmos:Yes
    149236 20:22:36.2812500s - PerfFreq:3579545c/s
    149236 20:22:36.2812500s - Time zone OK.
    149236 20:22:36.2812500s - ReadConfig: Found provider 'NtpClient':
    149236 20:22:36.2812500s - ReadConfig: 'Enabled'=0x00000001
    149236 20:22:36.2812500s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
    149236 20:22:36.2812500s - ReadConfig: 'InputProvider'=0x00000001
    149236 20:22:36.2812500s - ReadConfig: Found provider 'NtpServer':
    149236 20:22:36.2812500s - ReadConfig: 'Enabled'=0x00000001
    149236 20:22:36.2812500s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
    149236 20:22:36.2812500s - ReadConfig: 'InputProvider'=0x00000000
    149236 20:22:36.2812500s - ReadConfig (policy): Found provider 'NtpClient':
    149236 20:22:36.2812500s - ReadConfig (policy): 'Enabled'=0x00000000
    149236 20:22:36.2812500s - ReadConfig (policy): Found provider 'NtpServer':
    149236 20:22:36.2812500s - ReadConfig (policy): 'Enabled'=0x00000000
    149236 20:22:36.2812500s - ReadConfig: 'PhaseCorrectRate'=0x00000007
    149236 20:22:36.2812500s - ReadConfig: 'UpdateInterval'=0x00000064
    149236 20:22:36.2812500s - ReadConfig: 'FrequencyCorrectRate'=0x00000004
    149236 20:22:36.2812500s - ReadConfig: 'PollAdjustFactor'=0x00000005
    149236 20:22:36.2812500s - ReadConfig: 'LargePhaseOffset'=0x02FAF080
    149236 20:22:36.2812500s - ReadConfig: 'SpikeWatchPeriod'=0x00000384
    149236 20:22:36.2812500s - ReadConfig: 'HoldPeriod'=0x00000005
    149236 20:22:36.2812500s - ReadConfig: 'MinPollInterval'=0x00000006
    149236 20:22:36.2812500s - ReadConfig: 'MaxPollInterval'=0x0000000A
    149236 20:22:36.2812500s - ReadConfig: 'AnnounceFlags'=0x00000005
    149236 20:22:36.2812500s - ReadConfig: 'LocalClockDispersion'=0x0000000A
    149236 20:22:36.2812500s - ReadConfig: 'MaxNegPhaseCorrection'=0x00000E10
    149236 20:22:36.2812500s - ReadConfig: 'MaxPosPhaseCorrection'=0x00000E10
    149236 20:22:36.2812500s - ReadConfig: 'EventLogFlags'=0x00000002
    149236 20:22:36.2812500s - ReadConfig: 'MaxAllowedPhaseOffset'=0x0000012C
    149236 20:22:36.2812500s - ReadConfig: failed. Use default one 'TimeJumpAuditOffset'=0x00007080
    149236 20:22:36.2812500s - DomainHierarchy: LSA role change notification. Redetecting.
    149236 20:22:36.2968750s - DomainHierarchy: we are now the domain root. Should be advertised as reliable
    149236 20:22:36.2968750s - ClockDisciplineThread: Starting:149236 20:22:36.2968750s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
    149236 20:22:36.2968750s - ClockDispln: we're a reliable time service with no time source: LS: 0, TN: 864000000000, WAIT: 86400000
    149236 20:22:36.2968750s - Starting Providers.
    149236 20:22:36.2968750s - Successfully started 0 providers.
    149236 20:22:36.2968750s - W32TmServiceMain: waiting i16.000s (64.000s)
    149236 20:22:36.2968750s - W32TmServiceMain: waiting i16.000s (64.000s)
    149236 20:22:38.3750000s - W32TimeHandler called: SERVICE_CONTROL_INTERROGATE
    149236 20:22:52.2968750s - W32TmServiceMain: timeout
    149236 20:22:52.2968750s - W32TmServiceMain: waiting 64.000s
    149236 20:23:11.3750000s - RPC Caller is NEVIS\markadmin (S-1-5-21-2864016548-2721457727-291041456-1106)
    149236 20:23:11.3750000s - RPC Call - HardResync
    149236 20:23:11.3750000s - W32TmServiceMain: ********** Time Slip Notification **********
    149236 20:23:11.3750000s - ClockDispln:149236 20:23:11.3750000s - ClockDispln TimeSlip:149236 20:23:11.3750000s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
    149236 20:23:11.3750000s - ClockDispln: we're a reliable time service with no time source: LS: 0, TN: 864000000000, WAIT: 86400000
    149236 20:23:11.3750000s - W32TmServiceMain: waiting i16.000s (64.000s)
    149236 20:23:27.3750000s - W32TmServiceMain: timeout
    149236 20:23:27.3750000s - W32TmServiceMain: waiting 64.000s

  • #2
    Re: Authoritative time server not getting external time

    Have you opened port 123 on the firewall as per below, also if so have you ran any logging on the firewall to check for the traffic?


    "Be sure to open UDP port 123 on the firewall at your network’s edge if you are syncing your forest root PDC Emulator to an external time source on the Internet. This is because UDP port 123 is the default port used by SNTP, which is the protocol used by W32Time for time synchronization over a network"

    Comment


    • #3
      Re: Authoritative time server not getting external time

      Hazey,

      I have ran packet captures and logs on the port UDP 123 and there are no requests from the PDC to get time. I have other non-domain attached computers that show up in the logs getting time from external time servers, like time.windows.com and others. I don't believe the problem is with a firewall blocking the port.

      It appears that the PDC is not requesting time from an external server.

      Mark

      Comment


      • #4
        Re: Authoritative time server not getting external time

        show us a dump of HKLM\SYSTEM\CurrentControlSet\Services\w32tm

        Comment


        • #5
          Re: Authoritative time server not getting external time

          Garen,

          I have attached a text file with the dump, hopefully it will help. Sorry for the delay got onto another problem.

          Mark
          Attached Files

          Comment


          • #6
            Re: Authoritative time server not getting external time

            Try going with level 2 servers, level 1 servers are usualy restiricted in some way. Also try omitting the 0x1

            http://support.microsoft.com/kb/262680

            Comment


            • #7
              Re: Authoritative time server not getting external time

              Garen,

              I have tried a variety of time servers, and none have worked, without the 0x1 you need to use ip address, which I have used both ways and still hasn't worked.

              Thanks for the advice.

              Mark

              Comment


              • #8
                Re: Authoritative time server not getting external time

                try uninstall/reinstall of the service:

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

                w32tm /config /syncfromflags:manual /manualpeerlist:<IP>
                w32tm /config /update
                w32tm /resync

                Comment


                • #9
                  Re: Authoritative time server not getting external time

                  Garen,

                  I had tried your suggestion once before, and it made no difference. This evening I checked the group policy for domain controller policy>administrative template>services>windows time again and changed it from not configured to disabled, applied the policy with gpupdate, retested, no change. Then I set it back to not configured applied policy again retested and it started to work.

                  Oh well, weeks of messing with it, for something that should have no effect on it.

                  Thanks for the suggestions, maybe some else can get theirs working with them.

                  Mark

                  Comment

                  Working...
                  X