Cannot reach time servers

[BoB]

Neutron and AtomicTime are no longer functioning.
Neutron worked when I set my time about two weeks ago
but have been unable to set the clock for over a week now.

Both programs state "Failed to read network time from server"
A ping cannot reach them either.

I renamed HOSTS and shutdown my firewall but still no success.

Any ideas?


BoB

 

[Dan]

Perhaps they are just not working today. Have you tried to contact their
customer service to ask about the sites being down?

"BoB" wrote:

> Neutron and AtomicTime are no longer functioning.
> Neutron worked when I set my time about two weeks ago
> but have been unable to set the clock for over a week now.
>
> Both programs state "Failed to read network time from server"
> A ping cannot reach them either.
>
> I renamed HOSTS and shutdown my firewall but still no success.
>
> Any ideas?
>
>
> BoB
>
>

 

[Casey]

In article <0866CA98-BDB9-491C-AF0D-44A7195B7536@microsoft.com>,
Dan@discussions.microsoft.com says...
> Perhaps they are just not working today. Have you tried to contact their
> customer service to ask about the sites being down?
>
> "BoB" wrote:
>
> > Neutron and AtomicTime are no longer functioning.
> > Neutron worked when I set my time about two weeks ago
> > but have been unable to set the clock for over a week now.
> >
> > Both programs state "Failed to read network time from server"
> > A ping cannot reach them either.
> >
> > I renamed HOSTS and shutdown my firewall but still no success.
> >
> > Any ideas?
> >
> >
> > BoB
> >
> >
>
Just ran AtomicTime. It worked o.k. It adjusted my computer
time 24-sec.
Casey

 

[Dan]

Well, I am glad it is okay now. Problem with Windows Update site with
certificate error with latest updates as of 10:56 pm --- Mountain Time in
U.S.A. -- version 6 as applies to XP Professional.



"Casey" wrote:

> In article <0866CA98-BDB9-491C-AF0D-44A7195B7536@microsoft.com>,
> Dan@discussions.microsoft.com says...
> > Perhaps they are just not working today. Have you tried to contact their
> > customer service to ask about the sites being down?
> >
> > "BoB" wrote:
> >
> > > Neutron and AtomicTime are no longer functioning.
> > > Neutron worked when I set my time about two weeks ago
> > > but have been unable to set the clock for over a week now.
> > >
> > > Both programs state "Failed to read network time from server"
> > > A ping cannot reach them either.
> > >
> > > I renamed HOSTS and shutdown my firewall but still no success.
> > >
> > > Any ideas?
> > >
> > >
> > > BoB
> > >
> > >
> >
> Just ran AtomicTime. It worked o.k. It adjusted my computer
> time 24-sec.
> Casey
>

 

[Dan]

Well, it seems like Microsoft has already fixed the error.

"Dan" wrote:

> Well, I am glad it is okay now. Problem with Windows Update site with
> certificate error with latest updates as of 10:56 pm --- Mountain Time in
> U.S.A. -- version 6 as applies to XP Professional.

 

[BoB]

On Tue, 11 Sep 2007 05:12:36 -0700, BoB <me@privacy.net> wrote:

>Neutron and AtomicTime are no longer functioning.
>Neutron worked when I set my time about two weeks ago
>but have been unable to set the clock for over a week now.
>
>Both programs state "Failed to read network time from server"
>A ping cannot reach them either.
>
>I renamed HOSTS and shutdown my firewall but still no success.
>
>Any ideas?
>
>
>BoB

To close this thread and since this is occurring on both computers
[98SE], I suspect it involves my ISP. Will check with them since no
other ideas have been provided.

Thanks anyway,

BoB

 

[Dan]

Sounds Good! Perhaps you could test it on a friend's computer and/or at your
local library computer and see what the result is there. Please post back
with your results. Thank you and have a nice day.

"BoB" wrote:

> On Tue, 11 Sep 2007 05:12:36 -0700, BoB <me@privacy.net> wrote:
>
> >Neutron and AtomicTime are no longer functioning.
> >Neutron worked when I set my time about two weeks ago
> >but have been unable to set the clock for over a week now.
> >
> >Both programs state "Failed to read network time from server"
> >A ping cannot reach them either.
> >
> >I renamed HOSTS and shutdown my firewall but still no success.
> >
> >Any ideas?
> >
> >
> >BoB
>
> To close this thread and since this is occurring on both computers
> [98SE], I suspect it involves my ISP. Will check with them since no
> other ideas have been provided.
>
> Thanks anyway,
>
> BoB
>
>

 

