Sponsored Content
Full Discussion: NTP Clients not sync
Operating Systems Linux Fedora NTP Clients not sync Post 302565267 by otheus on Monday 17th of October 2011 11:50:12 AM
Old 10-17-2011
1. Redhat's default ntpd.conf configuration is pure shit. Don't use it. Don't even think about basing your config on it. Notably, remove the "server 127.127...." and fudge lines.

2. You're Windows NT time server is essentially a "tier 2" server. That server (and its mirror/failover) really sohuld be the only "server" lines you need here.

3. You're "restrict" lines may be in fact restricting your server from being modified by the time servers you want to in fact synchronize to. That's how you've set your default, and then you are permissive only with the localhost. So that wouldn't work.

4. If your server is not behnid a firewall which blocks incoming NTP from unknown servers, having the authentication enabled would be a smart idea. Having said that, it might be easier to config the firewall than to figure out ntp's very confusing authentication scheme.
This User Gave Thanks to otheus For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TIME SYNC (NTP)

Is there a utility which offers the ability to utilize NTP to sync time on machine. If so please point to man page or web site (3 Replies)
Discussion started by: SmartJuniorUnix
3 Replies

2. AIX

NTP server with aix & wintel clients

Good morning to all, can someone advise me how to setup aix ntp server with aix & wintel clients? Secondly, I also require to enable the service to autostart on reboot, how do I configure this? Thirdly, how do I configure daily autosync between clients and server? Please advice, thanks.... (0 Replies)
Discussion started by: chongkls77
0 Replies

3. SuSE

unable to sync the time with ntp server

Hi folks, The server time is no tgetiing synched up with the NTP server. I tried ntpdate -u <ipadress> this is not working. please help out. regards, Sag. (7 Replies)
Discussion started by: sag71155
7 Replies

4. UNIX for Advanced & Expert Users

Tracking NTP Clients

I need to find out the NTP Clients which are syncing with my NTP Server in a Unix(Linux/Solaris) Machine. For eg. How many Stratum 2 Servers sync the time with my Stratum1 Server. Is there any way to track it? edit by bakunin: moving the thread to where it belongs: the technical forums. (4 Replies)
Discussion started by: hottyspidy
4 Replies

5. Solaris

NTP time sync in Solaris 10

Ok, I have 4 production systems. There is one NTP server for all four systems. In each system there is one Solaris 10 box that points to that NTP server. All of the other machines in the system point to the Solaris 10 machine to get their time sync. All four Solaris 10 machines have essentially... (2 Replies)
Discussion started by: DeCoTwc
2 Replies

6. Linux

ntp client/daemon sync

All, I need to write a script which can determine if my NTP client is X second off from the NTPD server time. I am looking for a crafty oneliner to calculate the time difference? (3 Replies)
Discussion started by: vada010
3 Replies

7. Red Hat

NTP sync problem

Hi, I have 4 machines and all are NTP configured with same ntp.conf file. But 3 machines are in sync with Time server and 4th machine is not contacting & sync with the NTP server. Please see the below details. # service ntpd stop Stopping ntpd: ... (0 Replies)
Discussion started by: uday123
0 Replies

8. HP-UX

Setting up NTP HP-UX clients from solaris NTP server

Hi I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server? FR (3 Replies)
Discussion started by: fretagi
3 Replies

9. Solaris

Client does not sync date with ntp servers

We had a network problem a couple of days before that caused 1 interface to down and up. But today I have noticed that our date is wrong, our system have 4 servers and the other 3 are OK. I used <date> command, the result is: Fri Jan 2 17:57:55 ICT 1970 I have tried set date to be the same as... (3 Replies)
Discussion started by: salvation3103
3 Replies

10. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies
ntp.keys(5)							   File Formats 						       ntp.keys(5)

NAME
ntp.keys - NTP symmetric key file format configuration file SYNOPSIS
[--option-name] [--option-name value] All arguments must be options. DESCRIPTION
This document describes the format of an NTP symmetric key file. For a description of the use of this type of file, see the "Authentica- tion Support" section of the ntp.conf(5) page. ntpd(8) reads its keys from a file specified using the -k command line option or the keys statement in the configuration file. While key number 0 is fixed by the NTP standard (as 56 zero bits) and may not be changed, one or more keys numbered between 1 and 65535 may be arbi- trarily set in the keys file. The key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form keyno type key opt_IP_list where keyno is a positive integer (between 1 and 65535), type is the message digest algorithm, key is the key itself, and opt_IP_list is an optional comma-separated list of IPs where the keyno should be trusted. that are allowed to serve time. Each IP in opt_IP_list may con- tain an optional /subnetbits specification which identifies the number of bits for the desired subnet of trust. If opt_IP_list is empty, any properly-authenticated message will be accepted. The key may be given in a format controlled by the type field. The type MD5 is always supported. If ntpd was built with the OpenSSL library then any digest library supported by that library may be specified. However, if compliance with FIPS 140-2 is required the type must be either SHA or SHA1. What follows are some key types, and corresponding formats: MD5 The key is 1 to 16 printable characters terminated by an EOL, whitespace, or a # (which is the "start of comment" character). SHA SHA1 RMD160 The key is a hex-encoded ASCII string of 40 characters, which is truncated as necessary. Note that the keys used by the ntpq(8) and ntpdc(8) programs are checked against passwords requested by the programs and entered by hand, so it is generally appropriate to specify these keys in ASCII format. FILES
/etc/ntp.keys the default name of the configuration file SEE ALSO
ntp.conf(5), ntpd(1), ntpdate(1), ntpdc(1), sntp(1) AUTHORS
The University of Delaware and Network Time Foundation COPYRIGHT
Copyright (C) 1992-2017 The University of Delaware and Network Time Foundation all rights reserved. This program is released under the terms of the NTP license, <http://ntp.org/license>. BUGS
Please send bug reports to: http://bugs.ntp.org, bugs@ntp.org NOTES
This document was derived from FreeBSD. This manual page was AutoGen-erated from the ntp.keys option definitions. 4.2.8p13 20 Feb 2019 ntp.keys(5)
All times are GMT -4. The time now is 01:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy