Home › Topics › The FTP Protocol

The FTP Protocol, Understood Properly

FTP is one of the oldest protocols still in daily production use, and it behaves unlike almost everything designed since. Most famously, it splits every session into a control connection and a separate data connection. That design explains both FTP's flexibility and nearly every headache it causes behind modern firewalls.

These articles take the protocol apart properly. They cover what travels over each connection, how to read the command conversation, and how FTP accounts and anonymous access work. They also cover how to build a safe lab where you can watch it all happen. If you administer anything that still speaks FTP — and almost every organization has something — this is the foundation series.

Articles in This Series

The Two-Channel Architecture: FTP's Control and Data Connections
Why FTP uses separate connections, walked through with an annotated capture.
FTP Commands and Reply Codes: Reading the Conversation Like a Pro
The command set and the three-digit reply system, decoded for troubleshooting.
A Short History of FTP and Why It Refuses to Die
Where FTP came from, where it survives, and an honest risk framing.
FTP's Failure Modes: The Complete Field Guide
Mode mismatches, NAT breakage, timeouts, encoding corruption — symptom to fix.
FTP Account Models: Anonymous, Real Users, Virtual Users, and Isolation
How each model works and why virtual users became the standard.
Building an FTP Lab for Learning and Troubleshooting
A disposable server, client, and capture setup for safe experiments.
Reading the FTP Automation You Inherited
Decoding scripts from admins past — and finding the embedded credentials.
How to Set Up an FTP Server on Windows - Install and Configure
This article is the hands-on setup guide. It covers the decisions to make first, installing the FTP service built into Windows or a dedicated server, users and home folders, the passive range and firewall rules, the host name, and how to connect and test from outside.
How to Connect to an FTP Server and Test FTP, FTPS and SFTP
This article is the client-side guide. It covers the five things every connection needs, how to connect to an FTP, FTPS, or SFTP server from Windows, why browsers no longer open FTP sites, a four-step test sequence, and what each error message means.
FTP on Windows - File Explorer, Command Line, Mapped Drive
This article covers every built-in way to use FTP on Windows: File Explorer, mapping a site as a network location, the old ftp command and its limits, curl and sftp for encrypted transfers, and the FTP server feature, with a cheat sheet to keep.

Frequently Asked Questions

What is an FTP server?

A program that listens on port 21, authenticates clients, and moves files to and from a directory tree using the File Transfer Protocol. Every session is two connections: a control connection for logins and commands, and a data connection for each file or listing. Modern FTP servers also speak FTPS, the encrypted form, and most Windows server products bundle SFTP and HTTPS as well.

How does an FTP server work?

The client connects to port 21 and logs in over the control connection. For each transfer or listing the two sides negotiate a second, short-lived data connection using PORT or PASV, the file crosses that connection, and the server confirms completion with a reply code such as 226. The articles in this series follow a real session in a packet capture and explain the account models, reply codes and classic failure modes.

Is FTP still used, and is it safe?

Plain FTP is still common because devices and legacy jobs depend on it, but it sends passwords and files unencrypted, so it is not safe on any network you do not fully control. The practical path is FTPS or SFTP for anything that leaves the building, with plain FTP confined to the lab or retired; the retiring-plain-FTP series covers how.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.