Troubleshoot the problem that your clients cannot connect to your IBM Aspera Point-to-Point Client.
The following diagram shows the troubleshooting procedure if clients can't establish a FASP transfer connection to your Point-to-Point. Follow the instructions to identify and resolve problems:
# telnet 10.0.1.1 33001
If the client cannot establish connections to your Point-to-Point, verify the port number and the firewall configuration on your Point-to-Point machine.
# ssh firstname.lastname@example.org -p 33001
If the SSH service runs normally, the client should see a message prompting to continue the connection or for a password. However, if you see a "Connection Refused" message, which indicates that the SSH service isn't running, review your SSH service status. Ignore the "permission denied" message after entering the password, which is discussed in next steps.
Permission denied (publickey,keyboard-interactive).
Open your SSH Server configuration file with a text editor:
To allow public key authentication, add or uncomment the PubkeyAuthentication yes. To allow password authentication, add or uncomment PasswordAuthentication yes. Here is a configuration example:
... PubkeyAuthentication yes PasswordAuthentication yes ...
To reload SSH service, execute the following command:
$ sudo service sshd restart
$ sudo /etc/init.d/ssh restart
To make sure that the client can establish a SSH connection to your Point-to-Point, and has correct system user credentials, use this command on the client machine: (Connect Server address: 10.0.1.1, login: aspera_user_1/aspera, TCP/33001)
$ ssh email@example.com -p 33001 firstname.lastname@example.org's password:
Enter the user's password when prompted. If you see "Permission denied" message, you may have a wrong user credentials, or the user has docroot configured and doesn't have sufficient access permissions to access it. Refer to Setting Up Users or Setting Up Transfer Users (Terminal) for instructions about setting up the user account, and review the user's docroot directory's permissions.
If you still encounter connection problems after going through these steps, contact Technical Support.