[EMAIL PROTECTED] wrote: > Problem: ntpd.exe fails and is not active, even though ntpd NT service > is running. > > ntp.log displays > 10 Feb 22:29:00 ntpd.exe[5484]: The Network Time Protocol Service has > stopped. > 10 Feb 22:29:15 ntpd.exe[4924]: synchronized to 130.123.2.99, stratum > 2 > 10 Feb 23:16:01 ntpd.exe[4924]: IO Completion Error: The network > location cannot be reached. For information about network > troubleshooting, see Windows Help. > 11 Feb 09:25:23 ntpd.exe[4924]: no servers reachable > > Neither statsdir or logfile show any further activity after network > error. >
What version of ntpd are you using? If you are using DHCP to obtain your network address, please make sure you are running 4.2.4 or later. That version has support for addresses that are dynamically changing as with DHCP. > # ntp.conf > driftfile "C:\Program Files\NTP\etc\ntp.drift" > logfile "C:\Program Files\NTP\etc\ntp.log" > fudge 127.127.1.0 stratum 12 > server ntp.massey.ac.nz iburst minpoll 4 maxpoll 5 > statsdir "C:\Program Files\NTP\etc\" > filegen loopstats file loopstats type day enable > > > Is there some way to keep ntpd.exe alive and active, even after a > network failure? > Surely I don't have to stop and restart the NT service periodically? > Make sure you are running ntpd 4.2.4 or later. Danny > Thanks > Nick _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
