| KB | 0000112 | |
| Dated | 10/11/09 | |
| Revision | 0.01 | |
| Event ID | Title |
| 12 22 29 36 38 47 50 |
W32 Time Time Provider NtpClient: This machine is configured.. The time provider NtpServer encountered an error while digitally.. The time provider NtpClient is configured to acquire time from one or.. The time service has not synchronized the system time for 86400.. The time provider NtpClient cannot reach or is currently receiving invalid.. Time Provider NtpClient: No valid response has been received from.. The time service detected a time difference of greater than 5000.. |
Cause: Misc Domain timing problems run through the steps below Problem Events - On the PDC Emulator Event ID 12 (W32 Time Time Provider NtpClient: This machine is configured to use {text omitted}, but it is the PDC emulator...). Problem Events - On Domain Members Event ID 50 (The time service detected a time difference of greater than 5000 milliseconds for 900 seconds...).
|
|
Fix: Step 1 Locate the PDC Emulator. 1. On a domain controller, Click Start > Run > dsa.msc{Enter} Step 2 Firewall config 1. Ensure UDP Port 123 is open outbound from the PDC Emulator. Step 3 Configure the PDC Emulator to collect Reliable Time 1. On the PDC emulator Click Start > Run > cmd {Enter} w32tm /config /manualpeerlist:ntp2d.mcc.ac.uk /syncfromflags:manual /reliable:yes /update Note: UK NTP Servers http://www.timetools.co.uk/info/ntp-servers-public/ntp-server-uk-stratum-2.htm 3. It should say "The command completed successfully." net stop "windows time" 5. It should say "The command completed successfully." --------------------------------------------------------------- For more 7. You may also see Event ID 35 --------------------------------------------------------------- For more Step 4 Check the domain clients. 1. Click Start > Run > cmd {enter} w32tm /monitor 3. You will see the time on all the domain controllers this client can see.. C:\Documents and Settings\Administrator.yourdomain>w32tm /monitor (In the case above the time on server-dc is way out address that first - it was a 2000 server and net time \\server-pdc {enter} fixed it). 4. Once all the domain controllers have a time that’s accurate (Like the last three in the example above), then proceed. net stop "windows time" 6. The Machines event log should log the following successful events Event ID 37 (The time provider NtpClient is currently receiving valid time data from..). |
|
Problems Error "The computer did not resync because no time data was available."
|
|









