ntp on win3k

fisko · ‎03-06-2007

hello

I have cisco 1841 in lan that is a gateway for the Lan.In that Lan i have domain controler with NTP enabled. After I configure ntp server (ip of domain controler) i get the message that ntp is "insane"

Here is the output fro sh ntp status and sh ntp assotiation detail

sh 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**18

reference time is 00000000.00000000 (00:00:00.000 UTC 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

sh ntp associations detail

x.x.x.x configured, insane, invalid, stratum 1

ref ID .LOCL., time C9970015.8420C49B (20:46:13.516 UTC Mon Mar 5 2007)

our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024

root delay 0.00 msec, root disp 10559.74, reach 377, sync dist 10698.761

delay 0.84 msec, offset -132542.6057 msec, dispersion 138.61

precision 2**6, version 3

org time C997B7B8.F4000000 (09:49:44.953 UTC Tue Mar 6 2007)

rcv time C997B83D.7F03B6F8 (09:51:57.496 UTC Tue Mar 6 2007)

xmt time C997B83D.7ECCB175 (09:51:57.495 UTC Tue Mar 6 2007)

filtdelay = 0.84 0.89 0.92 0.93 0.96 1.02 0.98 0.81

filtoffset = -132542 -132464 -132386 -132292 -132292 -132292 -132292 -132292

filterror = 0.02 15.64 31.27 46.89 46.91 46.92 46.94 46.95

What could be the issue?Is there any extra configurations on Win3k to work with cisco? Win 3k does not use external sources.There is no any access lists between router and domain controler

akemp · ‎03-06-2007

Windows doesn't really use or supply NTP unless you configure it to do so, instead it uses w32time which is +/- 20 seconds accurate:

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

Here's how you set up ntp on w2k3:

http://support.microsoft.com/kb/816042

fisko · ‎03-06-2007

I already have ntp on my domain controler win2k3 that is not using external clock resources.

steve.busby · ‎03-06-2007

First I would check the clock on your router, ensure it's set close in time to the NTP server. If it's too far off, it won't sync.

The only other thing I've seen in the past is the dispersion setting on W2K3 is too high.

http://technet2.microsoft.com/WindowsServer/en/library/a9fb3bdd-766e-4137-9321-d9dc14a08b0d1033.mspx?mfr=true

HTH

Steve

fisko · ‎03-06-2007

I already have that register configured in win2k3. When i set time on router close to NTP time it seems that this time had been synchronized.

When I write

sh clock detail i get the time correct and i get message that NTP is source.

when i issue sh ntp association i get the same result that NTP is "insane"

How to verify this?

THANKS!

andrew.butterworth · ‎03-07-2007

I have never seen this work, nor been able to get it to work using the W32Time service on Windows 2000 or 2003. 3rd party 'proper' NTP time servers work if you disable the W32Time Service.

The best way to configure this is to swap it around - i.e. get a couple of your core switches/routers to sync externally to valid time servers or better still an internal GPS clock. Then synchronise your Windows Domain Controller off the Cisco switches/routers.

HTH

Andy

steve.busby · ‎03-07-2007

Like Andy, I've also experienced a lot of issues getting Cisco equipment to time sync with Win 2000 or 2003. In theory 2003 is using NTP and we would expect MS to follow industry standards, most Cisco equipment using SNTP will sync ok, but there is still those few devices that don't.

If you don't want to sync off your Cisco devices, then I would suggest setting up a small linux distro and setting it up as your domain time source.

HTH

Steve

Danilo Dy · ‎03-07-2007

Windows is by default an NTP Client, not NTP Server. To make it an NTP Server, you need to configure the registry http://www.gude.info/english/main-windows-ntp.htm

andrew.butterworth · ‎03-07-2007

Medan - I have tested this previously and it doesn't work if your IOS devices are NTP clients. If your devices are SNTP clients (low end 800-series routers, Wireless AP's etc) then it does work.

Andy