Time Synchronization
John Randall
external time source. I have used the following command to set the external
servers:
w32tm /config /manualpeerlist: "time.nist.gov, time.windows.com,
bigben.cac.washington.edu" /update
When I run w32time /querysntp it shows the list noted above. I can ping the
NTP servers so I know it's not a DNS issue. However, I continue to receive
Event ID 12 errors that indicate the PDC Emulator is not connecting. Our
firewall has non-restricted access for the server IP addresses so it's not a
firewall issue. Whenever I try and sync time from an other DC in the domain,
it always says that the PDC Emulator is not responding.
Any ideas?
Ulf B. Simon-Weidner
can you post the content of the registry underneath the hive HKLM\System
\CurrentControlSet\Services\w32time\Parameters of your PDC-Emulator?
Gruesse - Sincerely,
Ulf B. Simon-Weidner
Jeromy Statia [MSFT]
w32tm /config
/manualpeerlist:"time.nist.gov,time.windows.com,bigben.cac.washinton.edu"
/syncfromflags:"MANUAL" /update
this should fix up your PDC sync issues
tx
--
Jeromy Statia [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Randall" <john.r...@keithco.com> wrote in message
news:OrYMkDs5...@TK2MSFTNGP10.phx.gbl...
John Randall
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
Class Name: <NO CLASS>
Last Write Time: 1/30/2004 - 8:42 AM
Value 0
Name: type
Type: REG_SZ
Data: NTP
Value 1
Name: ServiceMain
Type: REG_SZ
Data: SvchostEntry_W32Time
Value 2
Name: ServiceDll
Type: REG_EXPAND_SZ
Data: C:\WINNT\system32\w32time.dll
Value 3
Name: NtpServer
Type: REG_SZ
Data: time.nist.gov,time.windows.com,bigben.cac.washington.edu
Value 4
Name: ReliableTimeSource
Type: REG_DWORD
Data: 0x1
Value 5
Name: WriteTime
Type: REG_SZ
Data: True
Value 6
Name: Log
Type: REG_DWORD
Data: 0x64
"Ulf B. Simon-Weidner" <nospa...@usw-consulting.com> wrote in message
news:MPG.1a83c3e5b...@msnews.microsoft.com...
John Randall
I used the command you specified but am still receiving Event ID 12 messages
which indicate synchronization is not occurring. The Win2000 w32tm command
had a -v switch for troubleshooting. However, the Win2003 versions doesn't
support the -v switch - is there something similar that I am missing?
John
"Jeromy Statia [MSFT]" <jst...@online.microsoft.com> wrote in message
news:eJPwnks5...@TK2MSFTNGP11.phx.gbl...
Jeromy Statia [MSFT]
manualpeerlist:<peers> - sets the manual peer list to <peers>,
which is a space-delimited list of DNS and/or IP addresses.
When specifying multiple peers, this switch must be enclosed in
quotes.
notice the space-delimited list of DNS and/or IP...
so you will want to have w32tim.exe /config /manualpeerlist:"time.nist.gov
time.windows.com bigben.cac.washinton.edu" /syncfromflags:"MANUAL" /update
Hope this fixes things
tx
--
Jeromy Statia [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Randall" <john.r...@keithco.com> wrote in message
news:#z7mqM15...@TK2MSFTNGP09.phx.gbl...
Ulf B. Simon-Weidner
thanks for those informations. Basically as Jeromy said you'll need to use
spaces instead of commas seperating the NTP-Server names. Also note that your
configuration depends on DNS - if DNS fails for some reason you also have
problems with the time. A failure on your ISPs DNS usually just will cause your
internet-stuff not to work, but if you provide all NTP-Servers as DNS-Names the
name resolution will also fail, which might lead into a bad time and no ability
to log onto the domain (if time difference >5min). Very unlikely, but possible.
I prefer putting at least one reliable NTP-Server in the config as IP to be
sure.
And the registry reliabletimesource is not set by default (did you write it in
there) and usually just used if the pdc-emulator is supposed to trust himself
or configured with some 3rd party time-source (hardware or software). You
should set this key to 0 when using a external timesource.
See the following article on informations about those keys:
Registry Entries for the W32Time Service
http://support.microsoft.com/?id=223184
John Randall
receiving Event ID 12. I even changed the DNS names to IP addresses just to
confirm it wasn't a name resolution issue - still no luck. Other than the
Event ID 12, what other troubleshooting is available to see wher the problem
might lie? The old w32tm -v was great but there doesn't seem to be a similar
Win2003 option. Do you have an NTP server that you feel is extremely
reliable just in case I have chosen poorly?
"Jeromy Statia [MSFT]" <jst...@online.microsoft.com> wrote in message
news:O8L$0D25DH...@TK2MSFTNGP11.phx.gbl...
Jeromy Statia [MSFT]
this by following this link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816043
HOW TO: Turn On Debug Logging in the Windows Time Service
then if you could send me the log file I can help explain why its not
syncing properly
tx
--
Jeromy Statia [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Randall" <john.r...@keithco.com> wrote in message
news:u0pNs935...@TK2MSFTNGP09.phx.gbl...
John Randall
I have made the appropriate registry changes. How long should I let the log
grow bewfore sending it to you?
John
"Jeromy Statia [MSFT]" <jst...@online.microsoft.com> wrote in message
news:OK5MCh55...@TK2MSFTNGP09.phx.gbl...
Jeromy Statia [MSFT]
send the logs.
tx
--
Jeromy Statia [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"John Randall" <john.r...@keithco.com> wrote in message
news:uEU6ekc6...@tk2msftngp13.phx.gbl...
Ulf B. Simon-Weidner [MVP]
> Well, I have done everything that you and Ulf recommended and am still
> receiving Event ID 12. I even changed the DNS names to IP addresses just to
> confirm it wasn't a name resolution issue - still no luck. Other than the
> Event ID 12, what other troubleshooting is available to see wher the problem
> might lie? The old w32tm -v was great but there doesn't seem to be a similar
> Win2003 option. Do you have an NTP server that you feel is extremely
> reliable just in case I have chosen poorly?
>
you'd also be able to run the following command to see if the time-sources are
available:
w32tm /monitor
/computers:time.nist.gov,time.windows.com,bigben.cac.washington.edu
BTW - note that you had a typo in bigben ;-)
Also w32tm /resync is the command to trigger the local NTP to resync manually
against the server configured.
John Randall
Did as you said (great idea) and received the following:
bigben.cac.washington.edu (1 of 1)...
resolving referer 85.83.78.79 (1 of 1)...
bigben.cac.washington.edu [140.142.16.34]:
ICMP: 37ms delay.
NTP: -20.3070612s offset from local clock
RefID: 'USNO' [85.83.78.79]
I then did a w32tm /resync with the following results:
The computer did not resync because no time data was available.
When I enabled logging per Jeromy, when I did the manual resync, it came up
with the following:
RPC Call - HardResync
W32TmServiceMain: ********** Time Slip Notification **********
ClockDispln:147224 23:46:30.9062500s - ClockDispln TimeSlip:147224
23:46:30.9062500s - LI:0 S:1 RDl:0 RDs:100000000 TSF:0x0
ClockDispln: we're a reliable time service with no time source: LS: 0, TN:
864000000000, WAIT: 86400000
TimeProvCommand([NtpClient], TPC_TimeJumped) called.
TimeProvCommand([NtpServer], TPC_TimeJumped) called.
W32TmServiceMain: waiting i16.000s (64.000s)
PeerPollingThread: PeerListUpdated
Resolving domain hierarchy
RPC Caller is NT AUTHORITY\SYSTEM (S-1-5-18)
Query 1 (BACKGROUND): <SITE: ORANGE-COUNTY, DOM: TKCTEST.LOCAL, FLAGS:
00026B00>
Query 1: no DC found (asked for reliable timeserv, got regular timeserv)
Query 4 (BACKGROUND): <SITE: (null), DOM: (null), FLAGS: 00006B00>
Query 4: no DC found (asked for reliable timeserv, got regular timeserv)
Retrying resolution for domain hierarchy. Retry 1 will be in 15 minutes.
PeerPollingThread: waiting 903.688s
PeerPollingThread: PeerListUpdated
PeerPollingThread: waiting 900.000s
W32TmServiceMain: timeout
TimeProvCommand([NtpClient], TPC_GetSamples) called.
NtpClient returned 0 samples.
W32TmServiceMain: waiting 64.000s
Thanks for all your help.
"Ulf B. Simon-Weidner [MVP]" <nospa...@usw-consulting.com> wrote in
message news:MPG.1a88f47e2...@msnews.microsoft.com...
John Randall
anon...@discussions.microsoft.com
I did as both of you said and received the following:
bigben.cac.washington.edu (1 of 1)...
>.
>
John Randall
had a group policy that had manually configured NTP to look for the PDC
Emulator. Now why it was applying to a Domain COntroller is another issue.
But as soon as I removed the manaul NTP server, time synch started working.
Thanks for everyones help and input.
"John Randall" <john.r...@keithco.com> wrote in message
news:urmJ$de6DH...@TK2MSFTNGP12.phx.gbl...
Ulf B. Simon-Weidner [MVP]
> It dawned on me while eating dinner - check Group Policies. Sure enough, I
> had a group policy that had manually configured NTP to look for the PDC
> Emulator. Now why it was applying to a Domain COntroller is another issue.
> But as soon as I removed the manaul NTP server, time synch started working.
>
> Thanks for everyones help and input.
>
>
sorry for getting back so late - but I'm really glad you figured it out!