That did the trick, thank you very much, Greg!
/iain
Greg Wooledge <[EMAIL PROTECTED]> wrote:
>Iain Lamb ([EMAIL PROTECTED]) wrote:
>
>> stratum 16, precision -17, leap 11, trust 000
>>
>> It's like ntpdate doesn't consider .1 'suitable' or trustworthy to
>> sync up with. Maybe I need to find
Iain Lamb ([EMAIL PROTECTED]) wrote:
> I have two machines: 192.168.1.1, 192.168.1.2
>
> I want to synchronize .2's time with .1's. I've setup ntp on both. On
> .2 I've specified 192.168.1.1 as the server.
What did you specify on .1? It would help to see the ntp.conf files.
> 1 Nov 16:54:57
Thank you very much, Thomas, that fixed it!
/iain
Thomas Keusch wrote:
>If there currently is no time source available for xntpd to sync with,
>the daemon will refuse to propagate its own "unreliable" time, until
>it is in sync again.
>
>On .1, add the following to the config:
>
>It tells the da
i run xntp3 on tick.firetrail.com and it gives connection refused when i
attempt connection on port 123. but 'ntpdate tick.firetrail.com' does
work.
[EMAIL PROTECTED] ~] telnet galactica 123
Trying 208.222.179.31...
telnet: Unable to connect to remote host: Connection refused
[EMAIL PROTECTED] ~]
aphro <[EMAIL PROTECTED]> wrote:
>just make sure xntp3 is running, you can test it by telnetting to
>port 37 on the ntp server
Yes, a telnet to .1 37 does indeed return a little healty garbage -
although I thought perhaps ntp connects to port 123 using udp (this
idea based on a 'grep ntp /etc/ser
On Mon, Nov 01, 1999 at 05:59:18PM -0800, Iain Lamb wrote:
> Note that netdate tcp 192.168.1.1 works fine on .2.
That means your xntpd is not loaded, otherwise it should return:
2 Nov 03:21:51 ntpdate[5563]: the NTP socket is in use, exiting
Check you've got a symlink in /etc/rc2.d, alike:
S20x
just make sure xntp3 is running, you can test it by telnetting to port 37
on the ntp server, it'll spit out some garbage and drop you thats
normal. then setup a cron entry i suppose to synch the time every 12 hours
or something.. my ntp server is rarely more then 0.001 seconds off from
the servers
uncle!
I have two machines: 192.168.1.1, 192.168.1.2
I want to synchronize .2's time with .1's. I've setup ntp on both. On
.2 I've specified 192.168.1.1 as the server.
But things don't seem to work - after waiting a few hours, .2's time
is still very out of sync with .1's. If I kill ntpd on .
8 matches
Mail list logo