User manual

Masterclock RC 500 User Manual – v2014.01.01

is saved and returned as an error to WinDiscovery. This error status is available to the user via

the Status window on WinDiscovery.

If the configuration of the network device is changed while a 169.254.xxx.xxx is being use, then

the current 169.254.xxx.xxx address will become the permanent static address and the original

conflicting static address is lost. At this point, it is necessary to manually change the static IP

address to one that will not conflict, or you may do a “Reset Configuration” to restore the

system to factory default settings.

3. If DHCP was selected and the network device fell back to a 169.254.xxx.xxx address

approximately every 10 [depending upon the “Advanced Setting” values] minutes the Ethernet

interface will be reinitialized and the RC500 will attempt to get an IP address from the DHCP

sever. If the 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 1 hour.

RC500 appears to ‘reset’ periodically

Possible reasons/solutions:

1. Check the network connection and setup. If DHCP is enabled [Note: DHCP is enabled by default]

and a DHCP server is not active on the local network the clock will hesitate periodically while

attempting to resolve DHCP configuration. To correct the problem, switch to manual networking

configuration or determine why the local DHCP server is not operating.

2. If the device cannot resolve its DHCP mode, the unit will periodically perform a soft restart to

reinitialize its communication port and DHCP configuration.

3. If the RC500 has not been configured with a least one valid DNS server (or that DNS server is

down) hesitations similar to those described in #1 will occur. At least one valid DNS server is

required for operation.

Unable to communicate with the RC500 using Telnet

Possible reasons/solutions:

1. If the Slimline NTD has been configured to use DHCP for network configuration but no

DHCP/BOOTP server is present, the Slimline NTD may not respond to discovery requests for up to

twenty seconds after power-on. [Note: DHCP is enabled as a factory-default.]

2. Verify that you have the correct IP address for the unit and the IP address did not change. If using

DHCP to provide the IP address, this address may change periodically; you must know the IP

address of the unit to use the TELNET interface.

3. Verify that the device does not have the Telnet interface disabled.

For security purposes, the Telnet interface can be disabled. When disabled, you will no longer

be able to access the unit with Telnet. To re-enable the Telnet feature, one of the other

configuration methods must be used, or the unit must be reset to factory default

configuration.

Lost the password

Possible reasons/solutions:

1. The password cannot be recovered if it is lost. Reset the clock to the factory default configuration

using the procedure described in the Configuration section. After the clock has been reset to

factory defaults, the unit must be reconfigured. The factory - default password is “public”