Table of Contents
Advertisement
9.6
Solutions to Possible Problems
9.6.1
Possible Common Problems
Solutions to possible common problems are described in the table below.
Table 9-1: Solutions to Possible Common Problems
Problem
Possible Cause
No
Software does not
communicati
function in the device
on
Network problem
Network definitions
BootP did not reply to
the board/module
ini file was
TFTP server down
not loaded
TFTP server didn't
get the request
TP-1610 didn't
request the file from
your TFTP
TFTP server bug
BootP sent to a board
with the wrong TFTP
server address
ini file does not exists
in the default
directory of the TFTP
server
User's Manual
Solutions
Try to "ping" the board/module. If ping fails, check for
network problems/definitions and try to reset the
board/module
Check the cables.
Check if the default gateway can reach the IP of the
board/module.
Check if the board/module got the correct IP.
Check the validity of the IP address, subnet and default
gateway.
If the default gateway is not used, enter 0.0.0.0
Check if the BootP server replied to the board/module at
restart by viewing the log of the BootP server.
Try to restart the BootP server.
Check the MAC address of the board/module in the
BootP server.
Check if the TFTP server is working.
Check the log of the TFTP server.
Check that the TFTP server's IP address is the one that
the TP-1610 is trying to use by viewing the Syslog.
Try to restart the TFTP server.
Check the IP address of the TFTP server being used.
Check the default directory of the TFTP server and check
that the ini file exists there.
214
MG 3200
Document # LTRT-72704
Advertisement
Table of Contents
Troubleshooting
