On 2008-02-12, Nick Bright <[EMAIL PROTECTED]> wrote:
> The resolution ended up being to comment out:
>
> restrict default ignore
>
> from the default ntpd.conf
Unfortunately the one bit of information you did _not_ post was your
ntp.conf. So no one here would have seen that.
> After I commented
Nick,
Even better would be for folks to visit:
http://support.ntp.org/bin/view/Support/AccessRestrictions
--
Harlan Stenn <[EMAIL PROTECTED]>
http://ntpforum.isc.org - be a member!
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp
The resolution ended up being to comment out:
restrict default ignore
from the default ntpd.conf
After I commented out that line, I was able to get updates from the
servers I had configured, as well as provide updates to client devices.
For those coming upon this in a search engine result, ple
"Richard B. Gilbert" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Nick Bright wrote:
>> ntpq> pe
>> remote refid st t when poll reach delay offset
>> =
>> 217.160.254.116 0.0.0.0 16 u- 128
Danny Mayer wrote:
> Nick Bright wrote:
>> If the NTPD isn't synchronized with external servers, will it simply
>> ignore clients?
>>
>
> Yes, unless you tell it to act as if it was by using the "local" refclock.
>
Actually, it won't ignore the clients, but the clients will ignore it.
It sends
Nick Bright wrote:
> I've installed and configured NTP on a RHEL 3 machine, and configured it
> to query the US pool servers.
>
> Unfortunately, because the firewall administrator this machine is behind
> hasn't yet set up the firewall rules the time can't sync. At least I
> assume that he hasn
Nick Bright wrote:
> I've installed and configured NTP on a RHEL 3 machine, and configured it
> to query the US pool servers.
>
> Unfortunately, because the firewall administrator this machine is behind
> hasn't yet set up the firewall rules the time can't sync. At least I
> assume that he hasn
I've installed and configured NTP on a RHEL 3 machine, and configured it
to query the US pool servers.
Unfortunately, because the firewall administrator this machine is behind
hasn't yet set up the firewall rules the time can't sync. At least I
assume that he hasn't done it, because the time is
