On 29/07/06 15:00, Elijah Savage wrote:
I must be missing something, I am moving my ntp server from freebsd to SuSE 10.0 becuase the freebsd box will be retired. I have everything setup and ntp running but for some reason the other unix box's can't bind to the ntp server and sync off of it. I have done this a million times with freebsd but I can't figure out what is different with SuSE.
rcntp status Checking for network time protocol daemon (NTPD): running
when I run ntpdate from an of the unix boxes I get this back
ntpdate ntpserver 29 Jul 16:57:13 ntpdate[24948]: no server suitable for synchronization found
/etc/ntp.conf server 0.north-america.pool.ntp.org server 1.north-america.pool.ntp.org
## Generic DCF77 clock on serial port (Conrad DCF77) ## Address: 127.127.8.u ## Serial Port: /dev/refclock-u ## ## (create soft link /dev/refclock-0 to the particular ttyS?) ## # server 127.127.8.0 mode 5 prefer
## ## Undisciplined Local Clock. This is a fake driver intended for backup ## and when no outside source of synchronized time is available. ## server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
## Miscellaneous stuff ## restrict 192.168.11.0 mask 255.255.255.0 notrust nomodify notrap
^^^ Does it work without the authentication requirement? If not, then ensure the ntp port is open on the internal interface. If it does work, then have another look at your client config files (ie. do they include the autokey option in the server definition, etc?)
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com