GE Multinet 4 Instruction Manual page 246

TERMINAL SERVER APPLICATION NOTES
Example Symptom
Event: "Serial port S1 reports that
the certificate presented by the
host at 192.168.1.2 (10201) was
invalid (certificate has expired)"
Event: "Serial port S1 reports that
the certificate presented by the
host at 192.168.1.2 (10201) was
invalid (certificate is not yet
valid)"
Event: "Serial port S1 received a
notification (sslv3 alert
certificate expired) from the host
at 192.168.1.2 (10201)"
Event: "Serial port S1 reports that
the certificate presented by the
host at 192.168.1.2 (10201) was
invalid (self signed certificate in
certificate chain)"
Event: "SSL: Message from peer
on channel SX (tlsv1 alert
unknown ca)."
7–16
Table 7–1: Troubleshooting Terminal Server Connections
Problem
The SSL handshake failed during
certificate verification because
the current day and time are not
within the peer certificate's valid
date range
The SSL handshake failed during
certificate verification because
your certificate has expired.
The SSL handshake failed during
certificate verification because
an un-trusted self-signed
certificate was found in the
chain.
The SSL handshake failed during
certificate verification because
you presented an un-trusted
self-signed certificate in your
certificate chain.
MULTINET4 MULTI-PORT SERIAL SERVER & MANAGED SWITCH – INSTRUCTION MANUAL
CHAPTER 7: TERMINAL SERVER APPLICATION NOTES
Make sure your system's time
and date is set properly.
Check the certificate on the
other system and make it has
appropriate "notBefore" and
"notAfter" dates.
Make sure the other system's
time and date are set properly.
Check your key file and make
sure that the enclosed certificate
file has appropriate "notBefore"
and "notAfter" dates.
Make sure that you have
installed the peer's root CA
certificate and have marked it as
trusted.
Make sure that you are
presenting a valid certificate
chain (that is, each certificate in
a valid chain is signed by the
next certificate in the chain,
except for the final certificate,
which is a self-signed root CA
certificate).
Make sure that the other system
has installed your CA's certificate
and marked it as trusted.
Resolution