[ntp:questions] ntpd service doesn't connect to remote servers on Windows XP

David J Taylor david-taylor at blueyonder.neither-this-bit.nor-this.co.uk
Thu Apr 2 15:56:01 UTC 2009

Dave Hart wrote:
> On Apr 2, 8:54 am, "David J Taylor" <david-tay... at blueyonder.neither-
> this-bit.nor-this.co.uk> wrote:
>> Running from the command-line, we get:
>> 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.
> The Can't create I/O event handle is the error you'll see with
> Meinberg's vegas-v2 when there is another ntpd.exe hanging around.
> Keep in mind the message claiming the service has stopped is a lie, it
> is coming from the service as it is about to stop.  My QPC releases as
> well as official versions starting with 4.2.4p7RC1 and 4.2.5P160 will
> give a differrent error in that case, likely complaining about being
> unable to bind to address for example, possibly with a
> different IP address but definitely with port 123.
> That doesn't explain why the first process failed, but it does hint it
> is not terminating cleanly after failing.
> Martin's suggestion to try a debug binary with tracing enabled is
> probably the next fruitful approach.
> Cheers,
> Dave Hart

Thanks, Dave.  I've pointer the user to debug binaries.  I should tell him 
to add a PAUSE after the NET STOP in his batch file.


More information about the questions mailing list