Re: NTP time service not syncing

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...

--
Message posted via http://www.winserverkb.com

.

Relevant Pages

  • Re: NTP time service not syncing
    ... NTP connections are outbound only and my firewall permits outbound connections on any port. ... You only need to open your firewall if you want your time server to be available to everyone on the whole Internet. ... the network time protocol Version-4 The newest version of NTP. ...
    (microsoft.public.windows.server.general)
  • Re: How to establish connection to TCP port 13 on a remote server from within VBA?
    ... Use the time server to keep your PC clock in time, and just read that from Access. ... "well-known port) for the "daytime" protocol defined by the RFC found here: http://www.faqs.org/rfcs/rfc867.html ... For an accurate time source you'll want to use a modern protocol like NTP or Simple NTP. ...
    (comp.databases.ms-access)
  • Work anywhere time synch
    ... time server and this works ok most of the time. ... networks) I can't get through port 123 and talk to the NTP server. ...
    (comp.protocols.time.ntp)
  • Re: machines send ntp packets to 85.85.170.170
    ... NTP is the Network Time Protocol. ... machines time with that of a Time server. ... > Using a packet sniffer, I've discovered that the XP computers on my network> send ntp packets to 85.85.170.170. ...
    (microsoft.public.windowsxp.network_web)
  • Re: xntp both serve and client
    ... we only use NTP as a client. ... ntpd binds UDP port 123 on all interfaces. ... The port scan shows that ntpd is listening on 123/UDP. ... If you tell ntpd to poll certain servers that is what it will do. ...
    (comp.protocols.time.ntp)