Re: Problems With W2003 Time Server !

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Peter Greenway (p.greenway_at_a-m-b-s.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 15:35:04 +0100

Hi Jeff

Sorry this did not work, took off teaming so only one NIC is used and still
the same problem.

Can this be escalated ?

Peter
""Jeff Qiu [MSFT]"" <jefffqiu@online.microsoft.com> wrote in message
news:4eitpiVTEHA.2764@cpmsftngxa10.phx.gbl...
> Hi Peter,
>
> Thank you for your MPS report.
>
> I have reviewed some of the logs and noticed that the DC's configurations
> are correct except the following:
>
> * The System Event log test
> An Error Event occured. EventID: 0xC0001B58
> Time Generated: 06/04/2004 21:59:43
> Event String: The Network Load Balancing service failed to
> start due to the following error: %%1058
> An Error Event occured. EventID: 0xC0001B58
> Time Generated: 06/04/2004 21:59:44
> Event String: The Network Load Balancing service failed to
> start due to the following error: %%1058
>
> And you have mentioned that you have applied NIC teaming on your server.
I
> suggest you disable the NIC team and using a single NIC adaptor. Try to
> resync again.
>
> Please feel free to let me know if you have any further concerns or
> questions regarding the issue.
>
> Have a nice day.
>
> Best Regards,
>
> Jeff Qiu
> Microsoft Online Partner Support
> MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>
> --------------------
> >
> >Hi Peter,
> >
> >What I requested is a network MPS report as I mentioned in the previous
> >post.
> >
> >Thank you for your time!
> >
> >Best Regards,
> >
> >Jeff Qiu
> >Microsoft Online Partner Support
> >MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
> >Get Secure! - www.microsoft.com/security
> >This posting is provided "as is" with no warranties and confers no
rights.
> >
> >--------------------
> >>From: "Peter Greenway" <p.greenway@a-m-b-s.com>
> >>Newsgroups: microsoft.public.windows.server.migration
> >>Subject: Re: Problems With W2003 Time Server !
> >>Date: Thu, 3 Jun 2004 15:19:44 +0100
> >>microsoft.public.windows.server.migration
> >>
> >>Hi Jeff
> >>
> >>We do have a firewall in place but port123 is open and appears to be
> >working
> >>all okay as other Third Party packages that we have tried work fine
first
> >>time.
> >>
> >>This is the ping result:
> >>
> >>Microsoft Windows XP [Version 5.1.2600]
> >>(C) Copyright 1985-2001 Microsoft Corp.
> >>
> >>U:\>ping 130.88.202.49
> >>
> >>Pinging 130.88.202.49 with 32 bytes of data:
> >>
> >>Reply from 130.88.202.49: bytes=32 time=35ms TTL=239
> >>Reply from 130.88.202.49: bytes=32 time=34ms TTL=239
> >>Reply from 130.88.202.49: bytes=32 time=77ms TTL=239
> >>Reply from 130.88.202.49: bytes=32 time=28ms TTL=239
> >>
> >>Ping statistics for 130.88.202.49:
> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> >>Approximate round trip times in milli-seconds:
> >> Minimum = 28ms, Maximum = 77ms, Average = 43ms
> >>
> >>U:\>
> >>
> >>I checked the link but was unsure what report to download - can you
advise
> >>me.
> >>
> >>
> >>""Jeff Qiu [MSFT]"" <jefffqiu@online.microsoft.com> wrote in message
> >>news:vBaW0wVSEHA.2260@cpmsftngxa10.phx.gbl...
> >>> Hi Peter,
> >>>
> >>> Thank you for your update.
> >>>
> >>> Would you please confirm me that your DC can ping that IP address
> >>correctly?
> >>>
> >>> Do you have any firewall that between the DC and the Internet?
> >>>
> >>> If the problem persists, please collect a network MPS report and send
to
> >>me
> >>> (remove the online from the e-mail address).
> >>>
> >>> The MPS report tool can be downloaded here:
> >>>
>
>>http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408
> F
> >-
> >>> 88B7-F9C79B7306C0&displaylang=en
> >>>
> >>> I am standing by for your response.
> >>>
> >>> Best Regards,
> >>>
> >>> Jeff Qiu
> >>> Microsoft Online Partner Support
> >>> MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
> >>> Get Secure! - www.microsoft.com/security
> >>> This posting is provided "as is" with no warranties and confers no
> >rights.
> >>>
> >>> --------------------
> >>> >From: "Peter Greenway" <p.greenway@a-m-b-s.com>
> >>> >Newsgroups: microsoft.public.windows.server.migration
> >>> >Subject: Re: Problems With W2003 Time Server !
> >>> >Date: Wed, 2 Jun 2004 14:43:00 +0100
> >>> >microsoft.public.windows.server.migration
> >>> >
> >>> >Hello Jeff
> >>> >
> >>> >This is what I did, and we still get no time data is available. Does
> >>> >W32time actually work under W2003 ???
> >>> >
> >>> >I checked the registry key and it was fine.
> >>> >
> >>> >Microsoft Windows [Version 5.2.3790]
> >>> >(C) Copyright 1985-2003 Microsoft Corp.
> >>> >
> >>> >U:\>W32TM /config /manualpeerlist:130.88.202.49,0x8
> >/syncfromflags:MANUAL
> >>> >The command completed successfully.
> >>> >
> >>> >U:\>net stop w32time
> >>> >The Windows Time service is stopping.
> >>> >The Windows Time service was stopped successfully.
> >>> >
> >>> >
> >>> >U:\>net start w32time
> >>> >The Windows Time service is starting.......
> >>> >The Windows Time service was started successfully.
> >>> >
> >>> >
> >>> >U:\>w32tm /resync
> >>> >Sending resync command to local computer...
> >>> >The computer did not resync because no time data was available.
> >>> >
> >>> >U:\>
> >>> >
> >>> >
> >>> >""Jeff Qiu [MSFT]"" <jefffqiu@online.microsoft.com> wrote in message
> >>> >news:$m2D7KISEHA.484@cpmsftngxa10.phx.gbl...
> >>> >> Hi Peter,
> >>> >>
> >>> >> Thank you for your update.
> >>> >>
> >>> >> Based on your registry key value, I suggest you may check the
> >following
> >>> >> steps:
> >>> >>
> >>> >> 1. Change the following registry key:
> >>> >>
> >>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W32time\Parameters\
> >>> >> Value name: Type
> >>> >> Value type: Reg_SZ
> >>> >> Value data: NTP
> >>> >>
> >>> >> 2. Run "w32tm /config /manualpeerlist:<time source ip>,0x8
> >>> >> /syncfromflags:MANUAL"
> >>> >> NOTE: Replace the <time source ip> here with 130.88.202.49 (the ip
of
> >>> >> ntp2a.mcc.ac.uk)
> >>> >> 3. net stop w32time & net start w32time to restart the time
service.
> >>> >> 4. Run "w32tm /resync".
> >>> >>
> >>> >> Please try the steps and let me know the results.
> >>> >>
> >>> >> Thanks!
> >>> >>
> >>> >> Best Regards,
> >>> >>
> >>> >> Jeff Qiu
> >>> >> Microsoft Online Partner Support
> >>> >> MCSE 2k/2k3, MCSA 2k/2k3, MCDBA
> >>> >> Get Secure! - www.microsoft.com/security
> >>> >> This posting is provided "as is" with no warranties and confers no
> >>> rights.
> >>> >>
> >>> >> --------------------
> >>> >> >From: "Peter Greenway" <p.greenway@a-m-b-s.com>
> >>> >> >Newsgroups: microsoft.public.windows.server.migration
> >>> >> >Subject: Re: Problems With W2003 Time Server !
> >>> >> >Date: Tue, 1 Jun 2004 15:41:17 +0100
> >>> >> >Organization: Posted via Supernews, http://www.supernews.com
> >>> >> >Message-ID: <10bp5c4jtpa0ic1@corp.supernews.com>
> >>> >> >X-Tomcat-NG: microsoft.public.windows.server.migration
> >>> >> >
> >>> >> >Hi Jeff
> >>> >> >
> >>> >> >Thanks very much for the help - This is the contents of the
registry
> >>> >> export:
> >>> >> >
> >>> >> >Windows Registry Editor Version 5.00
> >>> >> >
> >>> >> >[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time]
> >>> >> >"Description"="Maintains date and time synchronization on all
> clients
> >>> and
> >>> >> >servers in the network. If this service is stopped, date and time
> >>> >> >synchronization will be unavailable. If this service is disabled,
> any
> >>> >> >services that explicitly depend on it will fail to start.
> >>> >> >
> >>> >> >"
> >>> >> >"DisplayName"="Windows Time"
> >>> >> >"ErrorControl"=dword:00000001
> >>> >>
> >>>
>
>>>>"FailureActions"=hex:05,00,00,00,00,00,00,00,00,00,00,00,02,00,00,00,64,
> 0
> >0
> >>> ,
> >>> >> 2
> >>> >> >0,\
> >>> >> > 00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00
> >>> >> >"Group"=""
> >>> >>
> >>>
>
>>>>"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00
> ,
> >6
> >>> f
> >>> >> ,
> >>> >> >00,\
> >>> >> >
> >>> >>
> >>>
>
>>>>74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,
> 7
> >3
> >>> ,
> >>> >> \
> >>> >> >
> >>> >>
> >>>
>
>>>>00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> > 6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00
> >>> >> >"Objectname"="LocalSystem"
> >>> >> >"Start"=dword:00000002
> >>> >> >"Type"=dword:00000020
> >>> >> >
> >>> >>
> >[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config]
> >>> >> >"LastClockRate"=dword:0002625a
> >>> >> >"MinClockRate"=dword:000260d4
> >>> >> >"MaxClockRate"=dword:000263e0
> >>> >> >"FrequencyCorrectRate"=dword:00000004
> >>> >> >"PollAdjustFactor"=dword:00000005
> >>> >> >"LargePhaseOffset"=dword:02faf080
> >>> >> >"SpikeWatchPeriod"=dword:00000384
> >>> >> >"HoldPeriod"=dword:00000005
> >>> >> >"LocalClockDispersion"=dword:0000000a
> >>> >> >"EventLogFlags"=dword:00000002
> >>> >> >"PhaseCorrectRate"=dword:00000007
> >>> >> >"MinPollInterval"=dword:00000006
> >>> >> >"MaxPollInterval"=dword:0000000a
> >>> >> >"UpdateInterval"=dword:00000064
> >>> >> >"MaxNegPhaseCorrection"=dword:ffffffff
> >>> >> >"MaxPosPhaseCorrection"=dword:ffffffff
> >>> >> >"AnnounceFlags"=dword:0000000a
> >>> >> >"MaxAllowedPhaseOffset"=dword:0000012c
> >>> >> >"FileLogSize"=dword:10000000
> >>> >> >"FileLogName"="c:\\windows\\debug\\w32time.log"
> >>> >> >"FileLogEntries"="0-116"
> >>> >> >
> >>> >>
> >>>
>
>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> >>> >> >"ServiceMain"="SvchostEntry_W32Time"
> >>> >>
> >>>
>
>>>>"ServiceDll"=hex(2):43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,0
> 0
> >,
> >>> 5
> >>> >> 3
> >>> >> >,\
> >>> >> >
> >>> >>
> >>>
>
>>>>00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,77,00,33,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> > 32,00,74,00,69,00,6d,00,65,00,2e,00,64,00,6c,00,6c,00,00,00
> >>> >> >"Type"="NTP"
> >>> >> >"WriteTime"="True"
> >>> >> >"ntpserver"="ntp2a.mcc.ac.uk,ntp0.uk.uu.net"
> >>> >> >
> >>> >>
> >>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Security]
> >>> >>
> >>>
>
>>>>"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,
> 0
> >0
> >>> ,
> >>> >> 0
> >>> >> >2,\
> >>> >> >
> >>> >>
> >>>
>
>>>>00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> >
> >>> >>
> >>>
>
>>>>00,00,02,00,60,00,04,00,00,00,00,00,14,00,8d,00,02,00,01,01,00,00,00,00,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> >
> >>> >>
> >>>
>
>>>>05,0b,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> >
> >>> >>
> >>>
>
>>>>20,02,00,00,00,00,14,00,9d,00,00,00,01,01,00,00,00,00,00,05,04,00,00,00,
> 0
> >0
> >>> ,
> >>> >> \
> >>> >> >
> >>> >>
> >>>
>
>>>>00,18,00,9d,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,21,02,00,00,01,
> 0
> >1
> >>> ,
> >>> >> \
> >>> >> >
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00
> >>> >> >
> >>> >>
> >>>
>
>>>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProvid
> e
> >r
> >>> s
> >>> >> ]
> >>> >> >
> >>> >>
> >>>
>
>>>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProvid
> e
> >r
> >>> s
> >>> >> \
> >>> >> >NtpClient]
> >>> >> >"Enabled"=dword:00000001
> >>> >> >"InputProvider"=dword:00000001
> >>> >> >"AllowNonstandardModeCombinations"=dword:00000001
> >>> >> >"CrossSiteSyncFlags"=dword:00000002
> >>> >> >"ResolvePeerBackoffMinutes"=dword:0000000f
> >>> >> >"ResolvePeerBackoffMaxTimes"=dword:00000007
> >>> >> >"CompatibilityFlags"=dword:80000000
> >>> >> >"EventLogFlags"=dword:00000001
> >>> >> >"LargeSampleSkew"=dword:00000003
> >>> >> >"DllName"="C:\\WINDOWS\\system32\\w32time.dll"
> >>> >> >"SpecialPollTimeRemaining"=hex(7):00,00
> >>> >> >"SpecialPollInterval"=dword:00000e10
> >>> >> >
> >>> >>
> >>>
>
>>>>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProvid
> e
> >r
> >>> s
> >>> >> \
> >>> >> >NtpServer]
> >>> >> >"InputProvider"=dword:00000000
> >>> >> >"AllowNonstandardModeCombinations"=dword:00000001
> >>> >> >"DllName"="C:\\WINDOWS\\system32\\w32time.dll"
> >>> >> >"Enabled"=dword:00000001
> >>> >> >
> >>> >>
>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Enum]
> >>> >> >"0"="Root\\LEGACY_W32TIME\\0000"
> >>> >> >"Count"=dword:00000001
> >>> >> >"NextInstance"=dword:00000001
> >>> >> >
> >>> >> >
> >>> >> >""Jeff Qiu [MSFT]"" <jefffqiu@online.microsoft.com> wrote in
message
> >>> >> >news:yapikm7REHA.3744@cpmsftngxa10.phx.gbl...
> >>> >> >> Hi Peter,
> >>> >> >>
> >>> >> >> Thank you for your update.
> >>> >> >>
> >>> >> >> Based on your description, please export the following registry
> >node
> >>> to
> >>> >> >me:
> >>> >> >>
> >>> >> >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32time
> >>> >> >>
> >>> >> >> I will do a check for you.
> >>> >> >>
> >>> >> >> You may rename that .reg file to .txt and attached in the reply
> >>here.
> >>> >> >>
> >>> >> >> Thanks!
> >>> >> >>
> >>> >> >> Best Regards,
> >>> >> >>
> >>> >> >> Jeff Qiu
> >>> >> >> Microsoft Online Partner Support
> >>> >> >> MCSE2003, MCDBA, MCSA2003
> >>> >> >> Get Secure! - www.microsoft.com/security
> >>> >> >> This posting is provided "as is" with no warranties and confers
no
> >>> >> rights.
> >>> >> >>
> >>> >> >> --------------------
> >>> >> >> >From: "Peter Greenway" <p.greenway@a-m-b-s.com>
> >>> >> >> >Newsgroups: microsoft.public.windows.server.migration
> >>> >> >> >Subject: Re: Problems With W2003 Time Server !
> >>> >> >> >Date: Mon, 31 May 2004 17:44:39 +0100
> >>> >> >> >microsoft.public.windows.server.migration
> >>> >> >> >
> >>> >> >> >Hello Jeff
> >>> >> >> >
> >>> >> >> >If life were only that easy .. tried what you suggest exactly
and
> >>it
> >>> >> >still
> >>> >> >> >does not work, the debug log looks the same to me - I have
> >>specified
> >>> >two
> >>> >> >> NTP
> >>> >> >> >time servers in the UK separated with commas as posted viz:
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>cmd
> >>> >> >> >Microsoft Windows [Version 5.2.3790]
> >>> >> >> >(C) Copyright 1985-2003 Microsoft Corp.
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>w32tm /config
> /syncfromflags:manual
> >>> >> >> >/manualpeerli
> >>> >> >> >st:ntp2a.mcc.ac.uk,ntp0.uk.uu.net
> >>> >> >> >The command completed successfully.
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>w32tm /config /update
> >>> >> >> >The command completed successfully.
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>net stop w32time
> >>> >> >> >The Windows Time service is stopping.
> >>> >> >> >The Windows Time service was stopped successfully.
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>net start w32time
> >>> >> >> >The Windows Time service is starting.......
> >>> >> >> >The Windows Time service was started successfully.
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >C:\Program Files\Support Tools>
> >>> >> >> >
> >>> >> >> >This is the resultant log file:
> >>> >> >> >
> >>> >> >> >147343 16:38:31.9062500s - ---------- Log File
> >>> >Opened -----------------
> >>> >> >> >147343 16:38:31.9062500s - Entered W32TmServiceMain
> >>> >> >> >147343 16:38:31.9062500s - CurSpc:15625000ns
BaseSpc:15625000ns
> >>> >> >> >SyncToCmos:Yes
> >>> >> >> >147343 16:38:31.9062500s - PerfFreq:2791010000c/s
> >>> >> >> >147343 16:38:31.9062500s - Time zone OK.
> >>> >> >> >147343 16:38:31.9062500s - ReadConfig: Found provider
> 'NtpClient':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'InputProvider'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: Found provider
> 'NtpServer':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'InputProvider'=0x00000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy): Found provider
> >>> >> >'NtpClient':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy):
> >>> 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy): Found provider
> >>> >> >'NtpServer':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy):
> >>> 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'PhaseCorrectRate'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> 'UpdateInterval'=0x00007530
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'FrequencyCorrectRate'=0x00000004
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'PollAdjustFactor'=0x00000005
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'LargePhaseOffset'=0x00138800
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'SpikeWatchPeriod'=0x0000005A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'HoldPeriod'=0x00000005
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'MinPollInterval'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'MaxPollInterval'=0x0000000F
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'AnnounceFlags'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'LocalClockDispersion'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxNegPhaseCorrection'=0x0000D2F0
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxPosPhaseCorrection'=0x0000D2F0
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'EventLogFlags'=0x00000002
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxAllowedPhaseOffset'=0x0000012C
> >>> >> >> >147343 16:38:31.9218750s - DomainHierarchy: LSA role change
> >>> >> >notification.
> >>> >> >> >Redetecting.
> >>> >> >> >147343 16:38:31.9218750s - DomainHierarchy: we are now the
> >>> domain
> >>> >> >> root.
> >>> >> >> >Should be advertised as reliable
> >>> >> >> >147343 16:38:31.9218750s - ClockDisciplineThread:
Starting:147343
> >>> >> >> >16:38:31.9218750s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
> >>> >> >> >147343 16:38:31.9218750s - ClockDispln: we're a reliable time
> >>service
> >>> >> >with
> >>> >> >> >no time source: LS: 0, TN: 864000000000, WAIT: 86400000
> >>> >> >> >147343 16:38:31.9218750s - Starting Providers.
> >>> >> >> >147343 16:38:31.9218750s - Starting 'NtpClient',
> >>> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - NtpTimeProvOpen("NtpClient") called.
> >>> >> >> >147343 16:38:31.9218750s - NtpProvider: Created 2 sockets (1
> >>> >> >listen-only):
> >>> >> >> >192.168.0.100:123, (127.0.0.1:123)
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting forever
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> 'CompatibilityFlags'=0x80000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'SpecialPollInterval'=0x00000E10
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'ResolvePeerBackoffMinutes'=0x0000000F
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'ResolvePeerBackoffMaxTimes'=0x00000007
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'EventLogFlags'=0x00000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'LargeSampleSkew'=0x00000003
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> 'CrossSiteSyncFlags'=0x00000002
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting 0.000s
> >>> >> >> >147343 16:38:31.9218750s - NtpClient started.
> >>> >> >> >147343 16:38:31.9218750s - Starting 'NtpServer',
> >>> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: PeerListUpdated
> >>> >> >> >147343 16:38:31.9218750s - Resolving domain hierarchy
> >>> >> >> >147343 16:38:31.9218750s - NtpTimeProvOpen("NtpServer") called.
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: WaitTimeout
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting forever
> >>> >> >> >147343 16:38:31.9375000s - RPC Caller is NT AUTHORITY\SYSTEM
> >>> >(S-1-5-18)
> >>> >> >> >147343 16:38:31.9375000s - Query 1 (BACKGROUND): <SITE:
> >>> >> >> >Active-Media-Heyford-Park, DOM: ActiveMediaHeyfordPark.local,
> >>FLAGS:
> >>> >> >> >00026B00>
> >>> >> >> >147343 16:38:32.3437500s - Query 1: no DC found.
> >>> >> >> >147343 16:38:32.3437500s - Query 4 (BACKGROUND): <SITE: (null),
> >>DOM:
> >>> >> >> (null),
> >>> >> >> >FLAGS: 00006B00>
> >>> >> >> >147343 16:38:47.3437500s - Query 4: no DC found.
> >>> >> >> >147343 16:38:47.3437500s - Logging warning: NtpClient: This
> >machine
> >>> is
> >>> >> >the
> >>> >> >> >PDC of the domain at the root of the forest, so there is no
> >machine
> >>> >> above
> >>> >> >> it
> >>> >> >> >in the domain hierarchy to use as a time source. NtpClient will
> >>fall
> >>> >> back
> >>> >> >> to
> >>> >> >> >the remaining configured time sources, if any are available.
> >>> >> >> >147343 16:38:47.3437500s - Retrying resolution for domain
> >>hierarchy.
> >>> >> >Retry
> >>> >> >> 1
> >>> >> >> >will be in 15 minutes.
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 915.422s
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 900.000s
> >>> >> >> >147343 16:38:47.3437500s - NtpServer started.
> >>> >> >> >147343 16:38:47.3437500s - Successfully started 2 providers.
> >>> >> >> >147343 16:38:47.3437500s - W32TmServiceMain: waiting i16.000s
> >>> >> (1024.000s)
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: PeerListUpdated
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 900.000s
> >>> >> >> >147343 16:38:47.3437500s - W32TmServiceMain: waiting i16.000s
> >>> >> (1024.000s)
> >>> >> >> >147343 16:38:47.4218750s - W32TimeHandler called:
> >>> >> >> >SERVICE_CONTROL_INTERROGATE
> >>> >> >> >147343 16:39:03.3593750s - W32TmServiceMain: timeout
> >>> >> >> >147343 16:39:03.3593750s - TimeProvCommand([NtpClient],
> >>> >TPC_GetSamples)
> >>> >> >> >called.
> >>> >> >> >147343 16:39:03.3593750s - NtpClient returned 0 samples.
> >>> >> >> >147343 16:39:03.3593750s - W32TmServiceMain: waiting 1024.000s
> >>> >> >> >147343 16:39:14.5625000s - W32TimeHandler called:
> >>> >> >> >SERVICE_CONTROL_INTERROGATE
> >>> >> >> >147343 16:38:31.9062500s - ---------- Log File
> >>> >Opened -----------------
> >>> >> >> >147343 16:38:31.9062500s - Entered W32TmServiceMain
> >>> >> >> >147343 16:38:31.9062500s - CurSpc:15625000ns
BaseSpc:15625000ns
> >>> >> >> >SyncToCmos:Yes
> >>> >> >> >147343 16:38:31.9062500s - PerfFreq:2791010000c/s
> >>> >> >> >147343 16:38:31.9062500s - Time zone OK.
> >>> >> >> >147343 16:38:31.9062500s - ReadConfig: Found provider
> 'NtpClient':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'InputProvider'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: Found provider
> 'NtpServer':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'InputProvider'=0x00000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy): Found provider
> >>> >> >'NtpClient':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy):
> >>> 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy): Found provider
> >>> >> >'NtpServer':
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig (policy):
> >>> 'Enabled'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'PhaseCorrectRate'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> 'UpdateInterval'=0x00007530
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'FrequencyCorrectRate'=0x00000004
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'PollAdjustFactor'=0x00000005
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'LargePhaseOffset'=0x00138800
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>'SpikeWatchPeriod'=0x0000005A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig: 'HoldPeriod'=0x00000005
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'MinPollInterval'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'MaxPollInterval'=0x0000000F
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'AnnounceFlags'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'LocalClockDispersion'=0x0000000A
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxNegPhaseCorrection'=0x0000D2F0
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxPosPhaseCorrection'=0x0000D2F0
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'EventLogFlags'=0x00000002
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> 'MaxAllowedPhaseOffset'=0x0000012C
> >>> >> >> >147343 16:38:31.9218750s - DomainHierarchy: LSA role change
> >>> >> >notification.
> >>> >> >> >Redetecting.
> >>> >> >> >147343 16:38:31.9218750s - DomainHierarchy: we are now the
> >>> domain
> >>> >> >> root.
> >>> >> >> >Should be advertised as reliable
> >>> >> >> >147343 16:38:31.9218750s - ClockDisciplineThread:
Starting:147343
> >>> >> >> >16:38:31.9218750s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
> >>> >> >> >147343 16:38:31.9218750s - ClockDispln: we're a reliable time
> >>service
> >>> >> >with
> >>> >> >> >no time source: LS: 0, TN: 864000000000, WAIT: 86400000
> >>> >> >> >147343 16:38:31.9218750s - Starting Providers.
> >>> >> >> >147343 16:38:31.9218750s - Starting 'NtpClient',
> >>> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - NtpTimeProvOpen("NtpClient") called.
> >>> >> >> >147343 16:38:31.9218750s - NtpProvider: Created 2 sockets (1
> >>> >> >listen-only):
> >>> >> >> >192.168.0.100:123, (127.0.0.1:123)
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting forever
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> 'CompatibilityFlags'=0x80000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >'SpecialPollInterval'=0x00000E10
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'ResolvePeerBackoffMinutes'=0x0000000F
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'ResolvePeerBackoffMaxTimes'=0x00000007
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
'EventLogFlags'=0x00000000
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >'LargeSampleSkew'=0x00000003
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> 'CrossSiteSyncFlags'=0x00000002
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting 0.000s
> >>> >> >> >147343 16:38:31.9218750s - NtpClient started.
> >>> >> >> >147343 16:38:31.9218750s - Starting 'NtpServer',
> >>> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: PeerListUpdated
> >>> >> >> >147343 16:38:31.9218750s - Resolving domain hierarchy
> >>> >> >> >147343 16:38:31.9218750s - NtpTimeProvOpen("NtpServer") called.
> >>> >> >> >147343 16:38:31.9218750s - ReadConfig:
> >>> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: WaitTimeout
> >>> >> >> >147343 16:38:31.9218750s - PeerPollingThread: waiting forever
> >>> >> >> >147343 16:38:31.9375000s - RPC Caller is NT AUTHORITY\SYSTEM
> >>> >(S-1-5-18)
> >>> >> >> >147343 16:38:31.9375000s - Query 1 (BACKGROUND): <SITE:
> >>> >> >> >Active-Media-Heyford-Park, DOM: ActiveMediaHeyfordPark.local,
> >>FLAGS:
> >>> >> >> >00026B00>
> >>> >> >> >147343 16:38:32.3437500s - Query 1: no DC found.
> >>> >> >> >147343 16:38:32.3437500s - Query 4 (BACKGROUND): <SITE: (null),
> >>DOM:
> >>> >> >> (null),
> >>> >> >> >FLAGS: 00006B00>
> >>> >> >> >147343 16:38:47.3437500s - Query 4: no DC found.
> >>> >> >> >147343 16:38:47.3437500s - Logging warning: NtpClient: This
> >machine
> >>> is
> >>> >> >the
> >>> >> >> >PDC of the domain at the root of the forest, so there is no
> >machine
> >>> >> above
> >>> >> >> it
> >>> >> >> >in the domain hierarchy to use as a time source. NtpClient will
> >>fall
> >>> >> back
> >>> >> >> to
> >>> >> >> >the remaining configured time sources, if any are available.
> >>> >> >> >147343 16:38:47.3437500s - Retrying resolution for domain
> >>hierarchy.
> >>> >> >Retry
> >>> >> >> 1
> >>> >> >> >will be in 15 minutes.
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 915.422s
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 900.000s
> >>> >> >> >147343 16:38:47.3437500s - NtpServer started.
> >>> >> >> >147343 16:38:47.3437500s - Successfully started 2 providers.
> >>> >> >> >147343 16:38:47.3437500s - W32TmServiceMain: waiting i16.000s
> >>> >> (1024.000s)
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: PeerListUpdated
> >>> >> >> >147343 16:38:47.3437500s - PeerPollingThread: waiting 900.000s
> >>> >> >> >147343 16:38:47.3437500s - W32TmServiceMain: waiting i16.000s
> >>> >> (1024.000s)
> >>> >> >> >147343 16:38:47.4218750s - W32TimeHandler called:
> >>> >> >> >SERVICE_CONTROL_INTERROGATE
> >>> >> >> >147343 16:39:03.3593750s - W32TmServiceMain: timeout
> >>> >> >> >147343 16:39:03.3593750s - TimeProvCommand([NtpClient],
> >>> >TPC_GetSamples)
> >>> >> >> >called.
> >>> >> >> >147343 16:39:03.3593750s - NtpClient returned 0 samples.
> >>> >> >> >147343 16:39:03.3593750s - W32TmServiceMain: waiting 1024.000s
> >>> >> >> >147343 16:39:14.5625000s - W32TimeHandler called:
> >>> >> >> >SERVICE_CONTROL_INTERROGATE
> >>> >> >> >
> >>> >> >> >""Jeff Qiu [MSFT]"" <jefffqiu@online.microsoft.com> wrote in
> >>message
> >>> >> >> >news:DIEja#sREHA.3960@cpmsftngxa10.phx.gbl...
> >>> >> >> >> Hi Peter,
> >>> >> >> >>
> >>> >> >> >> Thanks for posting!
> >>> >> >> >>
> >>> >> >> >> Before we troubleshooting this issue, I would like to
introduce
> >>> some
> >>> >> >> >> background information about Windows Time Service.
> >>> >> >> >>
> >>> >> >> >> Computers keep the time on their internal clocks, which
allows
> >>them
> >>> >to
> >>> >> >> >> perform any function that requires the date or time. For
> >>scheduling
> >>> >> >> >> purposes, however, the clocks must be set to the correct date
> >and
> >>> >> time,
> >>> >> >> >and
> >>> >> >> >> they must be synchronized with the other clocks in the
network.
> >>> >> Without
> >>> >> >> >> some other method in place, these clocks must be set
manually.
> >>> >> >> >>
> >>> >> >> >> With time synchronization, computers set their clocks
> >>automatically
> >>> >to
> >>> >> >> >> match another computer's clock. One computer maintains very
> >>> accurate
> >>> >> >> time,
> >>> >> >> >> and then all other computers set their clocks to match that
> >>> >computer.
> >>> >> >In
> >>> >> >> >> this way, you can set accurate time on all computers.
> >>> >> >> >>
> >>> >> >> >> Windows Time Service is installed by default on all computers
> >>> >running
> >>> >> >> >> Windows 2000, Windows XP, and products in the Windows Server
> >2003
> >>> >> >family.
> >>> >> >> >> Windows Time Service uses Coordinated Universal Time (UTC),
> >which
> >>> is
> >>> >> >> based
> >>> >> >> >> on an atomic time scale and is therefore independent of time
> >>zone.
> >>> >> Time
> >>> >> >> >> zone information is stored in the computer's registry and is
> >>added
> >>> >to
> >>> >> >the
> >>> >> >> >> system time just before it is displayed to the user.
> >>> >> >> >>
> >>> >> >> >> Windows Time Service starts automatically on computers that
are
> >>> >joined
> >>> >> >to
> >>> >> >> >a
> >>> >> >> >> domain. (For computers that are not joined to a domain, you
can
> >>> >start
> >>> >> >the
> >>> >> >> >> time service manually.) In a domain, time synchronization
takes
> >>> >place
> >>> >> >> when
> >>> >> >> >> Windows Time Service turns on during system startup. In the
> >>default
> >>> >> >> >> configuration, the Net Logon service looks for a domain
> >>controller
> >>> >> that
> >>> >> >> >can
> >>> >> >> >> authenticate and synchronize time with the client. When a
> domain
> >>> >> >> >controller
> >>> >> >> >> is found, the client sends a request for time and waits for a
> >>reply
> >>> >> >from
> >>> >> >> >> the domain controller. This communication is an exchange of
> >>Network
> >>> >> >Time
> >>> >> >> >> Protocol (NTP) packets intended to calculate the time offset
> and
> >>> >> >> roundtrip
> >>> >> >> >> delay between the two computers.
> >>> >> >> >>
> >>> >> >> >> In the Windows Server 2003 family, Windows Time Service
> >>> >automatically
> >>> >> >> >> synchronizes the local computer's time with other computers
on
> >>the
> >>> >> >> >network.
> >>> >> >> >> The time source for this synchronization varies, depending on
> >>> >whether
> >>> >> >the
> >>> >> >> >> computer is joined to a domain in the Active Directory
> directory
> >>> >> >service
> >>> >> >> >or
> >>> >> >> >> to a workgroup.
> >>> >> >> >>
> >>> >> >> >>
> >>> >> >> >> Based on your log file, there is no external time server set.
> >>This
> >>> >is
> >>> >> >> the
> >>> >> >> >> problem here. Here are the steps to set it.
> >>> >> >> >>
> >>> >> >> >> Configure the Windows Time Service with an external Time
Source
> >>> >> >> >>
> ----------------------------------------------------------------
> >>> >> >> >>
> >>> >> >> >> This scenario is the recommended scenario and must be used
with
> >>> >> >> >precedence.
> >>> >> >> >> Microsoft recommends that you configure the primary domain
> >>> >controller
> >>> >> >> >(PDC)
> >>> >> >> >> Emulator for the Forest Root Domain with multiple Startum 1
> NTP
> >>> >> >Servers
> >>> >> >> >to
> >>> >> >> >> make sure reliable time synchronizations. To synchronize an
> >>> >internal
> >>> >> >> time
> >>> >> >> >> server with an external time source, follow these steps:
> >>> >> >> >>
> >>> >> >> >> 1. click "Start", click "Run", type "cmd" (without the
> quotation
> >>> >> >marks),
> >>> >> >> >> and then click "OK".
> >>> >> >> >>
> >>> >> >> >> 2. At the command prompt, type the following command, and
then
> >>> press
> >>> >> >> ENTER
> >>> >> >> >> after each command:
> >>> >> >> >>
> >>> >> >> >> w32tm /config /syncfromflags:manual /manualpeerlist:PeerList
> >>> >> >> >>
> >>> >> >> >> w32tm /config /update
> >>> >> >> >>
> >>> >> >> >> Note: Peerlist is a comma-separated list of Domain Name
System
> >>> (DNS)
> >>> >> >> names
> >>> >> >> >> or IP addresses of the appropriate time sources.
> >>> >> >> >>
> >>> >> >> >> Here is an article with a list of available external Time
> >>Servers:
> >>> >> >> >> 262680 A List of the Simple Network Time Protocol Time
Servers
> >>That
> >>> >> Are
> >>> >> >> >> http://support.microsoft.com/?id=262680
> >>> >> >> >>
> >>> >> >> >> Hope this helps.
> >>> >> >> >>
> >>> >> >> >> Please feel free to let me know if you have any further
> concerns
> >>or
> >>> >> >> >> questions regarding the issue.
> >>> >> >> >>
> >>> >> >> >> Best Regards,
> >>> >> >> >>
> >>> >> >> >> Jeff Qiu
> >>> >> >> >> Microsoft Online Partner Support
> >>> >> >> >> MCSE 2000, MCDBA, MCSA
> >>> >> >> >> Get Secure! - www.microsoft.com/security
> >>> >> >> >> This posting is provided "as is" with no warranties and
confers
> >>no
> >>> >> >> rights.
> >>> >> >> >>
> >>> >> >> >> --------------------
> >>> >> >> >> >From: "Peter Greenway" <p.greenway@a-m-b-s.com>
> >>> >> >> >> >Newsgroups: microsoft.public.windows.server.migration
> >>> >> >> >> >Subject: Problems With W2003 Time Server !
> >>> >> >> >> >Date: Sun, 30 May 2004 14:57:52 +0100
> >>> >> >> >> >Organization: Active Media
> >>> >> >> >> >microsoft.public.windows.server.migration
> >>> >> >> >> >
> >>> >> >> >> >All
> >>> >> >> >> >
> >>> >> >> >> >Ever since we have installed this server we have not been
able
> >>to
> >>> >get
> >>> >> >> the
> >>> >> >> >> >Windows time server to work despite reading lots of posts on
> >the
> >>> >> >> subject,
> >>> >> >> >> >
> >>> >> >> >> >Other information:
> >>> >> >> >> >
> >>> >> >> >> >1. UDP 123 is enabled. We have tried a third party
package
> >>and
> >>> >> >this
> >>> >> >> >> >synchronises the time fine
> >>> >> >> >> >2. This is the only server we have
> >>> >> >> >> >3. O/S is W2003 standard edition
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> >This is the problem in the event log:
> >>> >> >> >> >
> >>> >> >> >> >Time Provider NtpClient: This machine is configured to use
the
> >>> >domain
> >>> >> >> >> >hierarchy to determine its time source, but it is the PDC
> >>emulator
> >>> >> for
> >>> >> >> >the
> >>> >> >> >> >domain at the root of the forest, so there is no machine
above
> >>it
> >>> >in
> >>> >> >the
> >>> >> >> >> >domain hierarchy to use as a time source. It is recommended
> >that
> >>> >you
> >>> >> >> >either
> >>> >> >> >> >configure a reliable time service in the root domain, or
> >>manually
> >>> >> >> >configure
> >>> >> >> >> >the PDC to synchronize with an external time source.
> Otherwise,
> >>> >this
> >>> >> >> >> machine
> >>> >> >> >> >will function as the authoritative time source in the domain
> >>> >> >hierarchy.
> >>> >> >> >If
> >>> >> >> >> >an external time source is not configured or used for this
> >>> >computer,
> >>> >> >you
> >>> >> >> >> may
> >>> >> >> >> >choose to disable the NtpClient.
> >>> >> >> >> >
> >>> >> >> >> >( Event ID 12 )
> >>> >> >> >> >
> >>> >> >> >> >Below is a fresh debug log from starting and stopping the
> >>server,
> >>> >we
> >>> >> >> >> believe
> >>> >> >> >> >that it is configured correctly but obviously not.
> >>> >> >> >> >
> >>> >> >> >> >If anyone can tell us what we are doing wrong and fix the
> >>problem
> >>> >we
> >>> >> >> >would
> >>> >> >> >> >be very grateful !
> >>> >> >> >> >
> >>> >> >> >> >Peter Greenway
> >>> >> >> >> >Active Media Business Solutions
> >>> >> >> >> >
> >>> >> >> >> >147342 13:43:19.7156250s - ---------- Log File
> >>> >> >Opened -----------------
> >>> >> >> >> >147342 13:43:19.7156250s - Entered W32TmServiceMain
> >>> >> >> >> >147342 13:43:19.7156250s - CurSpc:15625000ns
> >BaseSpc:15625000ns
> >>> >> >> >> >SyncToCmos:Yes
> >>> >> >> >> >147342 13:43:19.7156250s - PerfFreq:2790980000c/s
> >>> >> >> >> >147342 13:43:19.7156250s - Time zone OK.
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig: Found provider
> >>'NtpClient':
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
'Enabled'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> 'InputProvider'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig: Found provider
> >>'NtpServer':
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
'Enabled'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >> >> >'DllName'='C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> 'InputProvider'=0x00000000
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig (policy): Found
provider
> >>> >> >> >'NtpClient':
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig (policy):
> >>> >> 'Enabled'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig (policy): Found
provider
> >>> >> >> >'NtpServer':
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig (policy):
> >>> >> 'Enabled'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >'PhaseCorrectRate'=0x00000001
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>'UpdateInterval'=0x00007530
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >'FrequencyCorrectRate'=0x00000004
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >'PollAdjustFactor'=0x00000005
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >'LargePhaseOffset'=0x00138800
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >'SpikeWatchPeriod'=0x0000005A
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
'HoldPeriod'=0x00000005
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> 'MinPollInterval'=0x0000000A
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> 'MaxPollInterval'=0x0000000F
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>'AnnounceFlags'=0x0000000A
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >'LocalClockDispersion'=0x0000000A
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >> 'MaxNegPhaseCorrection'=0x0000D2F0
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >> 'MaxPosPhaseCorrection'=0x0000D2F0
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>'EventLogFlags'=0x00000002
> >>> >> >> >> >147342 13:43:19.7156250s - ReadConfig:
> >>> >> >> 'MaxAllowedPhaseOffset'=0x0000012C
> >>> >> >> >> >147342 13:43:19.7312500s - DomainHierarchy: LSA role
change
> >>> >> >> >notification.
> >>> >> >> >> >Redetecting.
> >>> >> >> >> >147342 13:43:19.7312500s - DomainHierarchy: we are now
> the
> >>> >> domain
> >>> >> >> >> root.
> >>> >> >> >> >Should be advertised as reliable
> >>> >> >> >> >147342 13:43:19.7312500s - ClockDisciplineThread:
> >>Starting:147342
> >>> >> >> >> >13:43:19.7312500s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
> >>> >> >> >> >147342 13:43:19.7312500s - ClockDispln: we're a reliable
time
> >>> >service
> >>> >> >> >with
> >>> >> >> >> >no time source: LS: 0, TN: 864000000000, WAIT: 86400000
> >>> >> >> >> >147342 13:43:19.7312500s - Starting Providers.
> >>> >> >> >> >147342 13:43:19.7312500s - Starting 'NtpClient',
> >>> >> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >> >147342 13:43:19.7312500s - NtpTimeProvOpen("NtpClient")
> called.
> >>> >> >> >> >147342 13:43:19.7312500s - NtpProvider: Created 2 sockets (1
> >>> >> >> >listen-only):
> >>> >> >> >> >192.168.0.100:123, (127.0.0.1:123)
> >>> >> >> >> >147342 13:43:19.7312500s - PeerPollingThread: waiting
forever
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> 'CompatibilityFlags'=0x80000000
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> >'SpecialPollInterval'=0x00000E10
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> >> >> >'ResolvePeerBackoffMinutes'=0x0000000F
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> >> >> >'ResolvePeerBackoffMaxTimes'=0x00000007
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>'EventLogFlags'=0x00000000
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> 'LargeSampleSkew'=0x00000003
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> 'CrossSiteSyncFlags'=0x00000002
> >>> >> >> >> >147342 13:43:19.7312500s - PeerPollingThread: waiting 0.000s
> >>> >> >> >> >147342 13:43:19.7312500s - NtpClient started.
> >>> >> >> >> >147342 13:43:19.7312500s - Starting 'NtpServer',
> >>> >> >> >> >dll:'C:\WINDOWS\system32\w32time.dll'
> >>> >> >> >> >147342 13:43:19.7312500s - PeerPollingThread:
PeerListUpdated
> >>> >> >> >> >147342 13:43:19.7312500s - Resolving domain hierarchy
> >>> >> >> >> >147342 13:43:19.7312500s - NtpTimeProvOpen("NtpServer")
> called.
> >>> >> >> >> >147342 13:43:19.7312500s - ReadConfig:
> >>> >> >> >> >'AllowNonstandardModeCombinations'=0x00000001
> >>> >> >> >> >147342 13:43:19.7312500s - PeerPollingThread: WaitTimeout
> >>> >> >> >> >147342 13:43:19.7312500s - PeerPollingThread: waiting
forever
> >>> >> >> >> >147342 13:43:19.7312500s - RPC Caller is NT AUTHORITY\SYSTEM
> >>> >> >(S-1-5-18)
> >>> >> >> >> >147342 13:43:19.7312500s - Query 1 (BACKGROUND): <SITE:
> >>> >> >> >> >Active-Media-Heyford-Park, DOM:
ActiveMediaHeyfordPark.local,
> >>> >FLAGS:
> >>> >> >> >> >00026B00>
> >>> >> >> >> >147342 13:43:20.1375000s - Query 1: no DC found.
> >>> >> >> >> >147342 13:43:20.1375000s - Query 4 (BACKGROUND): <SITE:
> (null),
> >>> >DOM:
> >>> >> >> >> (null),
> >>> >> >> >> >FLAGS: 00006B00>
> >>> >> >> >> >147342 13:43:35.1375000s - Query 4: no DC found.
> >>> >> >> >> >147342 13:43:35.1375000s - Logging warning: NtpClient: This
> >>> machine
> >>> >> is
> >>> >> >> >the
> >>> >> >> >> >PDC of the domain at the root of the forest, so there is no
> >>> machine
> >>> >> >> above
> >>> >> >> >> it
> >>> >> >> >> >in the domain hierarchy to use as a time source. NtpClient
> will
> >>> >fall
> >>> >> >> back
> >>> >> >> >> to
> >>> >> >> >> >the remaining configured time sources, if any are available.
> >>> >> >> >> >147342 13:43:35.1375000s - Retrying resolution for domain
> >>> >hierarchy.
> >>> >> >> >Retry
> >>> >> >> >> 1
> >>> >> >> >> >will be in 15 minutes.
> >>> >> >> >> >147342 13:43:35.1375000s - PeerPollingThread: waiting
915.407s
> >>> >> >> >> >147342 13:43:35.1375000s - PeerPollingThread: waiting
900.000s
> >>> >> >> >> >147342 13:43:35.1375000s - NtpServer started.
> >>> >> >> >> >147342 13:43:35.1375000s - Successfully started 2 providers.
> >>> >> >> >> >147342 13:43:35.1375000s - W32TmServiceMain: waiting
i16.000s
> >>> >> >> (1024.000s)
> >>> >> >> >> >147342 13:43:35.1375000s - PeerPollingThread:
PeerListUpdated
> >>> >> >> >> >147342 13:43:35.1375000s - PeerPollingThread: waiting
900.000s
> >>> >> >> >> >147342 13:43:35.1375000s - W32TmServiceMain: waiting
i16.000s
> >>> >> >> (1024.000s)
> >>> >> >> >> >147342 13:43:35.2625000s - W32TimeHandler called:
> >>> >> >> >> >SERVICE_CONTROL_INTERROGATE
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >>
> >>> >> >> >>
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> >>> >
> >>> >
> >>> >
> >>>
> >>
> >>
> >>
> >
> >
>
>

