Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Sep 2004 14:15:37 -0500
From:      Dan Nelson <dnelson@allantgroup.com>
To:        Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: how to update system time?
Message-ID:  <20040910191537.GJ5008@dan.emsphone.com>
In-Reply-To: <448ybiq6r7.fsf@be-well.ilk.org>
References:  <200409101942.51769.haimat@lame.at> <2301747004091010514a3271d@mail.gmail.com> <200409102000.52343.haimat@lame.at> <448ybiq6r7.fsf@be-well.ilk.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Sep 10), Lowell Gilbert said:
> "Matthias F. Brandstetter" <haimat@lame.at> writes:
> > The computer _is_ able to reach the ntp server.
> > See this example:
> > 
> > [ 17:34 mx2@ebox ~ ] date
> > Fri Sep 10 17:35:00 CEST 2004
> > [ 17:35 mx2@ebox ~ ] rdate time.fu-berlin.de
> > Fri Sep 10 19:57:55 2004
> > [ 17:35 mx2@ebox ~ ] rdate -s time.fu-berlin.de
> > [ 17:35 mx2@ebox ~ ] date
> > Fri Sep 10 17:35:27 CEST 2004
> > [ 17:35 mx2@ebox ~ ] ntpdate time.fu-berlin.de
> > 10 Sep 17:35:42 ntpdate[8708]: no server suitable for synchronization found
> > [ 17:35 mx2@ebox ~ ]
> 
> time.fu-berlin.de is not an ntp server, so that's a different problem
> than rdate.

Actually it is:

$ ntptrace time.fu-berlin.de
130.133.1.10: stratum 1, offset 0.011233, synch distance 0.00153, refid 'GPS'

Matthias, try running "ntpdate -d time.fu-berlin.de", which won't try
to set the local clock but will print out some debugging info that
might tell you why it coudln't fetch anything from the server.  Maybe
you have a firewall blocking incoming port 123 UDP traffic?

-- 
	Dan Nelson
	dnelson@allantgroup.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040910191537.GJ5008>