Re: NTP time service not syncing
- From: "Bruce Sanderson" <bsanders@xxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jul 2007 12:55:53 -0700
According to http://technet2.microsoft.com/windowsserver/en/library/71e76587-28f4-4272-a3d7-7f44ca50c0181033.mspx?mfr=true, the Windows Time Service uses RFC 1305 (NTP), which is discussed at the beginning of the page you referenced. Windows 2000 used SNTP, which is a simplified way of using NTP - RFC 1769.
From what I know, the Windows Time Service (managed by the w32tm command) -Windows 2000 and later - does not use the protocols that are being deprecated by NIST per the page you reference (RFC-867 and RFC-868).
Before I sent my post 18 July 10:24, time.nist.gov was working with the time service in Windows 2003 R2 SP2 and Vista Ultimate RTM 64 bit. But, now, Windows Server 2003 R2 SP2 says it does not get valid time, so supsecting something wrong with that particular service, I sent an email to the email address identified on the page you referenced asking if there is a known issue with time.nist.gov. The response I got was:
" Yes, I know about this. The network connection is saturated and is
dropping requests.
Please continue to use one of the other servers."
Using NetMon, I found that time.nist.gov is responding (sending and receiving port was UDP 123 - the NTP port; NOT ports 13 or 37 that are being deprectated), but for some reason (perhaps the response took too long), the Windows Time Service on Windows Server 2003 R2 SP2 complains it is not getting valid time, whereas the time service on Vista says says it is getting valid time from time.nist.gov.
time-a.nist.gov and time-b.nist.gov appear to be working normally for both Windows 2003 R2 SP2 and Vista.
So, for the time being at least, I suggest using one of the other servers listed on the page at http://tf.nist.gov/service/time-servers.html, time.nrc.ca or time.windows.com.
Windows Server 2003 R2 SP2 reported "no time data was available" from time.windows.com once out of 5 tries.
--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders
It is perfectly useless to know the right answer to the wrong question.
"Coraleigh Miller" <CoraleighMiller@xxxxxxxxx> wrote in message news:O4o$4loyHHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
I just confirmed, I cannot sync with time.nist.gov but i can sync with time.windows.com & bigben.cac.washington.edu
Hope this helps.
Coraleigh Miller
"Coraleigh Miller" <CoraleighMiller@xxxxxxxxx> wrote in message news:O3cn4glyHHA.1208@xxxxxxxxxxxxxxxxxxxxxxxHi Nick,
I came across this blurb recently about time.nist.gov. You may want to try using an alternate time server, I use BigBen.cac.Washington.edu, but i am in Washington. :-)
"Starting on 14 April 2007 the server time.nist.gov will no longer respond to requests for time in the TIME format (as defined in RFC-868). These requests are generated by a number of different programs including DATE, RDATE, and other programs that connect to the time server using tcp or udp port 37. All of the other NIST servers (except for time-nw.nist.gov) will continue to respond to requests to either tcp or udp port 37 for time in the format specified in RFC-868. However, this format has poor error-handling capabilities in general, and many of the client programs that use this format are poorly written and may not handle network errors properly. Therefore users are strongly encouraged to switch to the Network Time Protocol (NTP), which is more robust and provides greater accuracy. We eventually intend to phase out support for the TIME format on all servers." http://tf.nist.gov/service/its.htm
Coraleigh Miller
"Bruce Sanderson" <bsanders@xxxxxxxxxxxxxxxxx> wrote in message news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@xxxxxxxxxxxxxxxxNot sure what your problem is, but I did test getting time (using w32tm) from time.nist.gov and it worked OK from here.
I also tried with /manualpeerlist:time.nist.gov,time.windows.com and that worked also - got time from time.nist.gov.
See the NIST NTP reference info at http://tf.nist.gov/service/time-servers.html.
--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders
It is perfectly useless to know the right answer to the wrong question.
"Nick Gilbert" <nickg@xxxxxxxxxxxxxxxx> wrote in message news:eh4p%23DSyHHA.4800@xxxxxxxxxxxxxxxxxxxxxxxHi,
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...
.
- Follow-Ups:
- Re: NTP time service not syncing
- From: Coraleigh Miller
- Re: NTP time service not syncing
- References:
- NTP time service not syncing
- From: Nick Gilbert
- Re: NTP time service not syncing
- From: Bruce Sanderson
- Re: NTP time service not syncing
- From: Coraleigh Miller
- Re: NTP time service not syncing
- From: Coraleigh Miller
- NTP time service not syncing
- Prev by Date: Re: VPN Ports
- Next by Date: Re: Windows 2003 SP2 Session_OnEnd not fire Fix
- Previous by thread: Re: NTP time service not syncing
- Next by thread: Re: NTP time service not syncing
- Index(es):
Relevant Pages
|
Loading
