Re: NTP time service not syncing
- From: Nick Gilbert <nickg@xxxxxxxxxxxxxxxx>
- Date: Wed, 18 Jul 2007 12:40:04 +0100
I don't think I should need to open my firewall for this since as far as I know, NTP connections are outbound only and my firewall permits outbound connections on any port. Additionally, I not need my time server to be accessible from outside my LAN. You only need to open your firewall if you want your time server to be available to everyone on the whole Internet. This time server is just a PDC for my local network.
Does anybody have a way of verifying that time.nist.gov and time.windows.com are still operating?
Nick...
Haovard via WinServerKB.com wrote:
Nick,.
Just a quick question that some of my customers have done wrong:
Have you enabled accsess for the ntp port in your firewall?
Some information I picked up on a internett site: (
http://ntp.kim.lipi.go.id/index-en.htm)
NTPv4, the network time protocol Version-4 The newest version of NTP. The time server is listening on UDP port 123. SNTP, the simple network time protocol Version-4 (RFC-2030).
The time server is listening on UDP port 123.
SNTP formats are compatible to the NTP protocol specification, using a
simplified access strategy for servers and clients; the access paradigm is
identical to the UDP/TIME protocol. NTPv3, the network time protocol Version-3 (RFC-1305).
The time server is listening on UDP port 123.
NTP is a very sophisticated protocol between NTP servers and multiple peers,
using unicast and multicast addressing. NTP timestamps are represented as a
64-bit unsigned fixed-point number, in seconds since 1900-01-01 00:00.00 UTC.
The integer part is in the first 32 bits and the fraction part of the second
is in the last 32 bits. The maxmimum number is 4294967295 seconds with a
precision of about 200 picoseconds.
Håvard
Nick Gilbert wrote:Hi,
I'm getting the following errors in the event log for the w32time service:
WARNING: "Time Provider NtpClient: No valid response has been received from manually configured peer time.nist.gov,time.windows.com after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name."
and
ERROR: "The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 960 minutes. NtpClient has no source of accurate time."
How can I fix this? This server is the PDC and therefore the times on all of our computers are starting to slew off by several minutes as they take their time from the PDC.
It's configured to use time.windows.com and time.nist.gov. Is it really the case that neither of these services is operating anymore?
Thanks,
Nick...
- References:
- NTP time service not syncing
- From: Nick Gilbert
- Re: NTP time service not syncing
- From: Haovard via WinServerKB.com
- NTP time service not syncing
- Prev by Date: Re: Low disk space
- Next by Date: Re: can ping server with fqdn but not with netbios name
- Previous by thread: Re: NTP time service not syncing
- Next by thread: Re: NTP time service not syncing
- Index(es):
Relevant Pages
|
