Thank you. You are quite right; had to hand type it off a photo and it is indeed .io.
And you are correct; it’s DNS related as I just tried switching to 8.8.8.8 & 8.8.4.4 and that got me past the error on the machine where it would not even start the download yesterday. Too late for today but this is great going forward.
Thank you again.
Original Message:
Sent: 11/21/2024 11:45:00 AM
From: Laurent Martin
Subject: RE: Aspera Connect Error
Hi,
The error message means that your laptop was not able to resolve the DNS name specified.
ats-aws-us-east-1.aspera.id is not an existing DNS name
Correct one is: ats-aws-us-east-1.aspera.io (with a O at the end, not D)
You can check in a browser by adding https:// in front, and /ping at the end : it shall be a plank page for that transfer server.
It seems you are using Aspera on Cloud, and that address (with o) is the address of a transfer cluster in AWS in US where the data is actually located.
The "begin test" in https://test-connect.ibmaspera.com/ starts a transfer on connect using a demo server.
For the transfer to work, the server must be accessible through IP and the TSP/UDP ports 33001 as well from your laptop.
Also, make sur you do not overdrive your network by adjusting the "target rate" in the Connect client around the actual bandwidth available.
------------------------------
Laurent Martin
------------------------------
Original Message:
Sent: Thu November 21, 2024 04:17 AM
From: Steve Kraus
Subject: Aspera Connect Error
A client was having me download a 236G group of files (a DCP) via Aspera Connect. I installed the software, added the browser extension, and began the download. It would take 6 hrs (my internet is not too swift). It was working, chugging right along. 5.5 hours in, 207G downloaded, with victory in sight, it stops with the error message
Cannot resolve target host='ats-aws-us-east-1.aspera.id'
I've been unable to get passed this. I've attempted to do this download both at my business and at home. At the business I was getting that error at the outset. But at home things looked promising. Both machines are PCs running W10. I was using Firefox but have also tried Chrome (with the extension added there as well). FWIW the internet connection is Comcast at both locations. I don't know if this is some sort of DNS issue but it's puzzling it would get as far as it did and just stop.
Under troubleshooting, it says Connect is compatible with the browser but I have not done the transfer test. Clicking on it produces this result but the box continues to say "Loading" if that means anything.
SYSTEM
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0
DIAGNOSTICS
Connect version: 4.2.12.780
Connect status: RUNNING
Compatible with browser: YES
Detected extension: YES
FIREWALL TEST
Result: loading
Ports: TCP 33001/UDP 33001
------------------------------
Steve Kraus
------------------------------