Your browser does not allow storing cookies. We recommend enabling them.


Defining Connection Profile Settings

Under the Connection Profile page, on the Connection tab, you can define the protocol settings used in the connection. Any changed connection settings will take effect the next time you log in.

Configuring connection profiles

Figure 3.6. Configuring connection profiles


In Profile name, type a name for the profile.


In Host name, enter the name of the remote host computer to which you want to connect with the profile.

In Port number, enter the port number you want to use for the Secure Shell connection. The default port is 22.


A Secure Shell server program must be listening to the specified port on the remote host computer or the connection attempt will not succeed. If you are unsure which port the remote host computer is listening to, contact the system administrator of the remote host.

User Name

Select Use current user name if the connection should always be made using the currently logged in Windows or Unix user name. This is similar to defining %USERNAME% (note the percent signs) as the user name.

Select Specify user name and enter the user name, if you want to define the user name to be used when connecting to the remote host computer. If you specify %USERNAME% (note the percent signs) as the user name, it will be replaced with the name of the current Windows or Unix user account upon connecting.


Not needed now: In Compression, select the desired compression setting from the drop-down menu. Valid choices are zlib and none. Compression is disabled by default.

Not needed now: In Tunnel using profile, select the desired connection profile from the drop-down menu. Any nested tunnels will be created through the profile. For information on the tunneling features, refer to Chapter 6.


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more