From: "Charles R. Tersteeg" <[EMAIL PROTECTED]>
> I have both the firewalls on the machines diabled for this test. ntpd
> is running on both machines:
Live dangerously you do. Punching selective holes for ntpd not disabling
firewalls, I suggest.
> # ntpdate -d -u 192.168.0.1
> 31 Jul 13:59:20 ntpdate[1941]: ntpdate 4.0.99k Thu Apr 5 14:21:52 EDT
> 2001 (1)
> transmit(192.168.0.1)
> transmit(192.168.0.1)
> transmit(192.168.0.1)
> transmit(192.168.0.1)
> transmit(192.168.0.1)
> server 192.168.0.1, port 123
> stratum 0, precision 0, leap 00, trust 000
> refid [0.0.0.0], delay 0.00000, dispersion 64.00000
> transmitted 4, in filter 4
> reference time: 00000000.00000000 Thu, Feb 7 2036 0:28:16.000
> originate timestamp: 00000000.00000000 Thu, Feb 7 2036 0:28:16.000
> transmit timestamp: bf117e8b.f6385404 Tue, Jul 31 2001 13:59:23.961
> filter delay: 0.00000 0.00000 0.00000 0.00000
> 0.00000 0.00000 0.00000 0.00000
> filter offset: 0.000000 0.000000 0.000000 0.000000
> 0.000000 0.000000 0.000000 0.000000
> delay 0.00000, dispersion 64.00000
> offset 0.000000
>
> 31 Jul 13:59:24 ntpdate[1941]: no server suitable for synchronization
> found
>
> me clueless here,
Give your reference server time to settle and declare itself valid. Monitor
it first, the one that talked to the three external addresses which MAY or
may not be ntp servers. (Test THAT with ntpdate. One step at a time.)
{^_^}
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
