sntpclock: warning: unable to read clock: timed out

Does this mean it can't read the system clock?  Or the remote NTP clock?
I don't have a firewall (just FreeBSD connected straight to a DSL line).

I know this has probably been covered on this list a million times.  Is
there an archive I can search?  I went to google.com and I found
references to this problem but no solution.

bin 19:28:50 > ./sntpclock `dnsip time.nist.gov` | ./clockview
sntpclock: warning: unable to read clock: timed out
before: 2004-12-13 19:29:03.629084000000000000
after:  2004-12-13 19:28:57.053052999865002930


Approximately 95% of the time that I use sntpclock I see the line
"sntpclock: warning: unable to read clock".  It doesn't seem to prevent
sntp from working.  When I use it, in conjunction with clockview, I get
the same offset (after accounting for the leap seconds) as I do with
sntp (an NTP client).  If I use sntpclock with clockadd then it resets
the clock to the same value reported by sntp (again after accounting for
leap seconds).

Also, I don't know if this matters, but when I use sntpclock in
conjunction with clockspeed, I do NOT get meaningful results.  My clock
ends up running very slow (lost 15 seconds per hour). I have recompiled
my time zone database so as to include leap seconds so I don't think
that is it.  

Any help would be appreciated.




derik      
 
                     email:  [email protected]

                     WWW:    http://www.pobox.com/~derik