David J Taylor wrote: > Running from the command-line, we get: > > 2 Apr 09:39:08 ntpd.exe[3984]: logging to file log.txt > 2 Apr 09:39:08 ntpd.exe[3984]: precision = 1.000 usec > 2 Apr 09:39:08 ntpd.exe[3984]: Listening on interface #0 wildcard, > 0.0.0.0#123 Disabled > 2 Apr 09:39:08 ntpd.exe[3984]: Listening on interface #1 Loopback > Interface 1, 127.0.0.1#123 Enabled > 2 Apr 09:39:08 ntpd.exe[3984]: Listening on interface #2 IP Interface 2, > 192.168.1.10#123 Enabled > 2 Apr 09:39:08 ntpd.exe[3984]: frequency initialized 0.000 PPM from > e:\NTP\etc\ntp.drift > 2 Apr 09:39:22 ntpd.exe[3984]: ntservice: The Network Time Protocol > Service has stopped. > 2 Apr 09:40:16 ntpd.exe[344]: logging to file log.txt > 2 Apr 09:40:16 ntpd.exe[344]: Can't create I/O event handle: Input/output > error - another process may be running - EXITING > 2 Apr 09:40:16 ntpd.exe[344]: ntservice: The Network Time Protocol > Service has stopped. > > I don't believe that either ntpd.exe or w32tm.exe is running.....
If no ntpd (or another instance of it) is running, then which application should reply to "ntpq -p" requests? Maybe you can use one of Dave Hart's binaries for testing which have been built with DEBUG enabled: http://davehart.net/ntp/refclock/ There are some *-debug-bin.zip files. Run them from the command line wit -D3 or so, e.g. similar to: ntpd -n -D3 -g -M -c "c:\program files\ntp\etc\ntp.conf" and watch the console output, which shold tell you if reply packetes are received. Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
