[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: configuring ntpd to respond to rdate



On Wed, 2007-01-24 at 13:49 -0500, Greg Folkert wrote:
> On Wed, 2007-01-24 at 10:15 -0800, Easthope wrote:
> > ntp is installed on a server here and appears to work.
> > Yet another machine runs rdate at startup and produces
> > this report.
> > 
> > rdate: connect: Connection refused
> > 
> > I have the ntpd man page and it isn't helping.
> > Someone please give a hint of what is needed 
> > in /etc/ntp.conf.  
> 
> You are confusing rdate and ntp.
> 
> rdate is port 37 (tcp and udp), typically disabled as a DoS on the
> machine running the reference can be had easily.
> 
> ntp runs on port 123
> 
> rdate (traditionally) does not even speak the protocol of ntp.
> 
> Why would you have rdate vs ntp installed on the one machine? Is it a
> commercial UNIX? If not, install ntpdate and ntp.
> 
> BTW, rdate is referenced here: http://www.faqs.org/rfcs/rfc868.html
> 
> Where as ntp v3 is here: http://www.faqs.org/rfcs/rfc1305.html
> 
> and snto is here: http://www.faqs.org/rfcs/rfc2030.html
> 
> They are related but not interchangeable *UNLESS* you have a time-client
> the does both or more.
> 
> Use ntp anyway.

You also need to configure your machine that you are referencing to
reply to requests.

http://www.eecis.udel.edu/~mills/ntp/html/index.html

Usually, you need to allow local only clients/networks.

Cheers.
-- 
greg, greg@gregfolkert.net

The technology that is
Stronger, better, faster:  Linux

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: