J
John555444
Hi,
We seem to have the below warning appearing on some of our workstations and servers. No errors on the PDC.
Time Provider NtpClient: No valid response has been received from domain controller DCNAME.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. The error was: The peer is unreachable.
The errors only seem to be appearing on Server 2016 and Windows 10 machines, it seems the clients don't actually try the other DC, but they do successfully sync with this one 5 or 10 mins later. Could it be that the PDC is just busy so not allowing time sync traffic?
I don't think its high traffic on the network either as the PDC is a VMware virtual machine and some of the other servers that show this warning would communicate via the virtual switch I believe...
Before any one says about the VM syncing time with the host, this option is unticked.
Can these warnings be safely ignored? I haven't seen any other comms problems...
Continue reading...
We seem to have the below warning appearing on some of our workstations and servers. No errors on the PDC.
Time Provider NtpClient: No valid response has been received from domain controller DCNAME.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. The error was: The peer is unreachable.
The errors only seem to be appearing on Server 2016 and Windows 10 machines, it seems the clients don't actually try the other DC, but they do successfully sync with this one 5 or 10 mins later. Could it be that the PDC is just busy so not allowing time sync traffic?
I don't think its high traffic on the network either as the PDC is a VMware virtual machine and some of the other servers that show this warning would communicate via the virtual switch I believe...
Before any one says about the VM syncing time with the host, this option is unticked.
Can these warnings be safely ignored? I haven't seen any other comms problems...
Continue reading...