Event 24 (Warning)

How important is this event?

Description

Time Provider NtpClient: No valid response has been received from domain controller {DC FQDN} 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.

Associated Messages

Time Provider NtpClient: No valid response has been received from domain controller WZ-VM-WDC2.webize.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.

Feb 11, 2010

Time Provider NtpClient: No valid response has been received from domain controller jmmes.JMME.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.

Jul 04, 2010

Time Provider NtpClient: No valid response has been received from domain controller ESTEE_CTCL.ESTEE.DOMAIN
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.

Oct 04, 2010

Time Provider NtpClient: No valid response has been received from domain controller amc-main.alvarado.corp
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.

Oct 06, 2010

Time Provider NtpClient: No valid response has been received from domain controller xxxxxx
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.

Nov 26, 2010

Time Provider NtpClient: No valid response has been received from domain controller xxxx-ROOT3.zzzzzzzzz.COM
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.

Jan 11, 2011

message string data: xxxxxxxxxxxxxx.xxxxx.COM

Jan 11, 2011

Time Provider NtpClient: No valid response has been received from domain controller cla003-dc00001.cplus.dom
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.

Jun 23, 2011

Time Provider NtpClient: No valid response has been received from domain controller MainSERV.bernhardt.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.

Aug 26, 2011

Time Provider NtpClient: No valid response has been received from domain controller SERVER 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.

Dec 06, 2011

Time Provider NtpClient: No valid response has been received from domain controller JUPITER.mrhhc.com
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.

Aug 15, 2012

Time Provider NtpClient: No valid response has been received from domain controller mif-dc01.rsg.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.

Aug 28, 2012

Time Provider NtpClient: No valid response has been received from domain controller sdc.cinmarlighting.ae
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.

Oct 03, 2012

Time Provider NtpClient: No valid response has been received from domain controller btp01.boddingtons.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.

Nov 28, 2012

Time Provider NtpClient: No valid response has been received from domain controller SBS.kuraas.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.

Time Provider NtpClient: No valid response has been received from domain controller ehs011
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.