Re: Peer to Peer
- From: "Mark St Laurent" <stormrunner'_removethis'@comcast.net>
- Date: Tue, 27 Sep 2005 00:17:49 GMT
The following commands run from command line
w32tm /config /manualpeerlist:(ciscorouter ip) /syncfromflags:manual /update
{for Windows XP}
[this config appears to force sync against list rather than PDC]
w32tm -v -once -period 65532 {for Windows 2000}
appear to perform some form of time sync and appear to be doing so via port
123. Granted given that the second example switch (-period 65532) only
updates every 8 hours the 20 ms tolerance is not sustainable. Is this what
you mean by "W32Time does not support broadcast [S]NTP" or that it does not
update via these broadcasts period. It appears to be working am I missing
something?
{A drawback to W32time config above is someone invoking time applet from
system tray which overwrites reg file. I am hoping local group policy can
avert this.}
> It's arguably a first party implementation as it is the reference
> implementation
By third party I meant not native to operating system requiring a separate
install.What product are you referring to as the "reference implementation"
and how is it available.
My objective here is to sync within 1 min for coordination of batch files
dependant upon tasks running on peer PC's, the reliability factor is more
important to me than the tolerance.
Thanks for your time.
"David Woolley" <david@xxxxxxxxxxxxxxxxxxx> wrote in message
news:T1127767049@xxxxxxxxxxxxxxxxxxxxxx
> In article <wfVZe.2791$KQ5.2144@xxxxxxxxxxxxxxxxxxxxxxxxxx>,
> Mark St Laurent <stormrunner'_removethis'@comcast.net> wrote:
>
>> My authoritative server would be my ciso router that does sync with
>> stratum
>> 2 time source then broadcasts to the LAN. I also found this post entitled
>
> W32Time does not support broadcast [S]NTP.
>
>> to peer. I have trouble believing that windows peer configured machines
>> have
>> no native way to sync with NTP broadcasts. Also I see additional post
>
> Peer Windows networks can't use kerberos and don't have revenue generating
> server machines in them. The only reason for W32Time is to support
> kerberos.
>
> Please remember that a product like Windows XP tends to be a single
> product with some parameter tweaks and parts disabled to produce versions
> that can be sold for different amounts of money. Providing central
> time services is one of those things that gets enabled by paying more
> money
> for the server version.
>
> I have a feeling that the only nobbling for XP is in not automatically
> configuring the server address.
>
>> mentioning free client obviously third party implementation what is the
>> concensus on most used NTP Client for this and how would it be preferable
>> to
>> what was discussed previously.
>
> It's arguably a first party implementation as it is the reference
> implementation
> of NTP which other valid implementations strive to emulate.
>
> The advantages are:
>
> - it implements the protocol it claims to implement correctly;
> - it implements the full NTP protocol so for Windows will hold the time in
> synch to around 20ms most of the time (rather better on other OSes);
> - it supports broadcast mode.
>
> W32Time does none of these.
>
> Except for those with an axe to grind about their pet *S*NTP client, I
> think
> you will find there is unanimous agreement that you should use the
> reference implementation. The only real question is which particular
> Windows port to use.
>
> Note, it seems the subject refers to the structure of the Windows network,
> not to the structure of the time distribution network.
.
- Follow-Ups:
- Re: Peer to Peer
- From: David J Taylor
- Re: Peer to Peer
- References:
- Peer to Peer
- From: Mark St Laurent
- Re: Peer to Peer
- From: David Woolley
- Re: Peer to Peer
- From: Mark St Laurent
- Re: Peer to Peer
- From: David Woolley
- Peer to Peer
- Prev by Date: Servers just doen't work (after following the troubleshooting page)
- Next by Date: Re: Servers just doen't work (after following the troubleshooting page)
- Previous by thread: Re: Peer to Peer
- Next by thread: Re: Peer to Peer
- Index(es):
Relevant Pages
|
