Mark Minasi's Tech Forum
Register Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 3      1   2   3   Next
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #1 

AD domain with two win2016 DCs where the PDC was not advertising time properly. Fixed the advertising issue and fsmos are happily reporting from both DCs - dcdiag is all happy. But the 2nd DC will not update time from the PDC and neither will workstations.

I've made sure NT5DS is set in the registry, and announceflag is 10.  On the PDC these values are NTP and 5.

w32tm /resync /rediscover continue to give me: The computer did not resync because no time data was available.

Any thoughts would be great!

0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #2 
https://support.microsoft.com/en-us/help/929276/error-message-when-you-run-the-w32tm-resync-command-to-synchronize-win

That site mentions group policy.

https://social.technet.microsoft.com/Forums/ie/en-US/127e7fe7-6fff-469d-8536-8da1c9825cb0/the-computer-did-not-resync-because-no-time-data-was-available-w32tm?forum=winserverNIS

That site suggests some commands.

To make sure that all domain members are using it, run:
w32tm /config /syncfromflags[biggrin]omhier /update After that run:
net stop w32time
net start w32time
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #3 
yep been all through the interwebz and tried all those suggestions.  hoping the minasi crew has another more experienced take because nothing works :-)
0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #4 
Is there anything else in the event viewer?
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 232
Reply with quote  #5 
> and announceflag is 10

10, or 0x10?

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #6 
No salient events I can see.

10 decimal, 0xa hex
0
wkasdo

Avatar / Picture

Administrator
Registered:
Posts: 232
Reply with quote  #7 
Time to stop guessing... enable logging on both DCs: https://support.microsoft.com/en-us/help/816043/how-to-turn-on-debug-logging-in-the-windows-time-service

restart w32time on the PDC, then restart w32time on the other DC, and check what you have. You may have to restart w32time to flush the logs, or just wait a couple of minutes.

__________________
[MSFT]; Blog: https://blogs.technet.microsoft.com/389thoughts/
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 208
Reply with quote  #8 
Are the DC's virtual mechines (on hyper-v) ?
Check if the Time Sync is not enabled in the hyper-v settings and choose 'shutdown the VM ' if the host goes down, not Save State.

__________________
Pieter Demeulemeester
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #9 
Thanks guys.  All hyper-v settings are as they should be (first thing I checked hoping it would be that easy, sadly no).

