Hi, I am using ntp.4.2.8, compiled the source code from ntp.org and using the same. But when I try to run ntpd.exe the client is not syncing with server, if I change time in client and run ntpd.exe -q I see some KoD packets received at client side. Below is the message I am seeing:
C:\Windows\SysWOW64>ntpd.exe -q 22 Nov 14:18:47 ntpd[40932]: ntp-keygen 4.2.8p8@1.3265-o Oct 28 12:19:56.86 (UTC+05:0-30) 2016 (1): Starting 22 Nov 14:18:47 ntpd[40932]: Command line: ntpd.exe -q 22 Nov 14:18:47 ntpd[40932]: Raised to realtime priority class 22 Nov 14:18:47 ntpd[40932]: Clock interrupt period 15.625 msec 22 Nov 14:18:47 ntpd[40932]: Performance counter frequency 2.604 MHz 22 Nov 14:18:47 ntpd[40932]: Windows clock precision 0.977 msec, min. slew 6.400 ppm/s 22 Nov 14:18:47 ntpd[40932]: using Windows clock directly 22 Nov 14:18:47 ntpd[40932]: proto: precision = 976.500 usec (-10) 22 Nov 14:18:47 ntpd[40932]: proto: fuzz beneath 0.174 usec 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 11 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 12 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 13 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 14 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 15 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 16 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 17 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 18 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 19 22 Nov 14:18:47 ntpd[40932]: Listen and drop on 0 v6wildcard [::]:123 22 Nov 14:18:47 ntpd[40932]: Listen and drop on 1 v4wildcard 0.0.0.0:123 22 Nov 14:18:47 ntpd[40932]: Listen normally on 2 Internal network 165.100.10.1:123 22 Nov 14:18:47 ntpd[40932]: Listen normally on 3 DICOM network 3.204.31.137:123 22 Nov 14:18:47 ntpd[40932]: Listen normally on 4 Loopback Pseudo-Interface 1 [::1]:123 22 Nov 14:18:47 ntpd[40932]: Listen normally on 5 Loopback Pseudo-Interface 1 127.0.0.1:123 22 Nov 14:18:47 ntpd[40932]: receive: KoD packet from 3.204.31.138 has inconsistent xmt/org/rec timestamps. Ignoring. 22 Nov 14:19:51 ntpd[40932]: receive: KoD packet from 3.204.31.138 has inconsistent xmt/org/rec timestamps. Ignoring. 22 Nov 14:20:56 ntpd[40932]: receive: KoD packet from 3.204.31.138 has inconsistent xmt/org/rec timestamps. Ignoring. 22 Nov 14:22:03 ntpd[40932]: receive: KoD packet from 3.204.31.138 has inconsistent xmt/org/rec timestamps. Ignoring. 22 Nov 14:23:10 ntpd[40932]: ntservice: The Network Time Protocol Service is stopping. Client has ntp.conf with below details: peer 127.127.1.0 server 3.204.31.138 prefer key 1 keys <path to keys file> trustedkey 1 tinker step 0 server has below in ntp.conf peer 127.127.1.0 server 165.100.10.1 keys <path to keys file> trustedkey 1 2 3 4 5 tinker step 0 Environment windows7 for client and server I am struck here, as I am unable to go further, in wireshark capture I am seeing the NTP packets being exchanged between client and server. Thanks in advance On Tue, Nov 22, 2016 at 8:05 AM, sneha b <snehabadardi...@gmail.com> wrote: > Just a small update in client conf file: > > peer 127.127.1.0 > server 3.204.31.138 prefer key 1 > keys <path to keys file> > trustedkey 1 > tinker step 0 > > On Tue, Nov 22, 2016 at 8:03 AM, sneha b <snehabadardi...@gmail.com> > wrote: > >> Hi, >> >> I am using ntp.4.2.8, compiled the source code from ntp.org and using >> the same. >> But when I try to run ntpd.exe the client is not syncing with server, if >> I change time in client and run ntpd.exe -q I see some KoD packets received >> at client side. >> Below is the message I am seeing: >> >> C:\Windows\SysWOW64>ntpd.exe -q >> 22 Nov 14:18:47 ntpd[40932]: ntp-keygen 4.2.8p8@1.3265-o Oct 28 >> 12:19:56.86 (UTC+05:0-30) 2016 (1): Starting >> 22 Nov 14:18:47 ntpd[40932]: Command line: ntpd.exe -q >> 22 Nov 14:18:47 ntpd[40932]: Raised to realtime priority class >> 22 Nov 14:18:47 ntpd[40932]: Clock interrupt period 15.625 msec >> 22 Nov 14:18:47 ntpd[40932]: Performance counter frequency 2.604 MHz >> 22 Nov 14:18:47 ntpd[40932]: Windows clock precision 0.977 msec, min. >> slew 6.400 ppm/s >> 22 Nov 14:18:47 ntpd[40932]: using Windows clock directly >> 22 Nov 14:18:47 ntpd[40932]: proto: precision = 976.500 usec (-10) >> 22 Nov 14:18:47 ntpd[40932]: proto: fuzz beneath 0.174 usec >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 11 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 12 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 13 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 14 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 15 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 16 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 17 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 18 >> 22 Nov 14:18:47 ntpd[40932]: authreadkeys: invalid type for key 19 >> 22 Nov 14:18:47 ntpd[40932]: Listen and drop on 0 v6wildcard [::]:123 >> 22 Nov 14:18:47 ntpd[40932]: Listen and drop on 1 v4wildcard 0.0.0.0:123 >> 22 Nov 14:18:47 ntpd[40932]: Listen normally on 2 Internal network >> 165.100.10.1:123 >> 22 Nov 14:18:47 ntpd[40932]: Listen normally on 3 DICOM network >> 3.204.31.137:123 >> 22 Nov 14:18:47 ntpd[40932]: Listen normally on 4 Loopback >> Pseudo-Interface 1 [::1]:123 >> 22 Nov 14:18:47 ntpd[40932]: Listen normally on 5 Loopback >> Pseudo-Interface 1 127.0.0.1:123 >> 22 Nov 14:18:47 ntpd[40932]: receive: KoD packet from 3.204.31.138 has >> inconsistent xmt/org/rec timestamps. Ignoring. >> 22 Nov 14:19:51 ntpd[40932]: receive: KoD packet from 3.204.31.138 has >> inconsistent xmt/org/rec timestamps. Ignoring. >> 22 Nov 14:20:56 ntpd[40932]: receive: KoD packet from 3.204.31.138 has >> inconsistent xmt/org/rec timestamps. Ignoring. >> 22 Nov 14:22:03 ntpd[40932]: receive: KoD packet from 3.204.31.138 has >> inconsistent xmt/org/rec timestamps. Ignoring. >> 22 Nov 14:23:10 ntpd[40932]: ntservice: The Network Time Protocol Service >> is stopping. >> >> Client has ntp.conf with below details: >> >> peer 127.127.1.0 >> server 3.204.22.22 prefer key 1 >> keys <path to keys file> >> trustedkey 1 >> tinker step 0 >> >> server has below in ntp.conf >> peer 127.127.1.0 >> server 165.100.10.1 >> keys <path to keys file> >> trustedkey 1 2 3 4 5 >> tinker step 0 >> >> >> I am struck here, as I am unable to go further, in wireshark capture I am >> seeing the NTP packets being exchanged between client and server. >> >> Thanks in advance >> > > _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