[Franc Zabkar]

On Tue, 11 Sep 2007 05:12:36 -0700, BoB <me@privacy.net> put finger to
keyboard and composed:

>Neutron and AtomicTime are no longer functioning.
>Neutron worked when I set my time about two weeks ago
>but have been unable to set the clock for over a week now.
>
>Both programs state "Failed to read network time from server"
>A ping cannot reach them either.
>
>I renamed HOSTS and shutdown my firewall but still no success.
>
>Any ideas?
>
>
>BoB

Could this be the cause?

http://schmail.com/atomictime/

"If your time server connections are refused, you may be running
through a proxy server. This is a problem. Your internet connection
may be blocking all connections except for basic http style access. No
time correction for you! (until you get a different internet
provider)"

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[... et al.]

BoB wrote:

> Neutron and AtomicTime are no longer functioning.
> Neutron worked when I set my time about two weeks ago
> but have been unable to set the clock for over a week now.
>
> Both programs state "Failed to read network time from server"
> A ping cannot reach them either.
>
> I renamed HOSTS and shutdown my firewall but still no success.
>
> Any ideas?

And you are trying to sync with what time-server? Maybe the server
is defunct.

Check out this link and maybe try syncing against a server-pool:
<http://support.ntp.org/bin/view/Servers/NTPPoolServers>


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

 

[... et al.]

BoB wrote:

> Still don't understand why I cannot connect to the servers I have
> always used. My ISP was no help other than to eliminate them as
> the possible problem.

<http://tf.nist.gov/timefreq/service/its.htm>
"Starting on 14 April 2007 the server time.nist.gov will no
longer respond to requests for time in the TIME format"

Maybe other servers are also dropping support for the 'time'
protocol. Perhaps it's /time/ to look for a NTP client.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

 

[Dan]

Heck, one can just use their cell phone and/or a wristwatch to properly
configure the time on their computer and not bother to have it automatically
updated. It usually seems to cause issues sometimes anyway because I have
seen it update to the wrong time on my computer and then I have to manually
change it anyway. Now this is just my thoughts on this topic and take it for
what it is worth and have a nice day.

"... et al." wrote:

> BoB wrote:
>
> > Still don't understand why I cannot connect to the servers I have
> > always used. My ISP was no help other than to eliminate them as
> > the possible problem.
>
> <http://tf.nist.gov/timefreq/service/its.htm>
> "Starting on 14 April 2007 the server time.nist.gov will no
> longer respond to requests for time in the TIME format"
>
> Maybe other servers are also dropping support for the 'time'
> protocol. Perhaps it's /time/ to look for a NTP client.
>
>
> --
> Nah-ah. I'm staying out of this. ... Now, here's my opinion.
>
> Please followup in the newsgroup.
> E-mail address is invalid due to spam-control.
>

 

[MEB]

"... et al." <look@sig.bcause.this.is.invalid> wrote in message
news:ipjIi.9204$ZA.4784@newsb.telia.net...
| BoB wrote:
|
| > Still don't understand why I cannot connect to the servers I have
| > always used. My ISP was no help other than to eliminate them as
| > the possible problem.
|
| <http://tf.nist.gov/timefreq/service/its.htm>
| "Starting on 14 April 2007 the server time.nist.gov will no
| longer respond to requests for time in the TIME format"
|
| Maybe other servers are also dropping support for the 'time'
| protocol. Perhaps it's /time/ to look for a NTP client.
|
|
| --
| Nah-ah. I'm staying out of this. ... Now, here's my opinion.
|
| Please followup in the newsgroup.
| E-mail address is invalid due to spam-control.

I'll verify that [beyond NIST's own statement], several of the older
standard time servers no longer serve the *public*.
I have had to reconfigure the various time correcting programs I have
tested recently to other servers. For instance, the one I am testing now,
*Chronos* [which uses or can be configured with dozens of servers], must be
reconfigured from several of the previous default servers.
Not that it makes much difference, as there are dozens of new sites that do
provide the service, and pull their time from the *official servers* around
the world.


