© Sealevel Systems, Inc.
- 64 -
SeaLINK User Manual
Pinpointing the Problem
When trouble arises, the first challenge (and often the most difficult part of the
problem) is to determine where a configuration issue is occurring. The following
procedure is recommended:
1.
Make sure the IP Address and Port Number for the SeaLINK serial
server are correct.
SeaLINK will not be able to connect to the remote
devices unless it is configured with the proper information.
2.
Run the Configuration Wizard to verify the IP Address and Port
Number.
If the Configuration Wizard does not run successfully, then
SeaLINK will not be able to function using the specified IP Address and Port
Number. There are many reasons why a Configuration Wizard session may
fail. The most common reason is the following:
•
Entering the incorrect IP port number in the SeaLINK Manager window.
A common mistake is to assume the TCP/IP port number is the "device number" on
the server. These numbers should be in the range of 4680 to 4696.
NOTE:
Any port number not in this range is incorrect and must be changed.
If more information is necessary, see the Wizard Status and Error Messages section
of this manual.
3.
Verify the make and model of Windows Modem Device installed.
Many
applications (such as Windows HyperTerminal and Dial-Up Networking)
require a Windows modem device to automatically dial. If the installed
device driver on the local PC does not match the modem(s) in the serial
server, then dialing will not succeed even when the Configuration Wizard
does
succeed.
4.
Verify the Application Requirements.
Certain applications require COM
Port Control. See the
Applications Settings
section to see if this may be a
requirement for you.
5.
If the application still fails, collect trace data and look for problems.
In
the event you need to contact Sealevel Systems support group, one of the
first things you may be asked for is a trace file collected during the
application failure. It is helpful to be familiar with the procedure for doing
this in advance. Because reading trace data is fairly self-explanatory, many
users can pinpoint the cause of certain problems from this information. See
the trace window discussion for details.
