I
INDYICEMAN
Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 1/4/2020 5:06:10 AM
Event ID: 134
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-10C8IUP
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
Community friends,
Ever since the calendar rolled into 2020, I have been getting this logged Event ID 134 (see below).
This appears to be occurring at my every morning startup and login to my PC.
Would anyone have any thoughts or comments on why this may be happening?
Many thanks!
IndyIceMan
_____________________________________________________________________________________________________________________
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>134</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-01-04T10:06:10.415885400Z" />
<EventRecordID>10778</EventRecordID>
<Correlation />
<Execution ProcessID="13668" ThreadID="11484" />
<Channel>System</Channel>
<Computer>DESKTOP-10C8IUP</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_MANUAL_PEER_DNS_ERROR">
<Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
<Data Name="RetryMinutes">15</Data>
<Data Name="DomainPeer">time.windows.com,0x9</Data>
</EventData>
________________________________________________________________________________________________________________________
Continue reading...
Source: Microsoft-Windows-Time-Service
Date: 1/4/2020 5:06:10 AM
Event ID: 134
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: DESKTOP-10C8IUP
Description:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
Event Xml:
Community friends,
Ever since the calendar rolled into 2020, I have been getting this logged Event ID 134 (see below).
This appears to be occurring at my every morning startup and login to my PC.
Would anyone have any thoughts or comments on why this may be happening?
Many thanks!
IndyIceMan
_____________________________________________________________________________________________________________________
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06edcfeb-0fd0-4e53-acca-a6f8bbf81bcb}" />
<EventID>134</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-01-04T10:06:10.415885400Z" />
<EventRecordID>10778</EventRecordID>
<Correlation />
<Execution ProcessID="13668" ThreadID="11484" />
<Channel>System</Channel>
<Computer>DESKTOP-10C8IUP</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData Name="TMP_EVENT_MANUAL_PEER_DNS_ERROR">
<Data Name="ErrorMessage">No such host is known. (0x80072AF9)</Data>
<Data Name="RetryMinutes">15</Data>
<Data Name="DomainPeer">time.windows.com,0x9</Data>
</EventData>
________________________________________________________________________________________________________________________
Continue reading...