Troubleshooting Tips - Symmetricom ND-CLK User Manual

TROUBLESHOOTING TIPS

[Important Note: 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 ND network clock(s). Delivery of UDP messages/packets is not guaranteed. If
you experience intermittent problems with WinDiscovery , try closing the current session
and restart the application. If this does not resolve the issue try the following trouble
shooting tips, or switch to an alternate method of configuration such as telnet.]
Problem: Unable to find [discover] the clock on the network with WinDiscovery.
Possible reasons/solutions:
1. The discovery process was not complete before selecting clock(s). After selecting
"Discover" button, wait until the discovery status indicates 100% completion.
2. Verify that the clock is on the same physical network as the computer from which
you are running WinDiscovery. If the computer is separated from the clock by a
router (on a remote network) 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 [Note: 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].
3. Verify that the hub/router/switch is capable of supporting the 10MB speed that the
attached network clock requires.
4. Verify that a DHCP/BOOTP server is present on the network. If the clock has been
configured to use DHCP for network configuration but no DHCP/BOOTP server is
present, the clock may not respond to discovery requests for up to twenty seconds
after power-on. [Note: DHCP configuration is enabled as a factory-default.] In
addition, the clock will reset its address (fallback) 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 clock 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.
5. Verify that the clock and the computer running WinDiscovery are attached to the
network.
6. 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.
Problem: Clock was found using WinDiscovery, but the status display is intermittent or
not updating and/or clock does not appear to be responding to configuration changes
under the current WinDiscovery session.
Problem: Clock(s) previously found during a recent session of WinDiscovery do not
show up during the current session.
Problem: The clock status or settings displayed under WinDiscovery show garbled
characters.
ND-CLK User Manual- Rev 1.0.1 - Sep-08
34
®
Symmetricom , Inc