[Eisfair] ntp tut's nicht
Jürgen Pfautsch
newsreply6 at clubeckstein.de
Sa Aug 19 14:06:38 CEST 2017
> "Olaf Jaehrling" schrieb im Newsbeitrag
> news:on7mpp$r2t$1 at vm-news.spline.inf.fu-berlin.de...
> Hallo Marcus,
> Aber zurück zum Thema. Was sagt denn
> ntpdate -d time.fu-berlin.de
> bzw
> ntpdate -d 1.asia.pool.ntp.org
Hier die Protokolle nach stop des Servers:
eis2 # ntpdate -d 1.asia.pool.ntp.org
19 Aug 18:42:58 ntpdate[6557]: ntpdate 4.2.8p9 at 1.3265-o Thu Dec 22 18:49:38
UTC 2016 (1)
Looking for host 1.asia.pool.ntp.org and service ntp
129.250.35.250 reversed to x.ns.gin.ntt.net
host found : x.ns.gin.ntt.net
transmit(129.250.35.250)
receive(129.250.35.250)
[snip ...]
receive(80.241.0.72)
server 129.250.35.250, port 123
stratum 2, precision -20, leap 00, trust 000
refid [129.250.35.250], delay 0.22369, dispersion 0.00034
transmitted 4, in filter 4
reference time: dd429f1c.a946a05c Sat, Aug 19 2017 18:27:24.661
originate timestamp: dd42a2ca.9be7ae12 Sat, Aug 19 2017 18:43:06.609
transmit timestamp: dd42a2c9.72cb0316 Sat, Aug 19 2017 18:43:05.448
filter delay: 0.22426 0.22369 0.22383 0.22403
0.00000 0.00000 0.00000 0.00000
filter offset: 1.061320 1.060936 1.061300 1.061360
0.000000 0.000000 0.000000 0.000000
delay 0.22369, dispersion 0.00034
offset 1.060936
server 211.233.40.78, port 123
stratum 2, precision -20, leap 00, trust 000
refid [211.233.40.78], delay 0.10425, dispersion 0.00008
transmitted 4, in filter 4
reference time: dd429e77.76b70b98 Sat, Aug 19 2017 18:24:39.463
originate timestamp: dd42a2ca.c0ebba84 Sat, Aug 19 2017 18:43:06.753
transmit timestamp: dd42a2c9.a5ee7a13 Sat, Aug 19 2017 18:43:05.648
filter delay: 0.10464 0.10425 0.10480 0.10440
0.00000 0.00000 0.00000 0.00000
filter offset: 1.065944 1.065977 1.066398 1.066026
0.000000 0.000000 0.000000 0.000000
delay 0.10425, dispersion 0.00008
offset 1.065977
server 80.241.0.72, port 123
stratum 1, precision -23, leap 00, trust 000
refid [PPS], delay 0.34258, dispersion 0.00150
transmitted 4, in filter 4
reference time: dd42a2c8.01610755 Sat, Aug 19 2017 18:43:04.005
originate timestamp: dd42a2cb.aab5330c Sat, Aug 19 2017 18:43:07.666
transmit timestamp: dd42a2ca.72bcc821 Sat, Aug 19 2017 18:43:06.448
filter delay: 0.35245 0.34846 0.34258 0.34286
0.00000 0.00000 0.00000 0.00000
filter offset: 1.064987 1.063323 1.060447 1.060001
0.000000 0.000000 0.000000 0.000000
delay 0.34258, dispersion 0.00150
offset 1.060447
server 61.216.153.107, port 123
stratum 3, precision -24, leap 00, trust 000
refid [61.216.153.107], delay 0.13306, dispersion 56.00000
transmitted 4, in filter 4
reference time: dd42a124.bdab3afe Sat, Aug 19 2017 18:36:04.740
originate timestamp: dd42a2cb.269c28a0 Sat, Aug 19 2017 18:43:07.150
transmit timestamp: dd42a2ca.0c5aa1d1 Sat, Aug 19 2017 18:43:06.048
filter delay: 0.00000 0.00000 0.00000 0.13306
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 1.048828
0.000000 0.000000 0.000000 0.000000
delay 0.13306, dispersion 56.00000
offset 1.048828
19 Aug 18:43:06 ntpdate[6557]: step time server 80.241.0.72 offset 1.060447
sec
eis2 # ntpdate -d 3.kh.pool.ntp.org
19 Aug 18:43:38 ntpdate[9706]: ntpdate 4.2.8p9 at 1.3265-o Thu Dec 22 18:49:38
UTC 2016 (1)
Looking for host 3.kh.pool.ntp.org and service ntp
118.67.201.10 reversed to ns2.cidc.com.kh
host found : ns2.cidc.com.kh
transmit(118.67.201.10)
receive(118.67.201.10)
[snip...]
receive(118.67.200.10)
server 118.67.201.10, port 123
stratum 2, precision -20, leap 00, trust 000
refid [118.67.201.10], delay 0.02831, dispersion 0.00050
transmitted 4, in filter 4
reference time: dd429dd0.a5dd5922 Sat, Aug 19 2017 18:21:52.647
originate timestamp: dd42a2f1.8f3b4eb7 Sat, Aug 19 2017 18:43:45.559
transmit timestamp: dd42a2f0.7d874055 Sat, Aug 19 2017 18:43:44.490
filter delay: 0.03456 0.02905 0.02910 0.02831
0.00000 0.00000 0.00000 0.00000
filter offset: 1.065175 1.067422 1.067802 1.067795
0.000000 0.000000 0.000000 0.000000
delay 0.02831, dispersion 0.00050
offset 1.067795
server 103.245.79.2, port 123
stratum 2, precision -20, leap 00, trust 000
refid [103.245.79.2], delay 0.03333, dispersion 0.00053
transmitted 4, in filter 4
reference time: dd429c4d.8699de9f Sat, Aug 19 2017 18:15:25.525
originate timestamp: dd42a2f1.c2e67748 Sat, Aug 19 2017 18:43:45.761
transmit timestamp: dd42a2f0.b21617ef Sat, Aug 19 2017 18:43:44.695
filter delay: 0.03470 0.03337 0.03333 0.03339
0.00000 0.00000 0.00000 0.00000
filter offset: 1.062323 1.061616 1.061124 1.061768
0.000000 0.000000 0.000000 0.000000
delay 0.03333, dispersion 0.00053
offset 1.061124
server 103.245.79.18, port 123
stratum 2, precision -20, leap 00, trust 000
refid [103.245.79.18], delay 0.03352, dispersion 0.00098
transmitted 4, in filter 4
reference time: dd429e7e.e98b9bb0 Sat, Aug 19 2017 18:24:46.912
originate timestamp: dd42a2f1.f685381d Sat, Aug 19 2017 18:43:45.962
transmit timestamp: dd42a2f0.e4940484 Sat, Aug 19 2017 18:43:44.892
filter delay: 0.03459 0.03352 0.03549 0.05231
0.00000 0.00000 0.00000 0.00000
filter offset: 1.061670 1.061494 1.060267 1.056713
0.000000 0.000000 0.000000 0.000000
delay 0.03352, dispersion 0.00098
offset 1.061494
server 118.67.200.10, port 123
stratum 2, precision -20, leap 00, trust 000
refid [118.67.200.10], delay 0.02875, dispersion 0.00043
transmitted 4, in filter 4
reference time: dd42a13e.ecff413d Sat, Aug 19 2017 18:36:30.925
originate timestamp: dd42a2f2.2b20d5e3 Sat, Aug 19 2017 18:43:46.168
transmit timestamp: dd42a2f1.17221cdc Sat, Aug 19 2017 18:43:45.090
filter delay: 0.03024 0.02875 0.02914 0.04175
0.00000 0.00000 0.00000 0.00000
filter offset: 1.067378 1.067175 1.067099 1.070023
0.000000 0.000000 0.000000 0.000000
delay 0.02875, dispersion 0.00043
offset 1.067175
19 Aug 18:43:45 ntpdate[9706]: step time server 118.67.201.10 offset
1.067795 sec
Und hier der lokale nach Freigabe in der Windows-Firewall:
eis2 # ntpdate -d 192.168.1.3
19 Aug 18:55:39 ntpdate[29368]: ntpdate 4.2.8p9 at 1.3265-o Thu Dec 22 18:49:38
UTC 2016 (1)
Looking for host 192.168.1.3 and service ntp
host found : 192.168.1.3
transmit(192.168.1.3)
receive(192.168.1.3)
[...]
receive(192.168.1.3)
server 192.168.1.3, port 123
stratum 2, precision -10, leap 00, trust 000
refid [192.168.1.3], delay 0.02776, dispersion 0.00041
transmitted 4, in filter 4
reference time: dd42a533.90a3a59f Sat, Aug 19 2017 18:53:23.564
originate timestamp: dd42a5c2.89954f44 Sat, Aug 19 2017 18:55:46.537
transmit timestamp: dd42a5c1.75607aea Sat, Aug 19 2017 18:55:45.458
filter delay: 0.02927 0.02783 0.02776 0.02861
0.00000 0.00000 0.00000 0.00000
filter offset: 1.076149 1.077041 1.077274 1.077922
0.000000 0.000000 0.000000 0.000000
delay 0.02776, dispersion 0.00041
offset 1.077274
19 Aug 18:55:45 ntpdate[29368]: step time server 192.168.1.3 offset 1.077274
sec
Aber jetzt wird es spannend:
Set Time via other NTP Server (y/n)? y
* Stopping Ntp daemon ...
Try to set Time via 1.asia.pool.ntp.org ...
19 Aug 19:02:37 ntpdate[25649]: no server suitable for synchronization found
Try to set Time via 192.168.1.3 ...
19 Aug 19:02:44 ntpdate[26271]: adjust time server 192.168.1.3 offset
0.003324 sec
Hardware Clock Time is now ...
Sat Aug 19 12:02:46 2017 .510227 seconds
Software Clock Time is now ...
Sat Aug 19 19:02:47 ICT 2017
Immerhin eine Lösung über den Windows-NTP-Server.
Aber warum das nun an der cmd geht und im NTP-Programm nicht - ???
Danke
Jürgen
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
Mehr Informationen über die Mailingliste Eisfair