[ntp:questions] unix and windows environment sync to one NT4 timeserver "HOW"

Nicholas Suan nsuan at ryouga.mine.nu
Thu Jul 31 16:50:39 UTC 2003


Nicholas Suan <nsuan at ryouga.mine.nu> wrote:

> "David L. Mills" <mills at udel.edu> news:bga0sl$qqn$1 at dewey.udel.edu 
> 
>> David,
>> 
>> Better be sitting down when reading this message.
>> 
>> I found just now that an ex-box Win/XP Professional Edition machine
>> as server works just fine from a Unix client using ntpdate. So, who
>> needs tardis? That's the good news.
>> 
>> Now the bad; maybe not even bad at that. The same Win/XP Professional
>> Edition machine does NOT return packets from a configured ntpd
>> client. Holy cowbunger! The only difference between ntpdate and ntpd
>> is the former uses something other than port 123 in the source port
>> field. Is Win/XP so clever as that?
>> 

Just a note: It seems to be even more clever than that. XP Home won't 
return packets from a configured ntpd client when the source ports have 
been changed with a NAT router.


>> I'm tempted to conclude Win/XP is so exquisitely clever that it 
>> purposely declines to serve what is very likely a broken
>> configuration when ntpd is the client on the assumption the Win/XP
>> server is a terrible source, since it asks for real time like once
>> per week. Nah, Win/XP can't be that clever.
>> 
>> At the moment we have no XP here other than Professional Edition. Can
>> someone confirm with Home Edition?
>> 
> 
> Here's the results of running ntpdate against a box running XP Home
> 
> [ed at tomato ed]$ ntpdate -d 68.200.0.0
> 30 Jul 22:52:25 ntpdate[1254]: ntpdate 4.1.1 at 1.786 Mon Apr  8 06:30:53
> EDT 2002 
> (1)
> transmit(68.200.0.0)
> receive(68.200.0.0)
> transmit(68.200.0.0)
> receive(68.200.0.0)
> transmit(68.200.0.0)
> receive(68.200.0.0)
> transmit(68.200.0.0)
> receive(68.200.0.0)
> transmit(68.200.0.0)
> 68.200.0.0: Server dropped: strata too high
> server 68.200.0.0, port 123
> stratum 16, precision -6, leap 11, trust 000
> refid [0.0.0.0], delay 0.09871, dispersion 0.00481
> transmitted 4, in filter 4
> reference time:    c2d215da.9b3b4479  Wed, Jul 30 2003  5:00:58.606
> originate timestamp: c2d31105.a764917a  Wed, Jul 30 2003 22:52:37.653
> transmit timestamp:  c2d310f9.f6e10492  Wed, Jul 30 2003 22:52:25.964
> filter delay:  0.11743  0.14851  0.09871  0.17885
>          0.00000  0.00000  0.00000  0.00000
> filter offset: 11.62802 11.61394 11.62491 11.62070
>          0.000000 0.000000 0.000000 0.000000
> delay 0.09871, dispersion 0.00481
> offset 11.624914
> 30 Jul 22:52:26 ntpdate[1254]: no server suitable for synchronization
> found 
> 
> This compter was just rebooted recently, and has not had it's clock
> synced since then so I'm not sure what it will give me when it has
> been synced to a known source.


Here are the results after it was synced about nine minutes ago 
(IP addresses I have no control over have had the last two octets 
replaced by zero):

server 68.200.0.0, port 123
stratum 3, precision -6, leap 00, trust 000
refid [66.69.126.170], delay 0.08488, dispersion 0.00468
transmitted 4, in filter 4
reference time:    c2d3bc66.daf1a9fb  Thu, Jul 31 2003 11:03:50.855
originate timestamp: c2d3bed9.2f787a65  Thu, Jul 31 2003 11:14:17.185
transmit timestamp:  c2d3bed9.c57d6b65  Thu, Jul 31 2003 11:14:17.771
filter delay:  0.09917  0.09381  0.11317  0.08488
         0.00000  0.00000  0.00000  0.00000
filter offset: -0.60268 -0.61185 -0.59652 -0.60783
         0.000000 0.000000 0.000000 0.000000
delay 0.08488, dispersion 0.00468
offset -0.607835

31 Jul 11:14:17 ntpdate[3395]: step time server 68.200.0.0 offset -
0.607835 sec



More information about the questions mailing list