NTP100 – Rev 2.2.0 Oct-12
42
© Masterclock
®
, Inc.
If setting up an authoritative time server from a PDC in Windows Server 2000 or Windows Server 2003 refer to the
knowledgebase articles on the Microsoft support site regarding editing the registry settings for the selection of the
internal hardware clock or external time source for Windows 32Time service.
The Microsoft support knowledgebase article #816042 entitled: “ How to configure an authoritative time server in
Windows Server 2003 ” pertains to addressing the hardware clock issue in Windows Server 2003.
http://support.microsoft.com/kb/816042/
The Microsoft support knowledgebase article #3140542 entitled: “ How to configure an authoritative time server in
Windows XP ” pertains to addressing the hardware clock issue in Windows XP.
http://support.microsoft.com/kb/314054/
The Microsoft support knowledgebase article #216734 entitled: “ How to configure an authoritative time server in
Windows Server 2000 ” pertains to addressing the hardware clock issue in Windows Server 2000 (Note: This article
was previously published under Q216734 http://support.microsoft.com/kb/216734/
The Microsoft support knowledgebase article #223184 entitled: “ Registry entries for the W32Time service”
pertains to addressing the registry entries Windows Server 2000 and Windows 2000 (Note: This article was
previously published under Q223184 http://support.microsoft.com/kb/223184/
The Microsoft support knowledgebase article #884776 entitled: “ How to configure the Windows Time service
against a large time offset” contains useful information regarding the W32Time service in Windows Server 2003,
Windows XP Pro, and Windows Server 2000 http://support.microsoft.com/kb/884776/
Problem: NTP client indicates that the NTP100 is providing invalid time, or has flagged time as invalid.
The NTP100 will always answer NTP requests (unless the client is set to use symmetric active mode), but will flag time as
invalid if it does not have trusted time to distribute. This may occur temporarily during GPS navigation state changes, or
before the first GPS acquisition after the NTP100 has been powered on after being off for an extended period of time.
By default, the NTP100 will begin flagging time invalid after 24 hours of consecutive GPS acquisition failure or non-
operation (powered off). This is a protective feature, and can be adjusted or disabled if desired – see device configuration
sections of this user manual.
Problem: The UTC date/time is incorrect and the unit does not retain configuration settings when powered up.
The NTP100 maintains its internal configuration and settings in battery backed memory located on the RTC chip. The
battery supplies power to the TCXO 32kHz Oscillator and RTC when the unit is powered off. This allows the internal
configuration to be maintained and the time and date to increment, when power is off. Under normal operating condition, the
memory devices maintaining the RTC data and configuration settings is powered by the external DC power supply and does
not rely on the battery for data retention.
Note: If the NTP100 does not retain its configuration, or its Date/Time settings (often indicated by the front panel time
display counting up from ‘zero’) the battery will likely need replacement.
Check and replace the battery, if necessary. The battery type is a ‘replaceable’ 3V lithium coin cell battery and can be
replaced by a qualified technician, or the unit can be sent to technical support at Masterclock for repair/replacement for
service using our RMA procedure. The battery size/type vary for the various models. See the “Specifications” section for
details on the recommended battery replacement, or contact technical support for assistance.
To Next Page
Loading...