Troubleshooting Terminal Server Ssl Connections - GE Multinet 4 Instruction Manual

CHAPTER 7: TERMINAL SERVER APPLICATION NOTES
7.9

Troubleshooting Terminal Server SSL Connections

Example Symptom
Connection is not made and no
events appear in the event log.
Event: "Serial port S1 reports that
the host at 192.168.1.2 is
unreachable"
Event: "Serial port S1 reports that
the host at 192.168.1.2 is down"
Event: "Serial port S1 reports that
the connection to the host at
192.168.1.2 (10201) was refused"
Event: "Serial port S1
experienced a problem
(unsupported protocol) while
connecting to the host at
192.168.1.2 (10201)"
Event: "Serial port S1
experienced a problem (no
shared cipher) while connecting
to the host at 192.168.1.2
(10201)"
MULTINET4 MULTI-PORT SERIAL SERVER & MANAGED SWITCH – INSTRUCTION MANUAL
If a terminal server connection between two Multinet4s cannot be established, use the
table below to determine what is wrong.
Table 7–1: Troubleshooting Terminal Server Connections
The local Multinet4 unit is not
attempting to connect out.
The local Multinet4 unit
attempted to connect to the
remote unit but it was
unreachable or the TCP port is
not open.
The SSL handshake could not
complete because the peer is
attempting to use a protocol that
we do not support.
The SSL handshake could not
complete because no shared
cipher was available.
TERMINAL SERVER APPLICATION NOTES
Problem
Verify that the serial port is
enabled and in the UP
operational state. A connection
will not be attempted from a
serial port that is DOWN or
DISABLED.
Note: Enabling a serial port and
setting "Ignore DSS" to TRUE will
force a serial port into the UP
state.
Verify that the remote unit is
reachable by logging into the
Command Line Interface (CLI)
and using the ping command.
Verify that the specified port is
open/available on the remote
unit by using a PC to telnet to the
port. If the connection is refused,
your remote unit is probably not
configured properly.
Verify that the operational state
of the remote serial port is UP. A
connection will not be accepted
on a port that is in the DOWN or
DISABLED state.
Check your configuration. Make
sure that both sides of the
connection allow compatible
cipher suites.
Check your configuration. Make
sure that both sides of the
connection allow compatible
ciphers suites.
Resolution
7–15