[ntp:questions] ntpdate works, but ntpd doesn't (reach = 0)

Steve Kostecke kostecke at ntp.org
Mon Jan 26 19:03:15 UTC 2009


On 2009-01-26, Lizvette Malave <Lizvette_Malave at raytheon.com> wrote:

> ntpdate timeServer (without the -u option) works too.

I'm not sure what you are replying to because (1) you top posted and (2)
the quoted material in your message was garbled.

If ntpdate <timeserver> works then ntpd should work, too. That is
because ntpdate without '-u' _or_ any other commandline options uses
123/UDP as the source port just like ntpd. If you ran ntpdate with any
command-line options (other than the time server hostname) it very
likely used a high (i.e. unprivileged, or >1024) source port.

> Is there a way to make the ntpd use a different port?

No. At least not without recompiling NTP.

The correct solution is to have port 123/UDP opened on your firewall.

-- 
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/




More information about the questions mailing list