# Automating FTPS Transfer **URL:** \ **Category:** PittSpeed Off Topic\ **Created:** [June 26, 2008, 5:02am UTC](https://forums.speedlife.net/t/automating-ftps-transfer/198247 "2008-06-26T05:02:29Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Swarzkopf](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@Swarzkopf](https://forums.speedlife.net/u/Swarzkopf)\ **Post date:** [June 26, 2008, 2:39pm UTC](https://forums.speedlife.net/t/automating-ftps-transfer/198247/9 "2008-06-26T14:39:36Z")
> [@DSM shootout 2008](https://forums.speedlife.net/t/dsm-shootout-2008/34080/11): > > wow… i guess i wasn’t really reading what you were asking… i mean we ftp over ssl but use certs and ipsec to create the tunnel then rock and roll… i’m guessing that’s not possible in this scenario? is it internal to internal? internal / external? > > this sounds hokey… wtf is up? I guess i can’t speak on ftps vs. sftp because i just always use sftp, why can’t you(just curious)?.. i’m guessing it’s an antiquated platform? It’s external to internal- we’re retrieving files from a vendor who does some outsourced data cleansing for us. Believe me, if this were internal to internal or internal to external, I wouldn’t be jammed up like this with FTPS. The vendor will not allow any transfer protocol beside FTPS- why, I honestly can’t answer. I’ve tried to get them to use SFTP (like the rest of the world), I’ve tried to get them to let us create a VPN tunnel…but they insist on FTPS. They won’t give us port 22, won’t give us VPN, ect. I’m going to try a new FTPS package tommorow morning (“MoveITFreely”). I captured a bunch of packets while my transfer attempts were erroring out and it looks like the FTPS package I was using doesn’t support passive mode FTP with SSLv3, which was causing my issues. The new package does. I’ll report back with my results. --- _[View the full topic](https://forums.speedlife.net/t/automating-ftps-transfer/198247)._