Unable to sync time - The computer did not resync because no time data was available.

Question

Unable to sync time - The computer did not resync because no time data was available.

The environment is:

PDC emulator running WIn2019 and used as time source for the entire domain, UDP/123 allowed on the local firewall and PDC emulator since 25/10/2019

Reliable time source for PDC emulator is the Cesium atomic clocks from: http://pcdsh01.on.br/HoraLegalBrasileira.php (less than 1 second error on 10 MILLION years) and following the guidelines of the "authoratiative time server", running OK since then

Serveral Windows domain-members and some Linux machines (using ntp.conf pointing to the FQDN of the PDC emulator)

Occasionaly, some WIndows machines are getting 4 to 5 minutes late and the resync is impossible, i ended up setting clocks manually and some of then, on the next day, got to be late gain, 4-5 minutes

So, on my domain members i tried:

net stop w32time
net start w32time
w32tm /config /update
w32tm /resync /rediscover

net time \ntp /set /yes
w32tm /config /computer:ntp /update /syncfromflags:DOMHIER

w32tm /resync /computer:ntp
Sending resync command to ntp...
The computer did not resync because no time data was available.

The last error is particularly weird, because I can´t see any reason on why data couldn´t be available

Besides manual intervention, why can´t I just re-sync and set the cloks at the first attempt, why is sometimes so difficult to set time?

============= WINDOWS CLIENT =====================================
[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 10 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 10 (Local)
MaxPollInterval: 15 (Local)
MaxNegPhaseCorrection: 4294967295 (Local)
MaxPosPhaseCorrection: 4294967295 (Local)
MaxAllowedPhaseOffset: 300 (Local)

FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 1 (Local)
UpdateInterval: 30000 (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: 0 (Local)
InputProvider: 0 (Local)

============= WINDOWS CLIENT =====================================

============= WINDOWS SERVER - PDC EMULATOR =====================================

[Configuration]

EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 3600 (Local)
MaxPosPhaseCorrection: 1800 (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: 900 (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)

============= WINDOWS SERVER - PDC EMULATOR =====================================

Answer 1

Hi,
I cant tell you the resolution. But, can guide you with troubleshooting.
Hope this will help

First and Foremost, if the affected machine is hosted on VM, disable VMICTimeSync
This settings forces the machine to sync time from VM Host which is not recommended when you want the clients to sync time from AD.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider\Enabled --> 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider\InputProvider --> 0

---

Increase the event log flags
This will generate some more information and log events under system event logs

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\EventLogFlags --> 2
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\EventLogFlags --> 2

---

Enable time debug log
This is plaintext and will give you detailed information about what happened

https://support.microsoft.com/en-gb/office/how-to-turn-on-debug-logging-in-the-windows-time-service-8decbb8b-b178-ab87-9f42-bcaba7579741#:~:text=%20To%20turn%20on%20debug%20logging%20in%20the,name%3A%20FileLogName%0AData%20Type%3A%20String%0AValue%20data%3A%20C%3AWindowsTempw32time.log%0AThis...%20More%20

Answer 2

No matter what I do and how many times, this one machine will always state:

PS C:\WINDOWS\system32> w32tm /query /source

Local CMOS Clock

PS C:\WINDOWS\system32> w32tm /resync /rediscover

Sending resync command to local computer

The computer did not resync because no time data was available.