Doing a cluster experiment with cloned VMs and then using ntpdate it throws an error. The machines can ping each other, selinux and iptables are turned off.

[root@Server_2 ~]# service ntpd stop
Shutting down ntpd: [ OK ]
[root@Server_2 ~]# ntpdate Server_1
17 Apr 21:30:18 ntpdate[3113]: no server suitable for synchronization found

[root@Server_2 ~]# ntpdate -d Server_1
17 Apr 21:30:53 ntpdate[3115]: ntpdate [email protected] Mon Feb 6 07:22:46 UTC 2017 (1)
Looking for host Server_1 and service ntp
host found : Server_1
transmit(192.168.30.130)
receive(192.168.30.130)
transmit(192.168.30.130)
receive(192.168.30.130)
transmit(192.168.30.130)
receive(192.168.30.130)
transmit(192.168.30.130)
receive(192.168.30.130)
192.168.30.130: Server dropped: Leap not in sync
server 192.168.30.130, port 123
stratum 2, precision -24, leap 11, trust 000
refid [192.168.30.130], delay 0.02629, dispersion 0.00018
transmitted 4, in filter 4
reference time: de807515.a49f3f25 Tue, Apr 17 2018 21:28:53.643
originate timestamp: de80758d.672d9b0d Tue, Apr 17 2018 21:30:53.403
transmit timestamp: de80758d.5d4ac5ea Tue, Apr 17 2018 21:30:53.364
filter delay: 0.02629 0.02710 0.02734 0.02632
0.00000 0.00000 0.00000 0.00000
filter offset: 0.038197 0.037718 0.037627 0.038198
0.000000 0.000000 0.000000 0.000000
delay 0.02629, dispersion 0.00018
offset 0.038197

17 Apr 21:30:53 ntpdate[3115]: no server suitable for synchronization found

After tossing and turning for almost 20 minutes, the sad blowing ended with a reboot of the machine, then nothing was done and it was fine again.

[root@Server_2 ~]# ntpdate Server_1
17 Apr 21:36:24 ntpdate[3143]: adjust time server 192.168.30.130 offset -0.005873 sec