@johnpoz:
Its not using itself as a reference - I have a ntp server running on 192.168.1.40.. If I query it its using stratum 1 servers.. All my boxes and devices use it as ref, that first one is my pc I am on, then I changed over and looked at the server, then last one is pfsense showing what its talking too.
As you can see pfsense uses 192.168.1.40 as its ref, not itself. Pfsense is a vm - using it as a time source would be pretty inaccurate.
Got it. Thanks.
@johnpoz:
As to w32tm yes it is a ok tool for that sort of thing.. As to what you were using to sync - that analog X or whatever, why?? Why not just run ntp? Runs on pretty much anything, as you can see its running on windows.. While w32tm is not a bad cmd line tool for troubleshooting, the time sync in windows is a bit lacking. I always just turn it off and install ntp directly. You can get latest builds from here http://www.satsignal.eu/ntp/setup.html
I was just using AnalogX for testing. I wanted a free, simple NTP client that I knew how to use.
I wasn't using w32tm at the command line because I didn't know how to. I tried playing with settings in the time/date menu, but I found that it wasn't particularly reliable. Outside of testing, I've found that the Windows utility both fails often, and isn't easily configurable to sync more than one per week (playing with the registry doesn't seem to fix it permanently- I just had it reset back to once per week by itself.) On two machines in particular I have several reasons for wanting to keep the clocks within a couple seconds of the real time, I've generally found I (usually) lose more than that over a week. So, thanks for the link to the ntp utility. I'll give it a try.