Bob wrote: > It does more than just answer. After the first packet - Frame 1 - I answer > within a couple of hundred milliseconds. I also begin polling the remote for > time. Frame 72, 73, 75, 76. The remote also shows up on my peer list with > whatever frequency was requested by the remote. If it's considered normal > for a remote to request my machine to alter it's peer list with disable auth > in the config file, I'll just remove that. This seems to conflict with an > earlier post, but if that's how it's supposed to work, then that's how it > is.
Use the restrict nopeer option to prevent it peering with other servers. Windows W32time service try to use peer by default. It's a bug in Microsoft's code. They should always use client/server mode. Someone probably just got lazy when coding it. Danny _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