Will turn on logging and see what turns up!
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #10 
This is what I get on dc.domain.local (the PDC's name is print.domain.local and its log looked healthy and happy):

152293 18:39:49.1572686s - ---------- Log File Opened -----------------
152293 18:39:49.1574305s - CurSpc:15625000ns BaseSpc:15625000ns SyncToCmos:Yes
152293 18:39:49.1574426s - PowerNotificationCallback: Data:0 SuspendState:0
152293 18:39:49.1574775s - PowerNotificationCallback: Ignoring resume notification since we never entered suspend state.
152293 18:39:49.1574535s - PerfFreq:10000000c/s
152293 18:39:49.1583242s - ReadConfig: Found provider 'NtpClient':
152293 18:39:49.1583496s - ReadConfig: 'Enabled'=0x00000001
152293 18:39:49.1583596s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1583650s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1583701s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1583763s - ReadConfig: 'InputProvider'=0x00000001
152293 18:39:49.1583864s - ReadConfig: Found provider 'NtpServer':
152293 18:39:49.1584022s - ReadConfig: 'Enabled'=0x00000000
152293 18:39:49.1584095s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1584144s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1584192s - ReadConfig: 'DllName'='C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1584253s - ReadConfig: 'InputProvider'=0x00000000
152293 18:39:49.1584332s - ReadConfig: Found provider 'VMICTimeProvider':
152293 18:39:49.1584440s - ReadConfig: 'Enabled'=0x00000001
152293 18:39:49.1584516s - ReadConfig: 'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
152293 18:39:49.1584567s - ReadConfig: 'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
152293 18:39:49.1584617s - ReadConfig: 'DllName'='C:\WINDOWS\System32\vmictimeprovider.dll'
152293 18:39:49.1584677s - ReadConfig: 'InputProvider'=0x00000001
152293 18:39:49.1589254s - ReadConfig: 'PhaseCorrectRate'=0x00000001 (2)
152293 18:39:49.1589444s - ReadConfig: 'UpdateInterval'=0x00057E40 (2)
152293 18:39:49.1589518s - ReadConfig: 'FrequencyCorrectRate'=0x00000004 (2)
152293 18:39:49.1589584s - ReadConfig: 'PollAdjustFactor'=0x00000005 (2)
152293 18:39:49.1589922s - ReadConfig: 'LargePhaseOffset'=0x02FAF080 (2)
152293 18:39:49.1590016s - ReadConfig: 'SpikeWatchPeriod'=0x00000384 (2)
152293 18:39:49.1590078s - ReadConfig: 'HoldPeriod'=0x00000005 (2)
152293 18:39:49.1590141s - ReadConfig: 'MinPollInterval'=0x0000000A (2)
152293 18:39:49.1590204s - ReadConfig: 'MaxPollInterval'=0x0000000F (2)
152293 18:39:49.1590263s - ReadConfig: 'AnnounceFlags'=0x0000000A (2)
152293 18:39:49.1590324s - ReadConfig: 'LocalClockDispersion'=0x0000000A (2)
152293 18:39:49.1590387s - ReadConfig: 'MaxNegPhaseCorrection'=0x0000D2F0 (2)
152293 18:39:49.1590449s - ReadConfig: 'MaxPosPhaseCorrection'=0x0000D2F0 (2)
152293 18:39:49.1590508s - ReadConfig: 'EventLogFlags'=0x00000002 (2)
152293 18:39:49.1590567s - ReadConfig: 'MaxAllowedPhaseOffset'=0x00000001 (2)
152293 18:39:49.1590629s - ReadConfig: 'UtilizeSslTimeData'=0x00000001 (2)
152293 18:39:49.1590692s - ReadConfig: 'TimeJumpAuditOffset'=0x00007080 (2)
152293 18:39:49.1590825s - lastClockRate=156250, clockPrecision=-6
152293 18:39:49.1591204s - SetTimeSlipNotification succeeds with 0x00000000.
152293 18:39:49.1592028s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
152293 18:39:49.1592292s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
152293 18:39:49.1593087s - DomainHierarchy: LSA role change notification. Redetecting.
152293 18:39:49.1604556s - ClockDisciplineThread: Starting: SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
152293 18:39:49.1614806s - Starting Providers.
152293 18:39:49.1614923s - Starting 'NtpClient', dll:'C:\WINDOWS\system32\w32time.dll'
152293 18:39:49.1615012s - LoadLibrary
152293 18:39:49.1615117s - NtpTimeProvOpen("NtpClient") called.
152293 18:39:49.1615168s - StartNtpProv
152293 18:39:49.1615251s - sysPrecision=-6, systmeClockResolution=156250
152293 18:39:49.1618368s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
152293 18:39:49.1618622s - StartListeningThread completed!
152293 18:39:49.1618990s - PeerPollingThread: waiting forever
152293 18:39:49.1619129s - StartPeerPollingThread completed!
152293 18:39:49.1619631s - ReadConfig: 'AllowNonstandardModeCombinations'=0x00000001 (2)
152293 18:39:49.1619709s - ReadConfig: 'CompatibilityFlags'=0x80000000 (2)
152293 18:39:49.1619774s - ReadConfig: 'SpecialPollInterval'=0x00093A80 (2)
152293 18:39:49.1619837s - ReadConfig: 'ResolvePeerBackoffMinutes'=0x0000000F (2)
152293 18:39:49.1619899s - ReadConfig: 'ResolvePeerBackoffMaxTimes'=0x00000007 (2)
152293 18:39:49.1619959s - ReadConfig: 'EventLogFlags'=0x00000001 (2)
152293 18:39:49.1620020s - ReadConfig: 'LargeSampleSkew'=0x00000003 (2)
152293 18:39:49.1620080s - ReadConfig: 'SignatureAuthAllowed'=0x00000001 (2)
152293 18:39:49.1620144s - ReadConfig: 'Type'=NT5DS (2)
152293 18:39:49.1620207s - ReadConfig: 'CrossSiteSyncFlags'=0x00000002 (2)
152293 18:39:49.1620266s - NTP client telemetry enabled: 0
152293 18:39:49.1620984s - AddNewPendingPeer: domain
152293 18:39:49.1621125s - StartListeningThread completed!
152293 18:39:49.1621190s - PeerPollingThread: waiting 0.000s
152293 18:39:49.1621322s - StartPeerPollingThread completed!
152293 18:39:49.1621374s - NtpClient started.
152293 18:39:49.1621424s - Logging Info: Time provider 'NtpClient' has started successfully
152293 18:39:49.1621478s - Starting 'VMICTimeProvider', dll:'C:\WINDOWS\System32\vmictimeprovider.dll'
152293 18:39:49.1621498s - PeerPollingThread: PeerListUpdated
152293 18:39:49.1621709s - Resolving domain peer
152293 18:39:49.1623670s - NetLogonGetTimeServiceParentDomain dwErr = 1355 netlogonbits = 0.
152293 18:39:49.1623780s - Query 1 (BACKGROUND): <SITE: office, DOM: domain.local, FLAGS: 00026B00>
152293 18:39:49.1628653s - LoadLibrary
152293 18:39:49.1630336s - Logging Info: Time provider 'VMICTimeProvider' has started successfully
152293 18:39:49.1630423s - Successfully started 2 providers.
152293 18:39:49.1632517s - W32TmServiceMain: waiting i16.000s (1024.000s)
152293 18:39:49.1636030s - W32TmServiceMain: Network Topology Change
152293 18:39:49.1636192s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
152293 18:39:49.1636336s - W32TmServiceMain: Network Topology Change
152293 18:39:49.1636403s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
152293 18:39:49.1770565s - PeerPollingThread: WaitTimeout
152293 18:39:49.1770877s - PeerPollingThread: waiting forever
152293 18:39:49.2707208s - Query 1: \\print.domain.local found. Score: 12
152293 18:39:49.2711594s - Association: (Local) 0.0.0.0:123 => 192.168.168.35:123 (Remote)
152293 18:39:49.2711808s - Created reachability group: (
152293 18:39:49.2711880s - 192.168.168.35:123,
152293 18:39:49.2711931s - )
152293 18:39:49.2712081s - PeerPollingThread: waiting 0.000s
152293 18:39:49.2712861s - NtpProvider: Network Topology Change
152293 18:39:49.2713221s - Reachability: removing peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123). LAST PEER IN GROUP!
152293 18:39:49.2713371s - Peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123) never sync'd, resync now!
152293 18:39:49.2713432s - Peers reset: p-p:0 a-p:1 a-x:0
152293 18:39:49.2714782s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
152293 18:39:49.2714980s - StartListeningThread completed!
152293 18:39:49.2715051s - PeerPollingThread: waiting 1.500s
152293 18:39:49.2715176s - StartPeerPollingThread completed!
152293 18:39:49.2715331s - W32TmServiceMain: waiting i15.999s (1023.999s)
152293 18:39:49.2715406s - PeerPollingThread: PeerListUpdated
152293 18:39:49.2715470s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
152293 18:39:49.2715586s - Logging error: NtpClient has been configured to acquire time from one or more time sources, however none of the sources are currently accessible and no attempt to contact a source will be made for 1 minutes. NTPCLIENT HAS NO SOURCE OF ACCURATE TIME.
152293 18:39:49.2715668s - PeerPollingThread: waiting 1.500s
152293 18:39:49.2716302s - NtpProvider: Network Topology Change
152293 18:39:49.2717081s - Peer never sync'd, resync now!
152293 18:39:49.2717194s - Peers reset: p-p:1 a-p:1 a-x:0
152293 18:39:49.2718346s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
152293 18:39:49.2718542s - StartListeningThread completed!
152293 18:39:49.2718615s - PeerPollingThread: waiting 1.500s
152293 18:39:49.2718727s - StartPeerPollingThread completed!
152293 18:39:49.2718801s - W32TmServiceMain: waiting i15.999s (1023.999s)
152293 18:39:49.2718927s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
152293 18:39:49.2718967s - PeerPollingThread: PeerListUpdated
152293 18:39:49.2719139s - Logging error: NtpClient has been configured to acquire time from one or more time sources, however none of the sources are currently accessible and no attempt to contact a source will be made for 1 minutes. NTPCLIENT HAS NO SOURCE OF ACCURATE TIME.
152293 18:39:49.2719220s - PeerPollingThread: waiting 1.500s
152293 18:39:50.7706905s - PeerPollingThread: WaitTimeout
152293 18:39:50.7707158s - PeerPollingThread: waiting 0.001s
152293 18:39:50.7863175s - PeerPollingThread: WaitTimeout
152293 18:39:50.7863481s - Resolving domain peer
152293 18:39:50.7867236s - NetLogonGetTimeServiceParentDomain dwErr = 1355 netlogonbits = 0.
152293 18:39:50.7867368s - Query 1 (BACKGROUND): <SITE: office, DOM: domain.local, FLAGS: 00026B00>
152293 18:39:50.7870563s - Query 1: \\print.domain.local found. Score: 12
152293 18:39:50.7873732s - Association: (Local) 0.0.0.0:123 => 192.168.168.35:123 (Remote)
152293 18:39:50.7873921s - Created reachability group: (
152293 18:39:50.7873987s - 192.168.168.35:123,
152293 18:39:50.7874038s - )
152293 18:39:50.7874188s - PeerPollingThread: waiting 0.000s
152293 18:39:50.7874377s - PeerPollingThread: WaitTimeout
152293 18:39:50.7874379s - PeerPollingThread: PeerListUpdated
152293 18:39:50.7874532s - Reachability: Attempting to contact peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123).
152293 18:39:50.7874634s - Polling peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123)
152293 18:39:50.7874749s - Sending packet to print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123) in Win2K detect mode, stage 1.
152293 18:39:50.7875053s - PeerPollingThread: waiting forever
152293 18:39:50.7875457s - Peer poll: Max:1024.0000000s Cur:00.0000000s
152293 18:39:50.7875559s - PeerPollingThread: waiting 1024.000s
152293 18:39:51.1647216s - W32TimeHandler called: SERVICE_CONTROL_INTERROGATE
152293 18:40:05.2789628s - W32TmServiceMain: timeout
152293 18:40:05.2790028s - Sample Prepared at 131581824052789990 for peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123)
152293 18:40:05.2790157s - W32TmServiceMain: waiting 1024.000s
152293 18:40:30.7905749s - ListeningThread -- DataAvailEvent set for socket 1 (0.0.0.0:123)
152293 18:40:30.7906180s - ListeningThread -- response heard from 192.168.168.168:123 <- 192.168.168.10:123
152293 18:40:30.7906411s - Ignoring packet invalid mode combination (in:3 out:0).
152293 18:40:56.1244581s - RPC Caller is domain\administrator (S-1-5-21-860921380-982290669-229010428-500)
152293 18:40:56.1244828s - RPC Call Attribute is local=1, kernel=0, session=0, authentication=6, protocol=2, OpNum=0
152293 18:40:56.1244988s - RPC Call - Rediscover
152293 18:40:56.1245051s - W32TmServiceMain: Network Topology Change (RPC)
152293 18:40:56.1245112s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
152293 18:40:56.1245300s - NtpProvider: Network Topology Change
152293 18:40:56.1245695s - Reachability: removing peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123). LAST PEER IN GROUP!
152293 18:40:56.1245821s - Peers reset: p-p:0 a-p:1 a-x:0
152293 18:40:56.1247397s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
152293 18:40:56.1247611s - StartListeningThread completed!
152293 18:40:56.1247686s - PeerPollingThread: waiting 958.663s
152293 18:40:56.1247793s - StartPeerPollingThread completed!
152293 18:40:56.1247908s - W32TmServiceMain: waiting 973.154s
152293 18:40:56.1247994s - W32TmServiceMain: ********** Time Slip Notification **********
152293 18:40:56.1248032s - PeerPollingThread: PeerListUpdated
152293 18:40:56.1248158s - PeerPollingThread: waiting 958.663s
152293 18:40:56.1248162s - ClockDispln TimeSlip: SetUnsync: LI:3 S:0 RDl:0 RDs:0 TSF:0x0
152293 18:40:56.1248615s - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
152293 18:40:56.1248768s - W32TmServiceMain: waiting i16.000s (1024.000s)
152293 18:40:56.1248824s - PeerPollingThread: PeerListUpdated
152293 18:40:56.1248917s - Resolving domain peer
152293 18:40:56.1259428s - NetLogonGetTimeServiceParentDomain dwErr = 1355 netlogonbits = 0.
152293 18:40:56.1259595s - Query 1 (FORCE): <SITE: office, DOM: domain.local, FLAGS: 00026A01>
152293 18:40:56.2347756s - Query 1: \\print.domain.local found. Score: 12
152293 18:40:56.2351389s - Association: (Local) 0.0.0.0:123 => 192.168.168.35:123 (Remote)
152293 18:40:56.2351577s - Created reachability group: (
152293 18:40:56.2351644s - 192.168.168.35:123,
152293 18:40:56.2351693s - )
152293 18:40:56.2351851s - PeerPollingThread: waiting 0.000s
152293 18:40:56.2352058s - PeerPollingThread: WaitTimeout
152293 18:40:56.2352047s - PeerPollingThread: PeerListUpdated
152293 18:40:56.2352192s - Reachability: Attempting to contact peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123).
152293 18:40:56.2352256s - Polling peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123)
152293 18:40:56.2352323s - Sending packet to print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123) in Win2K detect mode, stage 1.
152293 18:40:56.2352514s - PeerPollingThread: waiting forever
152293 18:40:56.2353043s - Peer poll: Max:1024.0000000s Cur:00.0000000s
152293 18:40:56.2353148s - PeerPollingThread: waiting 1024.000s
152293 18:41:05.3139243s - ListeningThread -- DataAvailEvent set for socket 1 (0.0.0.0:123)
152293 18:41:05.3139663s - ListeningThread -- response heard from 192.168.168.25:123 <- 192.168.168.10:123
152293 18:41:05.3139839s - Ignoring packet invalid mode combination (in:3 out:0).
152293 18:41:12.1175372s - W32TmServiceMain: timeout
152293 18:41:12.1175704s - Sample Prepared at 131581824721175664 for peer print.domain.local (ntp.d|0.0.0.0:123->192.168.168.35:123)
152293 18:41:12.1175839s - W32TmServiceMain: waiting 1024.000s

