sntpclock: fatal: time uncertainty too large
Shantanu <[email protected]> Tue, 25 Mar 2003 20:56:50 -0800 (PST)
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Message-ID | <[email protected]> |
When i try to run # sntp clock <ip> | clockview sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: warning: unable to read clock: timed out sntpclock: fatal: time uncertainty too large clockview: fatal: data split across packets It is not that my clock is too screwed. # date Wed Mar 26 10:22:48 IST 2003 # hwclock Wed 26 Mar 2003 10:23:48 AM IST 0.992516 seconds Still i get this error. I tried with quite a few NTP servers. Same problem. One thing I must say here is that my ISP blocks by default many ports. Does clockspeed require any port to be kept open? Thank you. Shantanu __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com