--
MEB
http://peoplescounsel.orgfree.com
________

 

[PCR]

.... et al. wrote:
| BoB wrote:
|
|> Still don't understand why I cannot connect to the servers I have
|> always used. My ISP was no help other than to eliminate them as
|> the possible problem.
|
| <http://tf.nist.gov/timefreq/service/its.htm>
| "Starting on 14 April 2007 the server time.nist.gov will no
| longer respond to requests for time in the TIME format"

NisTime still works for me. It has multiple servers...
http://tf.nist.gov/

Here is what Kerio Firewall reports to be required for the time update
to be accomplished...

Details:
'TCP/Daytime Client Program' from your computer wants to connect to
64.236.96.53, port 13

Details about application:
c:\program files\nist time\nistime-32bit.exe

| Maybe other servers are also dropping support for the 'time'
| protocol. Perhaps it's /time/ to look for a NTP client.
|
|
| --
| Nah-ah. I'm staying out of this. ... Now, here's my opinion.
|
| Please followup in the newsgroup.
| E-mail address is invalid due to spam-control.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

 

[... et al.]

PCR wrote:

> ... et al. wrote:
>
> |
> | <http://tf.nist.gov/timefreq/service/its.htm>
> | "Starting on 14 April 2007 the server time.nist.gov will no
> | longer respond to requests for time in the TIME format"
>
> NisTime still works for me. It has multiple servers...
> http://tf.nist.gov/
>
> Here is what Kerio Firewall reports to be required for the time update
> to be accomplished...
>
> Details:
> 'TCP/Daytime Client Program' from your computer wants to connect to
> 64.236.96.53, port 13

Hmm.. So their own software uses the 'Daytime Protocol', even if
they on the page i link to writes:
"Therefore users are strongly encouraged to switch to the Network
Time Protocol (NTP)"

> Details about application:
> c:\program files\nist time\nistime-32bit.exe
>
> | Maybe other servers are also dropping support for the 'time'
> | protocol. Perhaps it's /time/ to look for a NTP client.

But for the most part i do what _Dan_ suggests, i time-sync my
computers against my wristwatch or another clock nearby. Works
for me.


--
Nah-ah. I'm staying out of this. ... Now, here's my opinion.

Please followup in the newsgroup.
E-mail address is invalid due to spam-control.

 

[J. Y.]

I use DS Clock and I have it contact MITS (Massachusetts Institute of
Technology). Been using it for a long time.

Still works great.

Jack



--

 

[PCR]

.... et al. wrote:
| PCR wrote:
|
|> ... et al. wrote:
|>
|> |
|> | <http://tf.nist.gov/timefreq/service/its.htm>
|> | "Starting on 14 April 2007 the server time.nist.gov will no
|> | longer respond to requests for time in the TIME format"
|>
|> NisTime still works for me. It has multiple servers...
|> http://tf.nist.gov/
|>
|> Here is what Kerio Firewall reports to be required for the time
|> update to be accomplished...
|>
|> Details:
|> 'TCP/Daytime Client Program' from your computer wants to connect to
|> 64.236.96.53, port 13
|
| Hmm.. So their own software uses the 'Daytime Protocol', even if
| they on the page i link to writes:
| "Therefore users are strongly encouraged to switch to the Network
| Time Protocol (NTP)"

I don't know what they are trying to say, but it seems nistime-32bit.exe
uses port 13. Looks like they are talking about port 37...

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

|> Details about application:
|> c:\program files\nist time\nistime-32bit.exe
|>
|> | Maybe other servers are also dropping support for the 'time'
|> | protocol. Perhaps it's /time/ to look for a NTP client.
|
| But for the most part i do what _Dan_ suggests, i time-sync my
| computers against my wristwatch or another clock nearby. Works
| for me.

I don't have NisTime constantly running, but will just click it now/then
when online. It seems my clock is almost always a tad fast.

| --
| Nah-ah. I'm staying out of this. ... Now, here's my opinion.
|
| Please followup in the newsgroup.
| E-mail address is invalid due to spam-control.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net