Unruh wrote: > Steve Kostecke <koste...@ntp.org> writes: > >> On 2009-02-14, Unruh <unruh-s...@physics.ubc.ca> wrote: > >>> gary.limanap...@elisys.co.uk writes: >>> >>>> The only way we can stop it is to disable W32Time process on the >>>> Tablets, but this then leaves them unsynchronised. Still searching for >>>> a solution? >>> So this definitely sounds like a bug of some kind in the Windows >>> server's ntp code. Are they running the ntpd reference implimentation >>> or what ntp software are they running? > >> w32time ... see the quoted text from the OP. > > > It is w32 time on the tablets, but they are not the problem, the server is. > It is the server, he said, which pumps out packets trying to change the > polling interval of the clients every 300ms. Thus it > is the server's program which one needs to look into. At least that was how > I read the post. > Note that one could surely install ntpd onto the tablets instead of > W32Time. > to keep them synchronized. >
What kind of server controls the client's polling interval? The server can send a "kiss of death" packet and a compliant implementation is supposed to stop polling altogether! This does not seem, to me, to be quite the same as changing the client's polling interval! At the very least, someone has an extremely limited, or totally incorrect, understanding of what is going on. _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
