I noticed that too. I guess that keeping the routers in sync is good
enough when they're not in the NTP serving business... I just stopped
using them at home.
But at work I use Road Runner's NTP servers which quite usable ones.
This is a discussion on SBC-ATT Time Servers - NTP ; I guess that I shouldn't keep trying to use them... But, SBC-ATT is my ISP and have the closest NTP Servers to me. However, they are always way out of whack with high offsets, often show as falsetickers. Does SBC ...
I guess that I shouldn't keep trying to use them... But, SBC-ATT is my
ISP and have the closest NTP Servers to me.
However, they are always way out of whack with high offsets, often show
as falsetickers. Does SBC do this intentionally to keep us from using
their services? Anyone at SBC in the NTP Server department that could
take a look?
Any advice? (Other than the obvious to forget about trying to use them?)
Thanks
ntpq -c pe
remote refid st t when poll reach delay offset
jitter
================================================== ============================
+ntp.okstate.edu .USNO. 1 u 85 1024 377 83.632 0.996
0.051
*clock.xmission. .GPS. 1 u 720 1024 377 70.735 0.031
0.277
+time.nist.gov .ACTS. 1 u 669 1024 377 63.289 -4.212
5.218
-ntp.your.org .CDMA. 1 u 205 1024 377 49.258 8.840
0.776
-ntp1.sbcglobal. st1gs-ntp.rcsnt 2 u 94 1024 377 26.339 -39.154
1.193
-ntp2.sbcglobal. st1gs-ntp.rcsnt 2 u 86 1024 377 23.710 -38.231
0.712
-st1gs-ntp.rcsnt .GPS. 1 u 217 1024 377 24.021 -41.391
4.134
I noticed that too. I guess that keeping the routers in sync is good
enough when they're not in the NTP serving business... I just stopped
using them at home.
But at work I use Road Runner's NTP servers which quite usable ones.