Testing a User-Initiated Remote Transfer

Follow the steps below to test your server's incoming connections from a client machine.

Important: These instructions require you to take steps on both the Enterprise Server and a client computer. Ensure that you are performing the task on the indicated machine. As a prerequisite, Enterprise Server must have at least one transfer user. For instructions on adding a transfer user, see Setting up Users.
  1. On your client machine, verify your connection to Enterprise Server.
    On the client machine, use the ping command from the Command Prompt window to verify connectivity to the host. In this example, the address of Enterprise Server is
    > ping
    PING ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=64 time=8.432 ms
    64 bytes from icmp_seq=1 ttl=64 time=7.121 ms
    64 bytes from icmp_seq=2 ttl=64 time=5.116 ms
    64 bytes from icmp_seq=3 ttl=64 time=4.421 ms
    64 bytes from icmp_seq=4 ttl=64 time=3.050 ms
  2. On your client machine, initiate a transfer to Enterprise Server.
    Attempt to establish a connection from your client machine to Enterprise Server. To do so, run the following command on your client machine (where aspera_user_1 is the example transfer user):
    > ascp -P 33001 -T --policy=fair -l 10000 -m 1000 /client-dir/files aspera_user_1@ 
    Item Value
    Host Address
    Transfer User aspera_user_1
    Files to upload /client-dir/files
    Destination Folder {user's docroot}/dir
    Transfer Options
    • Maximum transfer rate = 10 Mbps (-l 10000)
    • Minimum transfer rate = 1 Mbps (-m 1000)
    • Change default TCP port used for FASP session initiation = 33001 (-P 33001). Please note that this command does not alter ascp or your SSH server's configuration.
    • Disable encryption (-T)
    • Fair transfer policy (--policy=fair)

If you cannot establish a connection to Enterprise Server, see Clients Cannot Establish Connection.