Testing a User-Initiated Remote Transfer

Follow the steps below to test an incoming connection from a remote client machine to the Point-to-Point Client.


  1. On the client machine, verify your connection to Point-to-Point Client.
    Run a ping command from the Command Prompt window to verify connectivity to the host. In this example, the address of Point-to-Point Client is and the output shows successful responses from the host.
    > 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

    If the output returns "Destination host unreachable," check the firewall configuration of the server. For more information, see Clients Can't Establish Connection.

  2. On your client machine, initiate a transfer to Point-to-Point.
    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@ 

    This command specifies the following values for the transfer:

    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)
    • TCP port that is used to initiate the FASP session = 33001 (-P 33001). This command does not alter ascp or the configuration of your SSH server.
    • Disable encryption (-T)
    • Fair transfer policy (--policy=fair)

If you cannot establish a connection to Point-to-Point, see Clients Can't Establish Connection.