[ntp:questions] Re: Re: NTPD on Windows NT4

Heiko Gerstung heiko.gerstung at meinberg.de
Mon Aug 15 04:29:04 UTC 2005


Hi Danny and David,

Danny Mayer wrote:
>> - using the Terje Mathisen V4.2.0 release, with the ntpd.conf file 
>> generated by the failed Meinberg installation, NTP would see all the 
>> configured remote servers
>>
> 
> Sounds like an installer problem but I can't tell why.

There is a bug in the current developer version causing all recent
versions not to be able to run on NT4. The problem lies in the interface
detection routines.  See https://ntp.isc.org/bugs/show_bug.cgi?id=450

>> - using either the ntp-4.2.0a at 1.1354-o-win32-setup.exe or 
>> ntp-4.2.0a at 1.1370-o-win32-setup.exe from Meinberg, the setup failed at 
>> the point where it tried to install the service, however...
>>
This seems to be a bug in the installer, but I was able to install the
service here under NT4. Did you try to install it using the SYSTEM
account (in order to be sure that this is no access restrictions related)?

>> - I could use the instsrv.exe from Terje's release to install the 
>> Meinberg version, but both versions failed to see the external 
>> servers.  The local clock (at stratum 12) could be seen OK.  This is 
>> using the command:  ntpq -p
>>
>> - I think both Meinberg versions contain the same .exe files - the 
>> 1370 .exe files appear to be dated.
>>
> 
> I've no clue. Heiko would know.
No, they should contain different exe versions, but I'll check that when
I get back to my desk on Monday.

>> - I've just realised that there is a more recent Meinberg version - 
>> ntp-4.2.0a at 1.1397beta-o-win32-setup.exe - and installing that just in 
>> "upgrade the files" mode results in files dated June 2005 and, more 
>> importantly, the remote servers can now be seen.
>>
> 
> That one may well have the changes I made to the I/O completion ports 
> code. It depends on when it got built. It may well affect your charts. 
> I'd be interested in seeing the charts.
No, that version contains a workaround for bug #450, it overrides the
interface detection routines and simply binds to the first interface it
sees. This version is only usable on systems with only one interface
(i.e. one network interface card and one TCP/IP interface). I created it
for a few customers who experienced the same problems (no remote  servers).

Kind regards,
Heiko






More information about the questions mailing list