right .. I was asking to try to figure out how you could solve this. There's nothing wrong with that model.

Just make one the time server, point the others (ntp clients) at that one, or have them pick up the broadcasts from the time server. That way they will all have the same time, and then you can occasionally adjust the clock on the time server to compensate for the inherent drift. Just use the (statically assigned) IP address of the one you pick to be the server when you configure the time service on the clients. I forget if Windows allows you to configure it for broadcasts or not, but it's even easier if it allows you to set it up that way.

I have no idea how much a reference clock costs. Apparently they use GPS now. It would be interesting to see if there's a cheap/easy way to add a reference clock to your network.

Looks like there's a w32time service, and you have to configure it via the registry. ugh.

-David


-David