This tutorial is for those who 1) understand the vulnerabilities of FTP but still want to learn how it's used AND 2) prefer doing things on the FTP command line.

Overview

[Last updated: December 2020] Malicious insiders and careless insiders are increasingly posing serious risks to file transfer systems. If nothing is done to mitigate them, these internal threats can cause data loss or, worse, massive penalty-inducing data breaches. In this post, we take a closer look at internal threats, how they put file transfer systems at risk, and what you can do to mitigate them.

Overview

Are you receiving corrupt files during FTP transfers? It might simply be ,=to an incorrect data type setting. In this post, we help you understand the nuances and differences between FTP binary and ASCII data types (transfer modes) so you can avoid these issues.

Overview

Last time, we tackled the problem system administrators encounter when their passive FTP or FTPS connections have to pass through a NAT firewall or router. A similar problem can happen when you're dealing with the same type of connections and a reverse proxy. It gets even more complicated when you have to deal with both external and internal users. Let me show you how to deal with that.

It’s never easy to set up an FTP server the moment firewalls get involved. But it gets even more difficult once you start using the secure version of FTP, known as FTPS. In this post, we’ll talk about the problem you’ll usually encounter when your FTPS server is behind a firewall and your client is attempting to perform a file transfer using passive mode or PASV.

EPSV is a command issued by an FTP/S client to signal the server that it wishes to enter into what is known as Extended Passive Mode. But what is Extended Passive Mode and when is it appropriate to use EPSV? Let’s find out.

Overview

As explained in the first section of the article Preparing Trading Partner Servers For SFTP Automation, the process of establishing an automated file transfer can be greatly simplified by employing what is known as a trading partner. In this post, we'll teach you how to set up a trading partner designed for automated FTP/S transmissions. What you'll be able construct by the end of this tutorial can then be used for a variety of automated FTP/S-based transactions.

Overview

There will be times when you'll want to transfer files over a secure connection. One option is to use FTPS (FTP over SSL) which provides data-in-motion encryption through SSL (Secure Sockets Layer). When you setup an FTPS service in JSCAPE MFT Server, you'll notice that you actually have 3 modes to choose from explicit SSL, forced explicit SSL and implicit SSL.

This post was originally published on May 6, 2012 but was updated and republished on November 4, 2018.

Overview

Sending someone multi-megabyte or even gigabyte-sized files is getting more common these days. For example, in our Help Desk, it's normal to receive a zip file of log data of over 100MB. While it might seem this is just a highly specialized case that's only common in the tech business, it's not.

A single high resolution image can already run up to a few megabytes, while a regular video can easily exceed 50MB.We often use videos and images in our Power Point presentations and other files, so media file attachments of these types can be pretty common.

The problem is, people often resort to solutions that aren't suitable for sending large files, especially in an enterprise environment. Email, which is the most common way of sending files, is not a suitable big file transfer method for this. So are other methods many people unwisely use at work for sharing really big files; files that are even much larger than a gigabyte.

Overview

In one of my previous posts, I defined what an SSL file transfer is. Today, I'm going to show you how to actually set up an SSL file transfer service on JSCAPE MFT Server. After that, I'll demonstrate how an AnyClient user would connect to your server and perform a secure file transfer using that particular service.