Here are some troubleshooting tips if you are unable to connect to the Process Software SSH server from an SSH client

The server can be started with the following commands for each product:

TCPWARE
$ @TCPWARE:STARTNET SSH

MULTINET
$ @MULTINET:START_SERVER SSH

SSH for OpenVMS
$ @SYS$STARTUP:PSCSSH$STARTUP

First check for the presence of the process named "SSHD Master" (use the command $ SHOW SYSTEM). This process must exist for SSH connections to be made from other computers.

If the process does not exist after executing the command to start the SSH server, here are some suggestions:

  • Has a host key been generated? Before starting the SSH server, you will need to generate host keys using the following commands for each product:

    MultiNet and SSH for OpenVMS:
    $ MULTINET SSHKEYGEN/SSH1/HOST to generate SSHv1 host key, and
    $ MULTINET SSHKEYGEN/SSH2/HOST to generate SSHv2 host key.

    TCPware:
    $ SSHKEYGEN/SSH1/HOST to generate SSHv1 host key, and
    $ SSHKEYGEN/SSH2/HOST to generate SSHv2 host key.

    Note that you don't need to generate SSH1 host key if you're not going to allow SSH1 sessions and the same for SSH2 host keys and sessions.

  • Is the SSH server configured to support SSHv1 or SSHv2 or both? If you are trying to connect to the server using SSHv1 and the server is configured for SSHv2 only, it will not work. Check your configuration to determine which version of SSH connections are enabled.

  • Finally, look at the server log file SSH_DIR:SSHD_MASTER.LOG for hints of something else that can be causing a problem.

 

Search: