I have a problem when trying to run a SSIS package on a remote computer. Let's say I have two computers 188.8.131.52 and 184.108.40.206
My SQL server instance is on 220.127.116.11 and there is a firewall opening on 18.104.22.168 to an external machine. The SSIS package extracts files from the db, places them on 22.214.171.124 then opens WinSCP to ftp those files to the external machine.
The SSIS package is on \\126.96.36.199\d$\somefolder\ssispackage.dtsx
When I run the package on 188.8.131.52 there is no problem with database connectivity or FTP connectivity, however when I set the package to run through the SQL Server Agent and connect to the above file I am told that it can't find WinSCP.
What I am taking this to mean is that 184.108.40.206 is running the SSIS package it finds on 220.127.116.11, but because WinSCP doesn't exist on 18.104.22.168 it is falling over. While I can install WinSCP on 22.214.171.124 to get this to work it would be pointless because the firewall is closed here.
How can I run the package on 126.96.36.199, but ensure that it is 188.8.131.52 that is running the package?