User manual

Masterclock NTDS Series User Manual – v2 – December 2012
26
If these continue to be ongoing problems, consider the Telnet
configuration method or remove the device to an isolated LAN.
Clock periodically resets itself
Clock appears in red text under
WinDiscovery device tree
Clock is being assigned an IP address of
169.254.xxx.xxx
Clock is showing an “Error” field under the status
window in WinDiscovery
Possible reasons and solutions:
1. Incorrect network configuration may be causing the device
to receive a fallback IP address and or perform soft restarts.
Verify that the IP address configured for the device is
correct. If you manually enter (or DHCP assigns) an IP
address that already exists on the network, this will create
an IP address conflict. The device will reset its address
(fallback) to one within the link-local address space.
Determine the cause of fallback IP address and resolve
issue. View the error status field under the status window to
help determine the cause of why the device received a
“169.254.xxx.xxx”. Near the bottom of the status window
the error will be displayed. (If there is no error the text box
will not be displayed.)
2. If static IP addressing is being used the original conflicting
static IP address can be restored. Perform a soft restart of
the network device using either WinDiscovery or Telnet
prior to changing any other configuration parameters.
3. If DHCP was selected and the network device falls back to a
“169.254.xxx.xxx” address approximately every 10 minutes
(depending upon the “Advanced Settings” values) the
Ethernet interface will be reinitialized and the network
device will attempt to get an IP address from the DHCP
server. If the network device is successful, the error will be
cleared and the new address from the DHCP server will be
used. If a discovery was done using WinDiscovery or Telnet
was used this initialization will be delayed by two hours.
Status LED is flashing
Status in WinDiscovery says ‘”Unsynchronized”
Clock is unable to find NTP reference, either primary
or secondary
Possible reasons and solutions:
1. Verify that the NTP server(s) specified are reachable,
communicating, and are not flagging their reported time as
invalid. Use a PC-based SNTP client application to verify the
server(s) if necessary.
If the configuration of the network device
is changed while a “169.254.xxx.xxx” is
being used (for example: changing the
Time Zone offset), then the current
“169.254.xxx.xxx” address will become the
permanent static address and the original
conflicting static address will be lost.
At this point, it is necessary to manually
change the static IP address to one that
does not conflict, or you may do a [Reset
Configuration] to restore the system to
factory default settings.