Re: Is there a problem with time.windows.com?



David,
if it is only once in a while and only one error, don't worry about it.
There can be many reasons - lost packets, hiccup on one of the routers along
the way....
How often does this still show up?

--
Claus
"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4CB2AB9-B939-4098-A67B-16E130F8D170@xxxxxxxxxxxxxxxx
Don't know how to tell you this but something is still wrong. The
Win32time
errors are still appearing on all servers!

W32Time
29 14/08/2007 05:08 13 *
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 15 minutes. NtpClient has no
source of accurate time.

C:\>net time /querysntp
The current SNTP value is:
0.uk.pool.ntp.org,1.uk.pool.ntp.org,2.uk.pool.ntp.org
,3.uk.pool.ntp.org

The command completed successfully.


C:\>

Something trivial I hope?

Grateful for any assistance.
--
David @ Solsletta


"Claus" wrote:

That should work just fine.

--
Claus
"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75E1CA13-69DF-46AF-A56A-C42DCE2B5F7E@xxxxxxxxxxxxxxxx
Claus

Many thanks. I've made the changes. I let you know know how it
proceeds.

The syntaxt I used is:

net time
/setsntp:"0.uk.pool.ntp.org,1.uk.pool.ntp.org,2.uk.pool.ntp.org,3.uk.pool.ntp.org"
--
David @ Solsletta


"Claus" wrote:

You forgot to put a "," between the servers. It should look like
0.uk.pool.ntp.org,1.uk.pool.ntp.org,2.uk.pool.ntp.org,3.uk.pool.ntp.org
(no
spaces)

--
Claus
"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:45A2BBB4-629D-4375-9282-3F10B4144675@xxxxxxxxxxxxxxxx
Susan

Oops.

C:\>net time /querysntp
The current SNTP value is: 0.uk.pool.ntp.org 1.uk.pool.ntp.org
2.uk.pool.ntp.org
3.uk.pool.ntp.org

achived using the net time /setsntp: command.

However on all of them:

W32Time
29 05/08/2007 04:28 2 *
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 15 minutes. NtpClient
has
no
source of accurate time.

and on one:

W32Time
17 04/08/2007 13:28 2 *
Time Provider NtpClient: An error occurred during DNS lookup of the
manually
configured peer 'time.windows.com,0x1'. NtpClient will try the DNS
lookup
again in 60 minutes. The error was: No such service is known. The
service
cannot be found in the specified name space. (0x8007277C)

Port 123 is open for UDP.

I'm in the UK (obviously). What have I done wrong?
--
David @ Solsletta


"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:

A lot of us have stopped using time.windows.com

http://www.oreillynet.com/onlamp/blog/2006/02/help_save_the_endangered_time.html
Don't use nist's either.

David wrote:
On nine servers I have:

W32Time 29 28/07/2007 20:46 1
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 xxx minutes.
NtpClient
has
no
source of accurate time.

although port 123 is open inbound for udp and tcp.

I seem to see this error intermittently but for some weeks /
months
it
has
been ongoing.

Should I change my ports / time source?

--
David @ Solsletta


"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:

A lot of us have stopped using time.windows.com

http://www.oreillynet.com/onlamp/blog/2006/02/help_save_the_endangered_time.html
Don't use nist's either.

David wrote:
On nine servers I have:

W32Time 29 28/07/2007 20:46 1
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 xxx minutes.
NtpClient
has
no
source of accurate time.

although port 123 is open inbound for udp and tcp.

I seem to see this error intermittently but for some weeks /
months
it
has
been ongoing.

Should I change my ports / time source?









.



Relevant Pages


Loading