NTP100 – Rev 1.0.1 Dec-04
26
© Masterclock
®
, Inc.
Disclaimer
Masterclock, Inc. cannot provide technical support for the above-described client packages. Masterclock, Inc. makes no
warranty, either expressed or implied, with respect to any of these client software packages. Masterclock, Inc. specifically
disclaims the implied warranties of merchantability or fitness for a particular purpose.
Troubleshooting Tips
Problem: Unable to find the NTP100 on the network with WinDiscovery
Connectivity issues:
1. Verify that the NTP100 and the computer running WinDiscovery are attached to the network.
2. Verify that all network cables, hubs, etc. are in proper working order. Be sure that ethernet crossover cables are not
being used where inappropriate.
Router/Firewall issues:
1. Verify that the NTP100 is on the same logical network as the computer from which you are running WinDiscovery. If
the computer is separated from the NTP100 by a router, that is, on a remote network - it is likely that the router 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 in question to pass through (both directions) UDP traffic on port
6163.
2. Some routers will not forward UDP broadcasts across networks – currently, this capability is required to use
WinDiscovery for enterprise-level management of Masterclock, Inc. network appliances.
3. If you are running a personal firewall product, such as ZoneAlarm
TM
or BlackICE
TM
, you must adjust their configuration
to pass through (both directions) UDP traffic on port 6163.
Other:
1. If the NTP100 has been configured to use DHCP for network configuration but no DHCP/BOOTP server is present, the
NTP100 may not respond to discovery requests for up to twenty seconds after power-on.
[Note: DHCP is disabled as a
factory-default.]
Problem: Unable to communicate with the NTP100 on the network with Telnet
2. If the NTP100 has been configured to use DHCP for network configuration the but no DHCP/BOOTP server is present,
the NTP100 may not respond to discovery requests for up to twenty seconds after power-on.
[Note: DHCP is disabled
as a factory-default.]
[Note: 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.]
Problem: NTP client is unable to communicate with the NTP100
1. Verify that the NTP100 is attached to the network.
2. Verify that all network cables, hubs, etc. are in proper working order. Be sure that ethernet crossover cables are not
being used where inappropriate.
3. Verify that the NTP100 is actually reachable from the client. Try “pinging” the IP address of the NTP100. If this fails, it
is possible that the NTP100 has an invalid network configuration or that the network is down. Consult your network
administrator for assistance.
4. Verify that the NTP100 is set to output if operating in internal oscillator/real time clock mode and that the maximum
time difference has not been exceeded.
