[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: setting up NTPd



On Wed, 2003-10-01 at 15:38, Jeff Silberberg wrote:
> So, 
> 
> This is right ??
> 
> [root vc1 root]# ntpq -p
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
>  LOCAL(0)        LOCAL(0)        10 l    3   64    1    0.000    0.000   0.008
>  ns1.usg.edu     0.0.0.0         16 u    -   64    0    0.000    0.000 4000.00
>  ns2.usg.edu     0.0.0.0         16 u    -   64    0    0.000    0.000 4000.00
>  cs.columbia.edu 0.0.0.0         16 u    -   64    0    0.000    0.000 4000.00
> 

ok .  you are not reaching the servers at all 

Is there a firewall between you and the servers?

try ntpq -p ns1.usg.edu

here is what I got on a machine with direct access to the net. I am
going to preformat the output

[bhughes bretsony bhughes]$ ntpq -p ns1.usg.edu
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+reaper.twc.weat .CDMA.           1 u 1071 1024  377   34.480    0.705   0.580
+ntp0.mcs.anl.go 0.0.0.0          1 u  496 1024  377   17.060    0.367   0.440
 152.1.58.124    0.0.0.0         16 -    - 1024    0    0.000    0.000 16000.0
*navobs1.gatech. .PSC.            1 u 1093 1024  377    2.760   -0.597   0.640
-209.195.3.50    reaper.twc.weat  2 u  600 1024  377   37.020   -1.918   0.930
[bhughes bretsony bhughes]$ 

this tells us that ns1.usg.edu is currently synced to navobs1.gatech.[edu?]

hmm lets see the ips

[bhughes bretsony bhughes]$ ntpq -pn ns1.usg.edu 
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
+216.133.140.77  .CDMA.           1 u  468 1024  377   33.870   -0.020   0.550
+140.221.8.88    0.0.0.0          1 u  917 1024  377   17.060    0.367   0.440
 152.1.58.124    0.0.0.0         16 -    - 1024    0    0.000    0.000 16000.0
*130.207.244.240 .PSC.            1 u  489 1024  377    1.560    0.346   0.660
-209.195.3.50    216.133.140.77   2 u 1020 1024  377   37.020   -1.918   0.930
[bhughes bretsony bhughes]$ 


[bhughes bretsony bhughes]$ dig -x 130.207.244.240

; <<>> DiG 9.2.1 <<>> -x 130.207.244.240
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24751
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3

;; QUESTION SECTION:
;240.244.207.130.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
240.244.207.130.in-addr.arpa. 85802 IN	PTR	navobs1.gatech.edu.

yup that was a good guess.  Anyway the ntpq documentation page explains
all this better than I can but suffice it to say that this machine is
pretty damn close to the top of the food chain.  

Trouble is you can't talk to it.  find out why,  Usually firewall issues
port 123 udp and tcp is what I usually open up.  I don'tremember if it
uses both or not but lets get it working before we get to semantics.

there is also a debugging techniques page on my 7.3 machine in 
 /usr/share/doc/ntp-4.1.1/

HTH

Bret







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]