Relevant Pages

  • Re: NBC Ok, This Has Got To Stop
    ... We will live forever and go to listen to lots of great music and stop this ... I don't want to wear a tie. ... No sir, ... I will do what Peter tells me ...
    (rec.music.artists.springsteen)
  • Re: eingehende Mails von einer bestimmten domain verschieben
    ... ich hole die Mails vom Provider mittels eines POP-Connectors ab und habe dem ... allerdings hat der Provider des Kunden ... Guten Tag Peter, ... Die zu filternden Mails stecken einen öffentlichen Ordner, ...
    (microsoft.public.de.outlook)
  • Re: Want to build a nice Vista computer
    ... weeks is not forever but eventually you have to make a decision......and ... I waited for the April Price cuts....waited for a less expensive Nvidea ... peter wrote: ... memory kit ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Offene Rechnungen eintreiben
    ... Meines Wissens muss der Provider die Daten ... > Peter Gast schrieb: ... >> Wie schwierig ist es bei Bestellungen, ...
    (de.soc.recht.misc)
  • Re: Spam, crossposting and killfile
    ... You love to dish it but you can't take it, can you Peter? ... All in Cyberspace would hail you a hero should you decide to leave forever. ... You would know a lot about those "pathetic little games", ...
    (rec.food.cooking)