Re: ntp not synchronising
From: Michael D. Ober (obermd._at_.alum.mit.edu.nospam)
Date: 07/07/05
- Next message: My name is hidden: "IS the Hobbyist program active, I can't get any results"
- Previous message: Brad Hamilton: "Re: Now the UK Has it's own date in the history of al quiada attacks"
- In reply to: prep_at_prep.synonet.com: "Re: ntp not synchronising"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 7 Jul 2005 07:19:37 -0600
The time constraints for Windows are based on the requirements for the
Kerberos Authentication scheme. Thus, MS decided to embed SNTP instead of
NTP. Our network uses a Windows 2000 server that receives it's time from a
public Stratum 2 server. I have never had our windows systems more than 5
seconds off from WWV and WWVH radio when using the built in SNTP service.
On the other hand, I was never successful at getting a third party NTP
server for Windows to work.
NTP is supposed to be accurate to a few milliseconds. SNTP accuracy is
rated at a few seconds. The messages passed between a NTP client and a NTP
server are identical to the messages passed between a NTP client and a SNTP
server.
Mike Ober.
<prep@prep.synonet.com> wrote in message
news:87irznalm7.fsf@prep.synonet.com...
> Martin Hunt <martin.hunt@fairfaxnz.REMOVE.co.nz> writes:
>
> > I'm told that it is ntp (not sntp) on a Windows system. I'm also told
> > that (after a couple of hops) this system gets its time from the
> > internet. But it is becoming pretty obvious to me that this is not the
> > case.
>
> Windows ntp is know to be a total slag pit. Don't even THINK of trusting
> it.
>
> > I have manually set the VMS clock from radio time signals and,
> > according to the Windows system, VMS is running 95 seconds slow. I
> > know this can't possibly be true, and have asked the operators of
> > the intermediate boxes to verify this synchronisation. Hopefully
> > they will get it working properly.
>
> > What I want to know now is, what tells the VMS ntp that a clock is
> > not synchronised? Which comand and output (on ntpq or ntpdc) will
> > show this as the reason for the clock being rejected?
>
> ntpdc -p will give you the bumph. You should get the docs from
> ntp.org and read and understand them.
>
> $ mc tcpip$ntptrace
> LOCALHOST: stratum 3, offset 0.000488, synch distance 0.22771
> k9.prep.synonet.com: stratum 2, offset 0.298446, synch distance 0.18645
> murgon.cs.mu.OZ.AU: stratum 1, offset -0.048752, synch distance 0.00075,
refid 'GPS'
>
> That is from my Alpha, to the MX running Linux, to Melb Uni. You should
> be able to do the same and get a trace back to a stratum 1 server. Be
> interesting to see what sort of a mess you have.
>
> ntp and windows; just say NO!
>
> --
> Paul Repacholi 1 Crescent Rd.,
> +61 (08) 9257-1001 Kalamunda.
> West Australia 6076
> comp.os.vms,- The Older, Grumpier Slashdot
> Raw, Cooked or Well-done, it's all half baked.
> EPIC, The Architecture of the future, always has been, always will be.
>
- Next message: My name is hidden: "IS the Hobbyist program active, I can't get any results"
- Previous message: Brad Hamilton: "Re: Now the UK Has it's own date in the history of al quiada attacks"
- In reply to: prep_at_prep.synonet.com: "Re: ntp not synchronising"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
