Custom Server Ports

In the SSH Collection Module, you can set an alternate TCP port for a given credential entry. The SSH protocol uses TCP port 22 as a standard, however some environments may run SSH servers on alternate ports. The TCP port selected when entering a credential is localized to that specific credential entry. Be aware, however, that when an alternate port is provided as a component of an SSH credential entry, that TCP port will be included in the discovery process, and that port will be checked for every IP address that responds during the ICMP portion of discovery to determine if that IP address supports SSH. If a device is found to have that TCP port open, then the device will be considered to support SSH.

Custom SSH ports provided for SSH credentials must meet a set of criteria to be accepted as a valid credential. To meet these criteria, a port must be numeric, within the range of valid TCP ports (1 - 65535), and not conflict with the standard ports utilized by other collection protocols. The following ports, and their related protocols, are not considered valid SSH ports: 80 (HTTP), 443 (HTTPS), 135 (WMI), 161 (SNMP), 62078 (iphone-sync).

Because user-supplied port numbers are automatically added to the list of ports used during the discovery process, a limitation on the number of unique custom ports is enforced. The credential configuration interface will produce an error indicating this limit if it is reached. The limit reflects the count of unique port numbers across all credential entries, not the number of credential entries using custom ports. When modifying the port on an existing credential, the new port number must also satisfy the custom port count limitation.

If a credential entry with a custom SSH port is removed, and the associated port number is not present on another credential entry that has not been removed, then the port will not be included in the discovery process and will not count towards the custom port count limitation.