The reference NTP implementation - of which Meinberg provides a packaged M$WIN-version - is perfectly capable of logging.
Adding a few more servers to each PC and maybe adding the other PC as a server would make faultfinding easier. -- Björn On Thu, May 17, 2007 4:45, Bill Hawkins said: > Ah, well. You seem to have all the bases covered, except for the 9 > second error. How about using a freeware SNTP client with those IP > addresses. The client needs to keep a log; maybe you will need some > shareware. I use Tardis and YATS32. > > The log will show you gross errors, like seconds. SNTP logs the > request time, the receipt time at the server, the sent time at the > server and the receipt time at your PC. > > Dunno about Meinberg. Prefer the Brandenberg Concertos myself. > > Bill Hawkins > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Joseph Gray > Sent: Wednesday, May 16, 2007 8:13 PM > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] NTP problem on Windows > >>I am not familiar with the Meinberg software so I am guessing that if >>you are running that NTP software you would not be using Windows time > service? >> If you don't need Windows time service, go into services and stop the > >>windows time service and set it to "manual" or "disabled". My thinking > >>is the Windows time service may be conflicting with your time > software. >> >> Mike >> W8RKO > > Already done. Thanks for trying. > > > _______________________________________________ > time-nuts mailing list > [email protected] > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > > _______________________________________________ > time-nuts mailing list > [email protected] > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > _______________________________________________ time-nuts mailing list [email protected] https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
