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.
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)
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)
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)
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)
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)
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)
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)
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)
ntptrace(8) System Manager's Manual ntptrace(8)NAME
ntptrace - Traces a chain of NTP hosts back to their master time source
SYNOPSIS
/usr/sbin/ntptrace [-dnv] [-r retries] [-t timeout] [server]
OPTIONS
Turns on some debugging output. Turns off the printing of host names; instead, host IP addresses are given. This may be necessary if a
nameserver is down. Sets the number of retransmission attempts for each host; default = 5. Sets the retransmission timeout (in seconds);
default = 2. Prints verbose information about the NTP servers.
DESCRIPTION
The ntptrace command determines where a given Network Time Protocol (NTP) server gets its time from, and follows the chain of NTP servers
back to their master time source. If given no arguments, it starts with localhost.
The following is an example of the output from ntptrace: % ntptrace localhost: stratum 4, offset 0.0019529, synch distance 0.144135
server2.bozo.com: stratum 2, offset 0.0124263, synch distance 0.115784 usndh.edu: stratum 1, offset 0.0019298, synch distance 0.011993,
refid 'WWVB'
On each line, the fields are (left to right): the host name, the host's stratum, the time offset between that host and the local host (as
measured by ntptrace; this is why it is not always zero for localhost), the host's synchronization distance, and (only for stratum-1
servers) the reference clock ID. All times are given in seconds. (Synchronization distance is a measure of the goodness of the clock's
time.)
SEE ALSO
Commands: xntpd(8), xntpdc(8)ntptrace(8)