NTP to Windows 2000 Server 1

[routy]

Hello,

i'm trying to establish a ntp time sync from a Cisco router to a Windows 2000 Server (192.168.24.180) which is itself synchronized with another server (192.168.25.90). Therefore it has a stratum of 2.

The router is a cisco 2620XM runing IOS 12.3(6).

I configured "ntp server 192.168.24.180 prefer" on the router.

The router is receiving ntp packets (see below) but the ntp server is always in the state "insane, invalid" and the time is not synced. If have "debug ntp validity" enabled but can not see any errors.

I tried to configure HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ReliableTimeSource = 1 on the Windows Server with no effect.

Has anyone successful synced with a Windows Server?

Joachim

r01#sho ntp a

address ref clock st when poll reach delay offset disp
~192.168.24.180 192.168.25.90 2 240 1024 377 5.3 -2907. 0.1
* master (synced), # master (unsynced), + selected, - candidate, ~ configured

r01#show ntp a detail
192.168.24.180 configured, insane, invalid, stratum 2
ref ID 192.168.25.90, time C9229487.BB8CFDA9 (14:24:23.732 MET Thu Dec 7 2006)
our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024
root delay 0.00 msec, root disp 1000.02, reach 377, sync dist 1002.762
delay 5.26 msec, offset -2907.2393 msec, dispersion 0.12
precision 2**7, version 3
org time C9229AA6.D8D4FDF3 (14:50:30.846 MET Thu Dec 7 2006)
rcv time C9229AA9.C1C28226 (14:50:33.756 MET Thu Dec 7 2006)
xmt time C9229AA9.C06924E4 (14:50:33.751 MET Thu Dec 7 2006)
filtdelay = 5.26 5.05 5.04 5.00 5.14 4.99 5.42 4.93
filtoffset = -2907.2 -2907.1 -2907.1 -2907.1 -2907.1 -2907.1 -2907.3 -2907.0
filterror = 0.02 0.03 0.05 0.06 0.08 0.09 0.11 0.12

r01#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**16
reference time is 00000000.00000000 (01:00:00.000 MET Mon Jan 1 1900)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec

r01#show debug
NTP:
NTP clock parameters debugging is on
NTP events debugging is on
NTP loop filter debugging is on
NTP packets debugging is on
NTP clock synchronization debugging is on
NTP clock selection debugging is on
NTP peer validity debugging is on
NTP reference clocks debugging is on

.Dec 7 14:50:33.751 MET: NTP: xmit packet to 192.168.24.180:
.Dec 7 14:50:33.751 MET: leap 3, mode 3, version 3, stratum 0, ppoll 1024
.Dec 7 14:50:33.751 MET: rtdel 0000 (0.000), rtdsp 10001 (1000.015), refid 00000000 (0.0.0.0)
.Dec 7 14:50:33.751 MET: ref 00000000.00000000 (01:00:00.000 MET Mon Jan 1 1900)
.Dec 7 14:50:33.751 MET: org C9229AA5.D8D4FDF3 (14:50:29.846 MET Thu Dec 7 2006)
.Dec 7 14:50:33.751 MET: rec C9229AA8.C1B4A493 (14:50:32.756 MET Thu Dec 7 2006)
.Dec 7 14:50:33.751 MET: xmt C9229AA9.C06924E4 (14:50:33.751 MET Thu Dec 7 2006)
.Dec 7 14:50:33.755 MET: NTP: rcv packet from 192.168.24.180 to 159.173.172.227 on FastEthernet0/0:
.Dec 7 14:50:33.755 MET: leap 0, mode 4, version 3, stratum 2, ppoll 1024
.Dec 7 14:50:33.755 MET: rtdel 0000 (0.000), rtdsp 10001 (1000.015), refid 92F9FE5A (192.168.25.90)
.Dec 7 14:50:33.755 MET: ref C9229487.BB8CFDA9 (14:24:23.732 MET Thu Dec 7 2006)
.Dec 7 14:50:33.755 MET: org C9229AA9.C06924E4 (14:50:33.751 MET Thu Dec 7 2006)
.Dec 7 14:50:33.759 MET: rec C9229AA6.D8D4FDF3 (14:50:30.846 MET Thu Dec 7 2006)
.Dec 7 14:50:33.759 MET: xmt C9229AA6.D8D4FDF3 (14:50:30.846 MET Thu Dec 7 2006)
.Dec 7 14:50:33.759 MET: inp C9229AA9.C1C28226 (14:50:33.756 MET Thu Dec 7 2006)
.Dec 7 14:50:33.759 MET: NTP: 192.168.24.180: offset -2.907239293, delay 0.00526, error 0.00002clock_filter(192.168.24.180, -2.907239, 0.00526, 0.00002)

.Dec 7 14:50:33.759 MET: NTP: nlist 0, allow 0, found 0, low 0.000000, high 0.000000
.Dec 7 14:50:33.759 MET: NTP: no select intersection
.Dec 7 14:50:33.759 MET: NTP: no select intersection

 

[ADB100]

It doesn't work..........

I tried this a while ago and after a bit of searching and debugging I realised it won't work with the Windows 2000/2003 Time Service. This is due to the Windows Time Service just being SNTP (Simple NTP) and not NTP.

It does work the other way around though - i.e. configure your router to sync with an external time source or a GPS clock etc and then synchronise your Windows Server to the router.

HTH

Andy

 

[routy]

I followed your tip and it works as expected.

Thanks

Achim

 

[UnaBomber]

Why doesnt this surprise me?

/bash

UnaBomber
ccnp mcse2k