NTP time service not syncing

July 18, 2007

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

July 18, 2007

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

July 18, 2007

Re: NTP time service not syncing

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

>

July 18, 2007

Re: NTP time service not syncing

Nick,

Check this out, http://www.pool.ntp.org/ , I've had good luck syncing since

switching to the pool. I use it for the domain at work, and at home.

Cleve

"Nick Gilbert" <nickg@newsgroup.nospam> wrote in message

news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

July 19, 2007

Re: NTP time service not syncing

Not 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@newsgroup.nospam> wrote in message

news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

July 19, 2007

Re: NTP time service not syncing

Hi 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@newsgroups.nospam> wrote in message

news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

> Not 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@newsgroup.nospam> wrote in message

> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>

July 20, 2007

Re: NTP time service not syncing

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@yahoo.com> wrote in message

news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

> Hi 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@newsgroups.nospam> wrote in message

> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>> Not 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@newsgroup.nospam> wrote in message

>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>

>

July 20, 2007

Re: NTP time service not syncing

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@yahoo.com> wrote in message

news:O4o$4loyHHA.5980@TK2MSFTNGP04.phx.gbl...

>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@yahoo.com> wrote in message

> news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

>> Hi 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@newsgroups.nospam> wrote in message

>> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>>> Not 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@newsgroup.nospam> wrote in message

>>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>>

>>

>

July 20, 2007

Re: NTP time service not syncing

Excellent deductive work Bruce. :-)

I expect nothing less from a fellow westcoast Canadian.

Coraleigh

"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

news:10DF3E69-09C3-471F-A4DA-5E1058DD0D67@microsoft.com...

> 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@yahoo.com> wrote in message

> news:O4o$4loyHHA.5980@TK2MSFTNGP04.phx.gbl...

>>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@yahoo.com> wrote in message

>> news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

>>> Hi 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@newsgroups.nospam> wrote in message

>>> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>>>> Not 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@newsgroup.nospam> wrote in message

>>>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>>>

>>>

>>

>

July 20, 2007

Re: NTP time service not syncing

How do you know I'm a westcoast Canadian? Have we met - sorry, I have a

terrible memory for names of people I've met!

--

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@yahoo.com> wrote in message

news:uUrex0wyHHA.1576@TK2MSFTNGP03.phx.gbl...

> Excellent deductive work Bruce. :-)

> I expect nothing less from a fellow westcoast Canadian.

>

> Coraleigh

>

> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

> news:10DF3E69-09C3-471F-A4DA-5E1058DD0D67@microsoft.com...

>> 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@yahoo.com> wrote in message

>> news:O4o$4loyHHA.5980@TK2MSFTNGP04.phx.gbl...

>>>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@yahoo.com> wrote in message

>>> news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

>>>> Hi 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@newsgroups.nospam> wrote in message

>>>> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>>>>> Not 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@newsgroup.nospam> wrote in message

>>>>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>>>>

>>>>

>>>

>>

>

July 20, 2007

Re: NTP time service not syncing

Just the shaw.ca in your tagline. :-) Im from Vancouver (originally) so I

recognized it. Dont beleive we've met though at my last job I consulted for

many companies in Vancouver and Ive been to many MVP summits etc, as my

american husbands an Exchange MVP (Kevin Miller). ahhh i miss Vancouver.

:-)

"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

news:E92E7EEF-41ED-4DE3-A7F9-73CBDA1972B7@microsoft.com...

> How do you know I'm a westcoast Canadian? Have we met - sorry, I have a

> terrible memory for names of people I've met!

>

> --

> 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@yahoo.com> wrote in message

> news:uUrex0wyHHA.1576@TK2MSFTNGP03.phx.gbl...

>> Excellent deductive work Bruce. :-)

>> I expect nothing less from a fellow westcoast Canadian.

>>

>> Coraleigh

>>

>> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

>> news:10DF3E69-09C3-471F-A4DA-5E1058DD0D67@microsoft.com...

>>> 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@yahoo.com> wrote in message

>>> news:O4o$4loyHHA.5980@TK2MSFTNGP04.phx.gbl...

>>>>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@yahoo.com> wrote in message

>>>> news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

>>>>> Hi 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@newsgroups.nospam> wrote in message

>>>>> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>>>>>> Not 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@newsgroup.nospam> wrote in message

>>>>>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>>>>>

>>>>>

>>>>

>>>

>>

>

July 21, 2007

Re: NTP time service not syncing

Excellent deductive work yourself, but not quite the right answer - I'm in

Victoria.

--

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@yahoo.com> wrote in message

news:OekgiWxyHHA.2224@TK2MSFTNGP02.phx.gbl...

> Just the shaw.ca in your tagline. :-) Im from Vancouver (originally) so

> I recognized it. Dont beleive we've met though at my last job I consulted

> for many companies in Vancouver and Ive been to many MVP summits etc, as

> my american husbands an Exchange MVP (Kevin Miller). ahhh i miss

> Vancouver. :-)

>

> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

> news:E92E7EEF-41ED-4DE3-A7F9-73CBDA1972B7@microsoft.com...

>> How do you know I'm a westcoast Canadian? Have we met - sorry, I have a

>> terrible memory for names of people I've met!

>>

>> --

>> 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@yahoo.com> wrote in message

>> news:uUrex0wyHHA.1576@TK2MSFTNGP03.phx.gbl...

>>> Excellent deductive work Bruce. :-)

>>> I expect nothing less from a fellow westcoast Canadian.

>>>

>>> Coraleigh

>>>

>>> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message

>>> news:10DF3E69-09C3-471F-A4DA-5E1058DD0D67@microsoft.com...

>>>> 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@yahoo.com> wrote in message

>>>> news:O4o$4loyHHA.5980@TK2MSFTNGP04.phx.gbl...

>>>>>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@yahoo.com> wrote in message

>>>>> news:O3cn4glyHHA.1208@TK2MSFTNGP03.phx.gbl...

>>>>>> Hi 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@newsgroups.nospam> wrote in message

>>>>>> news:ECF9B1AA-F1B9-4755-A1DA-24FF8651C0E5@microsoft.com...

>>>>>>> Not 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@newsgroup.nospam> wrote in message

>>>>>>> news:eh4p%23DSyHHA.4800@TK2MSFTNGP05.phx.gbl...

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

>>>>>>>

>>>>>>

>>>>>

>>>>

>>>

>>

>

Sign In

NTP time service not syncing

Recommended Posts

Guest Nick Gilbert

Popular Days

Popular Days

Guest Haovard via WinServerKB.com

Guest Nick Gilbert

Guest Cleve S.

Guest Bruce Sanderson

Guest Coraleigh Miller

Guest Coraleigh Miller

Guest Bruce Sanderson

Guest Coraleigh Miller

Guest Bruce Sanderson

Guest Coraleigh Miller

Guest Bruce Sanderson

Similar Content

NTP Server

Windows Clients not Picking Up NTP Time from PDC

Windows time sync advance the system time by 21 hours

problem with 'sync your settings'

Family safety sync issues

Browse

Activity

Site Info