NTP time issue with md5 authentication.


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users NTP time issue with md5 authentication.
# 1  
Old 04-28-2016
NTP time issue with md5 authentication.

Hi All

Appreciate your help.

Here is the scenario:

1. Five months back we configured md5 authentication with network devices and NTP server and it worked fine.
2.Last week all of a sudden the network devices are out of sync.
3.We changed the md5 key and it started working.


Questions:
1.Why it failed to work after a long time?
2.With new key it's working but the main problem is we need to configure all the network devices ( around 200 devices) again.
3.Although the network devices are out of sync the NTP device was showing they are sync. Please find below output for the two network devices.

Please let me know if you need more information.
Code:
NTP SERVER:~)-> ntpdc -c monlist | grep  X.X.X.X
X.X.X.X               123 X.X.X.X       1721 3 4     d4     31      27

NTP SERVER:~)-> ntpdc -c monlist | grep  X.X.X.X
X.X.X.X              123 X.X.X.X        834 3 2     d4     65      49

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

NTP time problem

I got an ntp time problem on AIX server. os version is AIX7.1 OS LEVEL 7.1.0.0 i got below output,when i run the below command bash-3.2# ntpdate -dv XXXXXXXXXXXXXXXXXXXXXXXX 4 Dec 12:50:49 ntpdate: 3.4y transmit(xxxxxxxxx) receive(xxxxxxxxx) transmit(xxxxxxxx) receive(xxxxxxxxx)... (9 Replies)
Discussion started by: murali969
9 Replies

2. Red Hat

NTP Authentication Issues: Help Please!

Hello everyone, I've been trying to set up NTP authentication between a server and a workstation. Both point to the same NTP server which is on a different physical box with its own IP address. I followed the steps below but I get the following result. How can I get this working? Expected... (0 Replies)
Discussion started by: rchaud10
0 Replies

3. Red Hat

CUPS + passwd.md5 issue

I posted the below question on the CUPS forums yesterday and have still not been able to find a good answer of why or if I can keep this from happening. I have been looking for a while now and have still not found what I am looking for. Is there a way to allow multiple users to be updating the... (13 Replies)
Discussion started by: linuxn00b
13 Replies

4. Shell Programming and Scripting

Create md5 sums and archive the resulting md5 files

Hello everyone, I am looking to basically creating md5sum files for all iso files in a directory and archive the resulting md5 files into a single archive in that very same directory. I worked out a clumsy solution such as: #find files for which md5sum are to be created and store the... (1 Reply)
Discussion started by: SurfTranquille
1 Replies

5. Linux

How often does Linux NTP server update its time with the external NTP server?

All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies

6. Solaris

Solaris 10 openldap authentication with md5 passwords

Hello to everyone, We are trying to enable ldap authentication with pam_ldap and md5 passwords on a Solaris 10 system to an openldap server. If passwords are stored using crypt, everything works correctly. But if the password in openldap is in md5, then authentication fails. We have installed... (0 Replies)
Discussion started by: jfotop
0 Replies

7. AIX

NTP - with time difference

We have configured most of 1200 servers with an NTP server. For the rest of the servers, I have a strange requirement. I want to synchronize them with NTP time with a lag of 15 minutes. Is it possible ? If yes How ? (0 Replies)
Discussion started by: shauche
0 Replies

8. HP-UX

NTP time

Is anyone familiar with adding NTP timing to a HPUX 10 OS? Thanks Brian (2 Replies)
Discussion started by: breigner
2 Replies

9. UNIX for Advanced & Expert Users

ntp across time zones

I've been tasked to implement ntp on my SCO Unix servers. I have over 600 servers spread across the US in different time zones. Each remote server has network connectivity to a main server here, through their local ISP. (That's how we currently deliver mail to them). My question is, how can... (5 Replies)
Discussion started by: Howeird
5 Replies

10. 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
Login or Register to Ask a Question
TIMESYNCD.CONF(5)						  timesyncd.conf						 TIMESYNCD.CONF(5)

NAME
timesyncd.conf, timesyncd.conf.d - Network Time Synchronization configuration files SYNOPSIS
/etc/systemd/timesyncd.conf /etc/systemd/timesyncd.conf.d/*.conf /run/systemd/timesyncd.conf.d/*.conf /usr/lib/systemd/timesyncd.conf.d/*.conf DESCRIPTION
These configuration files control NTP network time synchronization. CONFIGURATION DIRECTORIES AND PRECEDENCE
The default configuration is defined during compilation, so a configuration file is only needed when it is necessary to deviate from those defaults. By default, the configuration file in /etc/systemd/ contains commented out entries showing the defaults as a guide to the administrator. This file can be edited to create local overrides. When packages need to customize the configuration, they can install configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. The main configuration file is read before any of the configuration directories, and has the lowest precedence; entries in a file in any configuration directory override entries in the single configuration file. Files in the *.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order, regardless of which of the subdirectories they reside in. When multiple files specify the same option, for options which accept just a single value, the entry in the file with the lexicographically latest name takes precedence. For options which accept a list of values, entries are collected as they occur in files sorted lexicographically. It is recommended to prefix all filenames in those subdirectories with a two-digit number and a dash, to simplify the ordering of the files. To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in the configuration directory in /etc/, with the same filename as the vendor configuration file. OPTIONS
The following settings are configured in the "[Time]" section: NTP= A space-separated list of NTP server host names or IP addresses. During runtime this list is combined with any per-interface NTP servers acquired from systemd-networkd.service(8). systemd-timesyncd will contact all configured system or per-interface servers in turn until one is found that responds. When the empty string is assigned, the list of NTP servers is reset, and all assignments prior to this one will have no effect. This setting defaults to an empty list. FallbackNTP= A space-separated list of NTP server host names or IP addresses to be used as the fallback NTP servers. Any per-interface NTP servers obtained from systemd-networkd.service(8) take precedence over this setting, as do any servers set via NTP= above. This setting is hence only used if no other NTP server information is known. When the empty string is assigned, the list of NTP servers is reset, and all assignments prior to this one will have no effect. If this option is not given, a compiled-in list of NTP servers is used instead. RootDistanceMaxSec= Maximum acceptable root distance. Takes a time value (in seconds). Defaults to 5 seconds. PollIntervalMinSec=, PollIntervalMaxSec= The minimum and maximum poll intervals for NTP messages. Each setting takes a time value (in seconds). PollIntervalMinSec= must not be smaller than 16 seconds. PollIntervalMaxSec= must be larger than PollIntervalMinSec=. PollIntervalMinSec= defaults to 32 seconds, and PollIntervalMaxSec= defaults to 2048 seconds. SEE ALSO
systemd(1), systemd-timesyncd.service(8), systemd-networkd.service(8) systemd 237 TIMESYNCD.CONF(5)