| Standard Installation | |
Firewall settings required by the product.
Your Aspera transfer product requires access through the ports listed in the table below. If you cannot establish the connection, review your local corporate firewall settings and remove the port restrictions accordingly.
| Product | Firewall Configuration |
|---|---|
| Enterprise Server | An Aspera server runs one SSH server on a configurable TCP port (33001 by default). Important:
Aspera strongly recommends running the SSH server
on a non-default port to ensure that your server remains secure from SSH
port scan attacks. Please refer to the topic Securing your SSH Server for detailed instructions on changing your
SSH port.
Your firewall should be configured as follows:
The firewall on the server side must allow the open TCP port to reach the Aspera server. Note that no servers are listening on UDP ports. When a transfer is initiated by an Aspera client, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port over which the data transfer will occur. For Aspera servers that have multiple concurrent clients, the Windows operating system does not allow the Aspera fasp protocol to reuse the same UDP port for multiple connections. Thus, if you have multiple concurrent clients and your Aspera server runs on Windows, then you must allow inbound connections on a range of UDP ports, where the range of ports is equal to the maximum number of concurrent fasp transfers expected. These UDP ports should be opened incrementally from the base port, which is UDP/33001, by default. For example, to allow 10 concurrent fasp transfers, allow inbound traffic from UDP/33001 to UDP/33010. |
| Connect Server | An Aspera server runs one SSH server on a configurable TCP port (33001 by default). Important:
Aspera strongly recommends running the SSH server
on a non-default port to ensure that your server remains secure from SSH
port scan attacks. Please refer to the topic Securing your SSH Server for detailed instructions on changing your
SSH port.
Your firewall should be configured as follows:
The firewall on the server side must allow the open TCP port to reach the Aspera server. Note that no servers are listening on UDP ports. When a transfer is initiated by an Aspera client, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port over which the data transfer will occur. For Aspera servers that have multiple concurrent clients, the Windows operating system does not allow the Aspera fasp protocol to reuse the same UDP port for multiple connections. Thus, if you have multiple concurrent clients and your Aspera server runs on Windows, then you must allow inbound connections on a range of UDP ports, where the range of ports is equal to the maximum number of concurrent fasp transfers expected. These UDP ports should be opened incrementally from the base port, which is UDP/33001, by default. For example, to allow 10 concurrent fasp transfers, allow inbound traffic from UDP/33001 to UDP/33010. |
| Client | The following bullet points provide basic information for configuring your
firewall to allow Aspera file transfers. Note that the outbound connection for
SSH may differ based on your organization's unique network settings. Although
TCP/22 is the default setting, please refer to your IT Department for questions
related to which SSH port(s) are open for file transfer. Please also consult
your specific Operating System's help documentation for specific instructions on
configuring your firewall. If your client host is behind a firewall that does
not allow outbound connections, you will need to allow the following:
|