0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #11 
Got this in the event viewer:

Time Provider NtpClient: No valid response has been received from domain controller print.domain.local after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable. 

So print thinks it's happily advertising as a proper time source, but dc thinks it's unreachable.  DCDIAG shows no issues.  Is it some kind of weird firewall issue?
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #12 
Just checked and print's windows firewall was actually turned off.  Turned it on but of course no change.
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 208
Reply with quote  #13 

Hi Wes,
- does other clients (PC's and/or member servers) in the same site update there time from the PDC correctly ?
- no other firewall between PRINT and DC ?
- PRINT and DC are in the same AD-site ?
Just trying to isolate the problem and giving you some things that maybe will set you in the correct direction to solve this.

These are my settings:
on the PDCe :
HKLM\System\CurrentControlSet\Services\W32Time\Parameters
  - NtpServer = be.pool.ntp.org         (<- be is Belgium where I live)
  - Type = NTP
HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config
  - MaxPosPhaseCorrection = 300 (decimal)
  - MaxNegPhaseCorrection = 300 (decimal)


On all other DC’s and member servers and PC's
(alle settings left default)
 

HKLM\System\CurrentControlSet\Services\W32Time\Parameters


__________________
Pieter Demeulemeester
0
Wes

Senior Member
Registered:
Posts: 231
Reply with quote  #14 
WOrkstations report the same thing as the other DC.  No other firewalls.  Print and DC are in the same site and subnet as are the workstations.  I have run into all the things you mention in other environments but this one is so flat and simple I have no idea what it could be.

We have the settings except the config values are 54000 instead of 300...
0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #15 
You didn't say what Event ID was in the event viewer. Was it 24?

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.