kennysarmy Posted January 23, 2014 Posted January 23, 2014 My PDC had system event log errors: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD 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 AD 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. I've now run the following: C:\>net stop w32time Configure external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.uk.pool.ntp.org,1.uk.pool.ntp.org,2.uk.pool.ntp.org,3.uk.pool.ntp.org” Made PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes Start the w32time service: C:\>net start w32time If I do C:\> w32tm /query /source on my other two Domain controllers they report back correctly with the PDC name. Clients when using the same query report back any of the DC's. I am unsure how the DC's and the windows 7 clients are getting this information, it seems not be via DHCP or Group Policy.... Any ideas
hummingtech Posted January 23, 2014 Posted January 23, 2014 It's by virtue of their domain membership.
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 (edited) Both the other DC's NOT the PDC shows this error in the system event log weekly: Log Name: System Source: Microsoft-Windows-Time-Service Date: 17/01/2014 21:23:55 Event ID: 142 Task Category: None Level: Warning The time service has stopped advertising as a time source because the local clock is not synchronized. Which is what I am trying to solve.... Edited January 23, 2014 by kennysarmy
Michael Posted January 23, 2014 Posted January 23, 2014 I believe by default the 2008 R2 PDC automatically acts as the time server, which is why it's important to configure your server with a real NTP server, be it external or the Local Authority.
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 I believe by default the 2008 R2 PDC automatically acts as the time server, which is why it's important to configure your server with a real NTP server, be it external or the Local Authority. I think I've done that bit now.... It's just not knowing if this will sort the errors on the other DC;s (see post above) The times on all three DC's seem to be in sync I might add....
SHimmer45 Posted January 23, 2014 Posted January 23, 2014 +1 on the above all DC's look to the Operations Master for time syncing i believe there is an option in W32time to query the time source to see if you get a response might be worth trying that
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 w32tm /query /configuration on the DC's which are not the PDC return: C:\Windows\system32>w32tm /query /configuration [Configuration] EventLogFlags: 2 (Local) AnnounceFlags: 10 (Local) TimeJumpAuditOffset: 28800 (Local) MinPollInterval: 6 (Local) MaxPollInterval: 10 (Local) MaxNegPhaseCorrection: 172800 (Local) MaxPosPhaseCorrection: 172800 (Local) MaxAllowedPhaseOffset: 300 (Local) FrequencyCorrectRate: 4 (Local) PollAdjustFactor: 5 (Local) LargePhaseOffset: 50000000 (Local) SpikeWatchPeriod: 900 (Local) LocalClockDispersion: 10 (Local) HoldPeriod: 5 (Local) PhaseCorrectRate: 7 (Local) UpdateInterval: 100 (Local) [TimeProviders] NtpClient (Local) DllName: C:\Windows\system32\w32time.dll (Local) Enabled: 1 (Local) InputProvider: 1 (Local) CrossSiteSyncFlags: 2 (Local) AllowNonstandardModeCombinations: 1 (Local) ResolvePeerBackoffMinutes: 15 (Local) ResolvePeerBackoffMaxTimes: 7 (Local) CompatibilityFlags: 2147483648 (Local) EventLogFlags: 1 (Local) LargeSampleSkew: 3 (Local) SpecialPollInterval: 3600 (Local) Type: NT5DS (Local) NtpServer (Local) DllName: C:\Windows\system32\w32time.dll (Local) Enabled: 1 (Local) InputProvider: 0 (Local) AllowNonstandardModeCombinations: 1 (Local) VMICTimeProvider (Local) DllName: C:\Windows\System32\vmictimeprovider.dll (Local) Enabled: 1 (Local) InputProvider: 1 (Local)
hummingtech Posted January 23, 2014 Posted January 23, 2014 Assuming your machines aren't VMs then MS advice is as follows: On all other DCs use: net stop w32Time w32tm /unregister w32tm /register net start w32time to reset the time service to use NT5DS (value of which is stored here; HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters ) VM DCs should all point to the same external time provider as they pass time depending on CPU usage and often end up out of sync.
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 On the PDC: C:\Windows\system32>w32tm /resync Sending resync command to local computer The computer did not resync because no time data was available.
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 Assuming your machines aren't VMs then MS advice is as follows: On all other DCs use: net stop w32Time w32tm /unregister w32tm /register net start w32time to reset the time service to use NT5DS (value of which is stored here; HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters ) VM DCs should all point to the same external time provider as they pass time depending on CPU usage and often end up out of sync. Hi. The PDC is physical and other two domain controllers are VM's.....
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 PDC does nt look right C:\Windows\system32>w32tm /query /source Local CMOS Clock C:\Windows\system32>w32tm /query /peers #Peers: 1 Peer: "0.uk.pool.ntp.org,1.uk.pool.ntp,2.uk.pool.ntp.org,3.uk.pool.ntp.org" State: Pending Time Remaining: 847.0535070s Mode: 0 (reserved) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 0 (unspecified) C:\Windows\system32>
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 Do you have firewalls on? Firewall is turned off....
hummingtech Posted January 23, 2014 Posted January 23, 2014 Did you stop and start the time service after updating, and have you set the syncfromflags bit to facilitate autoupdating?
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 C:\Windows\system32>tracert 0.uk.pool.ntp.org Tracing route to 0.uk.pool.ntp.org [176.58.109.199] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 10.107.93.254 2 <1 ms <1 ms <1 ms 10.107.95.253 3 7 ms 7 ms 7 ms 10.104.58.223 4 9 ms 9 ms 7 ms 192.168.65.254 5 7 ms 6 ms 6 ms 192.168.168.61 6 7 ms 7 ms 7 ms 46.60.252.190 7 6 ms 6 ms * globix-gw-a.lonap.net [5.57.80.95] 8 7 ms 7 ms 7 ms 85.90.238.69 9 8 ms 8 ms 8 ms 212.111.33.238 10 7 ms 8 ms 7 ms time.videxio.net [176.58.109.199] Trace complete.
kennysarmy Posted January 23, 2014 Author Posted January 23, 2014 Did you stop and start the time service after updating, and have you set the syncfromflags bit to facilitate autoupdating? Stop and start yes - as in opening post... net stop w32time w32tm /config /syncfromflags:manual /manualpeerlist:”0.uk.pool.ntp.org,1.uk.pool.ntp,2.uk.pool.ntp.org,3.uk.pool.ntp.org” w32tm /config /reliable:yes net start w32time
hummingtech Posted January 23, 2014 Posted January 23, 2014 w32tm /config /update don't think you sent the update command when configuring which is why PDC is pendng. Might have to stop and start the service again?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now