Troubleshooting your Telnet SSL server

Here are the detailed steps for troubleshooting your Secure Sockets Layer (SSL) server including system SSL return codes and a list of common SSL problems. To identify problems with your Telnet SSL server, follow these steps:

1. Check your system status to verify that the proper software has been installed and that the servers are started.

2. Ping your host server to check that TCP/IP is started and the network is OK.

3. Check that the Telnet server is started.

4. Check for an active SSL listener by using the NETSTAT *CNN command.

5. Check the Telnet job log to find the SSL return code.

6. Look up the SSL problems and return codes for suggestions to solve the problem.

Incorrect digital certificates can cause many problems with SSL. Digital Certificate Manager (DCM) lets you change your certificate authority (CA) or system certificates. To confirm that you have a valid system certificate, read how to start Digital Certificate Manager (DCM) and then view the system certificate.

• Checking system status
  You need to confirm that your Telnet is ready for Secure Sockets Layer (SSL) sessions.

• Checking for an active SSL listener
  Use this procedure to check for an active Secure Sockets Layer (SSL) listener. The Telnet server must be active and ready to receive connection attempts.

• Checking the Telnet job log
  When Secure Sockets Layer (SSL) initialization and handshake fails, the Telnet server sends CPDBC nn diagnostic messages to the QTVTELNET job.

• SSL return codes
  The topic lists the system Secure Sockets Layer (SSL) return codes for the most common problems that might occur during SSL initialization or SSL handshake.

Parent topic:

Related concepts
Securing Telnet with SSL DCM concepts Starting Digital Certificate Manager