[ntp:questions] Re: NTPD on Windows NT4

Anders anders.REMOVETHIS.r1f.ANDTHIS at tele2.se
Sat Aug 13 09:36:55 UTC 2005


"Martin Burnicki" <martin.burnicki at meinberg.de> skrev i meddelandet 
news:ddj3h2$q10$1 at online.de...
> Hi Anders,
>
> Anders wrote:
>
>> Hi Group!
>>
>> I'm trying to run XNTPD on an old WinNT4 machine. Having installed the
>> Meinberg package ntp-4.2.0a at 1.1354-o-win32-setup.exe I can't get it
>> working. The eventlog says:
>> "clock LOCAL(1) event 'clk_fault' (0x03)"
>> "configuration of xx.xx.xx.xx failed" and
>> "Could not find suitable interface for xx.xx.xx.xx"
> [...]
>
> This are 2 different things which are bugs in the NTP version in that
> packet. Please note that those GUI installers have been created from
> developer versios of NTP because the stable version of the NTP port for
> Windows is lacking some features.
>
>
> 1.) clock LOCAL(1) event 'clk_fault' (0x03)
>
> This is a known bug which has been fixed in a recent developer version of
> NTP, see:
> https://ntp.isc.org/bugs/show_bug.cgi?id=434
>
> The message simply results from a variable which has not been properly
> initilized so that the message is printed before the clock's status has
> been checked. You can simply ignore it. BTW, this happens under all
> operating systems and is not specific to Windows.
>
>
> 2.) configuration of xx.xx.xx.xx failed
>
> This is also a known bug which only happens under Windows NT, not under
> Windows 2000 and newer, see:
> https://ntp.isc.org/bugs/show_bug.cgi?id=450
>
> Here the NTP daemon is unable to initialize the network interface 
> properly,
> which results in that the daemon is unable to contact any upstream server.
>
> This bug has not yet been fixed and closed in bugzilla, but there is a NTP
> version available which contains a workaround for this:
> http://www.meinberg.de/download/ntp/windows/experimental/ntp-4.2.0a@1.1397beta-o-win32-setup.exe
>
> AFAIK this version works for Windows NT if and only if the machine has one
> single network card installed.
>
> Please let us know if that version also solves the problem for you.
>
>
> Best regards,
>
> Martin
> -- 
> Meinberg Funkuhren
> Bad pyrmont
> Germany
>

I tried the beta version mentioned above and it works splendidly!! Now the 
NTPQ pe command reads:
ntpq> pe
     remote           refid      st t when poll reach   delay   offset 
jitter
==============================================================================
 LOCAL(1)        LOCAL(1)        12 l    1   64  177    0.000    0.000 
0.004
+ntp2.gbg.netnod .PPS.            1 u   62   64   77    8.669  -1045.1 
14.947
-c-f93470d5.06-2 192.36.143.151   2 u    2   64  177   18.260  -1040.8 
2.525
+nic.lth.se      131.188.3.222    2 u    4   64  177   15.232  -1043.4 
1.663
*ntp2.sp.se      .PPS.            1 u    5   64  177   20.659  -1045.1 
1.471
-ntp1-sn2.hy.ska 192.36.133.17    2 u    3   64  177   14.801  -1042.4 
1.291

Many thanks!!

Anders J 





More information about the questions mailing list