X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C801EE.C250AFD3@onstor-exch02.onstor.net>; Fri, 28 Sep 2007 08:43:55 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: NTP from a win2k3 server
Date: Fri, 28 Sep 2007 08:43:55 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0346AA35@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E045EBCE6@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: NTP from a win2k3 server
Thread-Index: AcgBnpaXYVcnQzTSSaC+910t5CP+GAAAPOQSABLsImA=
From: "John Rogers" <john.rogers@onstor.com>
To: "Huy Duong" <huy.duong@onstor.com>,
	"David Crispin" <david.crispin@onstor.com>,
	"dl-cstech" <dl-cstech@onstor.com>

We use Windows 2003 as our NTP server in the lab. Its available at
10.2.0.7 if you want to try it out.

Here is a couple article on Windows Time Service.

Windows Time Service Overview
http://technet2.microsoft.com/WindowsServer/en/library/71e76587-28f4-427
2-a3d7-7f44ca50c0181033.mspx?mfr=3Dtrue

Configuring Time Services for a Heterogeneous UNIX and Windows
Environment
http://www.microsoft.com/technet/solutionaccelerators/cits/interopmigrat
ion/unix/usecdirw/21wsdsu.mspx

I think the real guts of it is that you have to change this key from
NT5DS to NTP.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\
Type



-----Original Message-----
From: Huy Duong=20
Sent: Friday, September 28, 2007 12:17 AM
To: David Crispin; dl-cstech
Subject: Re: NTP from a win2k3 server

Will not work. If you do a google search on ntp and windows, you will
many articles saying windows doesn't act properly as an ntp server.
-----------------------------------------
Huy Duong
ONStor Strategic Support Account Manager=20
Phone 408.963.2478=20
Cell    408.431.6803=20
http://support.onstor.com/
Sent From My Blackberry


-----Original Message-----
From: David Crispin
To: dl-cstech
Sent: Fri Sep 28 00:10:02 2007
Subject: NTP from a win2k3 server

I have two customers who told me that their w2k3 servers were set up as
NTP servers. The bobcats are not using them and are using their internal
clocks. I can't figure out why they won't sync to the "alleged" NTP
server.

=20

Here is the output of a few ntp commands and system show time commands
from both customers. Why won't they use the NTP server time?

=20

Oncore IT

=20

oncore-nas1# ntpdate -d 10.6.0.242

28 Sep 08:00:35 ntpdate[7115]: ntpdate 4.1.0 Thu Sep  6 14:38:30 PDT
2007 (1)

transmit(10.6.0.242)

receive(10.6.0.242)

transmit(10.6.0.242)

receive(10.6.0.242)

transmit(10.6.0.242)

receive(10.6.0.242)

transmit(10.6.0.242)

receive(10.6.0.242)

transmit(10.6.0.242)

server 10.6.0.242, port 123

stratum 1, precision -6, leap 00, trust 000

refid [LOCL], delay 0.04124, dispersion 0.01363

transmitted 4, in filter 4

reference time:    caa60254.87d70a3d  Thu, Sep 27 2007 11:20:04.530

originate timestamp: caa7250a.e4000000  Fri, Sep 28 2007  8:00:26.890

transmit timestamp:  caa72513.e5757d5a  Fri, Sep 28 2007  8:00:35.896

filter delay:  0.04124  0.04124  0.04124  0.04124

         0.00000  0.00000  0.00000  0.00000

filter offset: -9.02126 -9.00566 -9.00568 -9.00570

         0.000000 0.000000 0.000000 0.000000

delay 0.04124, dispersion 0.01363

offset -9.021264

=20

28 Sep 08:00:35 ntpdate[7115]: step time server 10.6.0.242 offset
-9.021264 sec

=20

oncore-nas1# ntptrace 10.6.0.242

oncore-olb03.oncore-olb.local: stratum 1, offset -9.014407, synch
distance 10.87709, refid 'LOCL'

oncore-nas1#

=20

oncore-nas1 ONCORE-NVS01 diag> syst ti sh -v

Fri Sep 28 08:00:18 BST 2007

status=3D0544 leap_none, sync_local_proto, 4 events, =
event_peer/strat_chg,

