Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a NTP server running in my local network with access to the internet. the local network is divided into two subnet, the main subnet where the NTP server is running, and a second subnet. Computers on both subnets sync with the same NTP server. Computers on the second subnet are able to sync without any problem, however, computers in the first subnet aren't/
Results from a computer on the second subnet:
Unless there is a danger of NTP requests causing an excessive load on -- or interfering with -- your NTP server you could simply remove the restrict lines from the ntp.conf file.
I tried a variety of simple restricts and could not get any of them to work so commented them out. This ntp.conf works for me. KISS!
# Configuration file for ntpd.
# Time sources
fudge 127.127.1.0 stratum 10
# Drift file
# Access control
# First deny access to all
#restrict default ignore
# Then open up to LAN without allowing them to change time or be used as time sources
#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
Last edited by catkin; 12-15-2009 at 02:18 AM.
Reason: Added "-- or interfering with --"
The subnet listed is actually the one where the server is on, and it is clients within this subnet that is rejecting the ntp.
I've tried adding the other subnet as well, and also removing all the restrict lines, but again, the clients on the same subnet as the server is rejecting, whereas the other subnet syncs without a problem.
From the NTP documentation, the flash code of 400 indicates that "The autokey protocol has not verified the server or peer is proventic and has valid public key credentials. See the Authentication Options page."
However, I'm not sure what to do about it... are there a way to turn off authentication off?
OK - I think I've found the problem - the server is running ntpd firstname.lastname@example.org Sat Nov 10 12:33:50 UTC 2007 (1) (CentOS5)
All the clients in the other subnet are running ntpd: ntpd email@example.com Sun Aug 13 01:49:12 CDT 2006 (1) (CentOS4)
I've found we have a client on the first subnet which I thought aren't syncing is actually able to sync, it is also a CentOS4 machine, whereas all the other machines are also CentOS5, and one Ubuntu 9.10, which is running Ver. 4.2.4p6
So it seems like ntp v4.2.0 are able to sync with 4.2.2, however 4.2.2 or 4.2.4 can't. Now to find out what's changed between these versions...