I have a Client, running on Server A, which executes a SSIS package which is located on Server B. This SSIS package process a SSAS Tabular Cube which is located on Server C. The connection from A to B works fine. However, the connection from B to C fails with the error "A connection cannot be made. Ensure that the server is running". The Connection from B to C is via Windows Authentication, the Servver is running and permissions are fine.
When I execute the deployed SSIS package directly on Server B then it works. When I execute the deployed SSIS package over SSMS on Server A then doesn't work. The user is the same on every server on which the services are running.
It was a "double hop kerberos" issue. I solved it by creating a SQl Server Agent Job which executes the SSIS Package. The client then starts the Agent Job.
Thanks @billinkc for the comment.