Thank you all for your answers. Finally, the problem is linked to security settings.
My previous laptop was using a simple userid/password credentials to login to my work account and same for the login on SSIS and SSMS. The new laptop requires a Kerberos double-hop authentication when SSIS and SSMS still require a single userid/password login. Therefore, when I try to execute a package in SSMS, the package is executed on my behalf by the server and the resources on the network cannot be reached.
The only solution is to create jobs with SQL Server Agent and a proxy.
Hope this will help others as well.