version=3D"ntpd 4.1.0 Thu Sep  6 14:38:29 PDT 2007 (1)",

processor=3D"pmonmips", system=3D"OpenBSD2.8", leap=3D00, stratum=3D11,

precision=3D-15, rootdelay=3D0.000, rootdispersion=3D11.948, peer=3D84,

refid=3D127.127.1.0,

reftime=3Dcaa724c6.5dc2d278  Fri, Sep 28 2007  7:59:18.366, poll=3D6,

clock=3Dcaa72502.68003254  Fri, Sep 28 2007  8:00:18.406, state=3D4,

offset=3D0.000, frequency=3D0.000, jitter=3D0.043, stability=3D0.000

     remote           refid      st t when poll reach   delay   offset
jitter

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D

*127.127.1.0     127.127.1.0     10 l   60   64  377    0.000    0.000
0.031

 10.6.0.242      .LOCL.           1 u   47   64  377    0.031  -9006.8
0.031

oncore-nas1 ONCORE-NVS01 diag>

=20

Securidata

=20

true2# ntpdate -d 192.168.20.202

28 Sep 08:07:45 ntpdate[22721]: ntpdate 4.1.0 Mon Jun  4 14:16:44 PDT
2007 (1)

transmit(192.168.20.202)

receive(192.168.20.202)

transmit(192.168.20.202)

receive(192.168.20.202)

transmit(192.168.20.202)

receive(192.168.20.202)

transmit(192.168.20.202)

receive(192.168.20.202)

transmit(192.168.20.202)

server 192.168.20.202, port 123

stratum 1, precision -6, leap 00, trust 000

refid [LOCL], delay 0.04124, dispersion 0.00002

transmitted 4, in filter 4

reference time:    caa61c56.9428f5c2  Thu, Sep 27 2007 13:11:02.578

originate timestamp: caa72591.38000000  Fri, Sep 28 2007  8:02:41.218

transmit timestamp:  caa726c1.21cbab64  Fri, Sep 28 2007  8:07:45.132

filter delay:  0.04124  0.04124  0.04124  0.04124

         0.00000  0.00000  0.00000  0.00000

filter offset: -303.913 -303.913 -303.913 -303.913

         0.000000 0.000000 0.000000 0.000000

delay 0.04124, dispersion 0.00002

offset -303.913208

=20

28 Sep 08:07:45 ntpdate[22721]: step time server 192.168.20.202 offset
-303.913208 sec

=20

true2# ntptrace 192.168.20.202

192.168.20.202: stratum 1, offset -303.917595, synch distance 10.80170,
refid 'LOCL'

true2#

=20

true2> sys ti sh -v

Fri Sep 28 08:06:09 BST 2007

status=3D0544 leap_none, sync_local_proto, 4 events, =
event_peer/strat_chg,

version=3D"ntpd 4.1.0 Mon Jun  4 14:16:42 PDT 2007 (1)",

processor=3D"pmonmips", system=3D"OpenBSD2.8", leap=3D00, stratum=3D11,

precision=3D-18, rootdelay=3D0.000, rootdispersion=3D11.841, =
peer=3D6596,

refid=3D127.127.1.0,

reftime=3Dcaa72626.7df1cfbb  Fri, Sep 28 2007  8:05:10.491, poll=3D6,

clock=3Dcaa72661.d4fabda0  Fri, Sep 28 2007  8:06:09.831, state=3D4,

offset=3D0.000, frequency=3D0.000, jitter=3D0.005, stability=3D0.000

     remote           refid      st t when poll reach   delay   offset
jitter

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D

*127.127.1.0     127.127.1.0     10 l   59   64  377    0.000    0.000
0.004

 192.168.20.202  .LOCL.           1 u   44   64  377    0.004  -303913
10.223

true2>

=20

=20

=20



David Crispin
Technical Services Manager

ONStor, Inc.
office: +44(0)118 963 5866
mobile: +44(0)7940 547 895

david.crispin@onstor.com <mailto:david.crispin@onstor.com>=20
http://www.onstor.com <http://www.onstor.com>=20

=09

=09

=20

