User manual

Masterclock www.masterclock.com

Troubleshooting

WinDiscovery uses bi-directional UDP messaging on port 6163 for both the discovery process and

to communicate configuration and status packets to and from the NTP network device(s). Delivery

of UDP messages/packets is not guaranteed. If you experience intermittent problems with

WinDiscovery, close the current session and restart the application. If this does not resolve the

issue try the following troubleshooting tips, or switch to an alternate method of configuration.

Lost password

Possible reasons and solutions:

A password cannot be recovered if it is lost or forgotten. Reset the device to the factory default

configuration using the procedure described in the section, “Default Password” (page 14). Then

the unit can be reconfigured and provided with a new password. The default password will once

again be “public”.

Unable to find/discover the device on the network using WinDiscovery

Possible reasons and solutions:

1. The discovery process was not complete before selecting your device(s). After clicking

[Discover] wait until the status indicates 100% completion.

2. Verify that all network cables, hubs, etc. are in proper working order. Be sure that Ethernet

cross-over cables are not being used where inappropriate.

3. Verify that the network device is on the same physical network as the computer from

which you are running WinDiscovery. If the computer is separated from the device by a

router or a firewall it is likely that the router/firewall is blocking communication with the

device. Run WinDiscovery from a computer within the remote network, or ask a network

system administrator to configure the router/firewall in question to pass through (both

directions) UDP broadcasts on port 6163. If this does not resolve the detection problems

you may additionally configure to pass through both directions UDP broadcasts on ports

6165, 6166, and 6264.

4. Verify that the hub/router/switch is capable of supporting the 10mb speed that the

attached network device requires.

5. Verify that a DHCP/BOOTP server is present on the network. If the device has been

configured to use DHCP for network configuration but no DHCP/BOOTP server is present,

the device may not respond to discovery requests for up to twenty seconds after power-

on. DHCP configuration is enabled as a factory-default. In addition, the device will reset its

fallback address to one within the link-local address space “169.254.xxx.xxx” when no

DHCP server is present or is not able to be reached. Reset the device to initiate a new

DHCP IP address request, or use static IP address mode. Consult your network system

administrator to ensure that a DHCP server is present and accessible on your network

and/or to obtain a list/range of available IP addresses.