On Mon, 13 Dec 1999, Mirek Kwasniak wrote:
> > > Try ntpq, is it working?
> >
> > ntpq does work. Does ntpdate use (a) port(s) that ntpq doesn't, so maybe
> > my ISP might have started blocking something ?
>
> No, both ntpdate & ntpq use ntp udp port.
> Again:
> - to long (99) servers list
> - temporary network problem
> - too log distance (time) to servers
>
> Try: ntpdate -d
----------------------------------------------------------------------
darxus:~# ntpdate 128.118.25.3
13 Dec 14:45:39 ntpdate[5606]: no server suitable for synchronization
found
darxus:~# ntpdate -d 128.118.25.3
13 Dec 14:45:43 ntpdate[5607]: ntpdate 4.0.98f Sun Nov 21 00:35:29 MST
1999 (1)
transmit(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
receive(128.118.25.3)
transmit(128.118.25.3)
server 128.118.25.3, port 123
stratum 2, precision -15, leap 00, trust 000
refid [128.4.1.1], delay 0.22501, dispersion 8.00395
transmitted 4, in filter 4
reference time: bbffc8ce.b9fe21d9 Mon, Dec 13 1999 14:34:38.726
originate timestamp: bbffca00.7f0ee49f Mon, Dec 13 1999 14:39:44.496
transmit timestamp: bbffcb68.a3e5321e Mon, Dec 13 1999 14:45:44.640
filter delay: 0.00000 0.22539 0.22501 0.31543
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 -360.303 -360.302 -360.289
0.000000 0.000000 0.000000 0.000000
delay 0.22501, dispersion 8.00395
offset -360.302934
13 Dec 14:45:44 ntpdate[5607]: step time server 128.118.25.3 offset
-360.302934 sec
----------------------------------------------------------------------
Interesting, eh ? Debug mode works, non debug mode doesn't. The ip
address 128.118.25.3 was gotten from doing ntpdate -d `head clock.lst`,
which succeded -- that was the ip it successfully contacted.
__________________________________________________________________
PGP fingerprint = 03 5B 9B A0 16 33 91 2F A5 77 BC EE 43 71 98 D4
[EMAIL PROTECTED] / http://www.op.net/~darxus
Find the next largest prime, be famous:
http://www.mersenne.org/prime.htm
