Skip to content
My Docs

Ftp And File Transfer Protocols

Category: Transport and Application Layer Protocols
Type: Network Concepts
Generated on: 2025-07-10 08:56:52
For: Network Engineering, Administration & Technical Interviews

1. Quick Overview

Section titled “1. Quick Overview”

What is it? File Transfer Protocol (FTP) is a standard network protocol used to transfer files between a client and a server on a computer network. It operates over TCP and uses separate control and data connections.

Why is it important? FTP, and its secure variants, are essential for:

  • File Sharing: Distributing large files (software, documents, media).
  • Website Management: Uploading and downloading website files.
  • Backup and Recovery: Moving backups to remote servers.
  • Automation: Scripting file transfers for automated tasks.

2. Key Concepts

Section titled “2. Key Concepts”
  • Client-Server Model: FTP operates on a client-server model, where the client initiates a connection to the server.
  • Control Connection (Port 21): Used for commands and responses (authentication, navigation, etc.). Remains open during the entire session.
  • Data Connection (Port 20 or Dynamic): Used for the actual file transfer. Created and closed for each file transfer.
  • Active Mode: The client initiates the data connection to the server. The client tells the server which port it is listening on for data. Often problematic due to firewalls.
  • Passive Mode: The server initiates the data connection to the client. The server tells the client which port it is listening on for data. More firewall-friendly.
  • ASCII Mode: Transfers text files with character encoding conversion (e.g., handling line endings).
  • Binary Mode: Transfers files without any conversion, preserving the exact byte-for-byte content. Used for images, executables, etc.
  • Anonymous FTP: Allows users to access publicly available files without requiring a user account (typically using “anonymous” as the username and an email address as the password).
  • Implicit TLS (FTPS): Establishes a TLS/SSL encrypted connection from the very beginning (typically on port 990).
  • Explicit TLS (FTPES): Starts with an unencrypted connection and then negotiates TLS/SSL encryption using the AUTH TLS command.
  • SFTP (SSH File Transfer Protocol): A secure file transfer protocol that runs over SSH (Secure Shell). Not actually FTP, but often confused with it. Uses port 22.

3. How It Works

Section titled “3. How It Works”

Basic FTP Connection (Active Mode):

Client (Port X)  -------------------SYN-------------------> Server (Port 21)
Client (Port X)  <-------------------SYN-ACK------------------- Server (Port 21)
Client (Port X)  -------------------ACK-------------------> Server (Port 21)
Client (Port X)  -------------------FTP Commands (USER, PASS, PASV, LIST, RETR, STOR) -------------------> Server (Port 21)


Server (Port 21)  -------------------220, 230, 227, 150 responses-------------------> Client (Port X)


Client (Port Y)  -------------------SYN-------------------> Server (Port 20)  (Data Connection - Active mode)
Client (Port Y)  <-------------------SYN-ACK------------------- Server (Port 20)
Client (Port Y)  -------------------ACK-------------------> Server (Port 20)
Client (Port Y)  <-------------------Data------------------- Server (Port 20)

Basic FTP Connection (Passive Mode):

Client (Port X)  -------------------SYN-------------------> Server (Port 21)
Client (Port X)  <-------------------SYN-ACK------------------- Server (Port 21)
Client (Port X)  -------------------ACK-------------------> Server (Port 21)
Client (Port X)  -------------------FTP Commands (USER, PASS, PASV, LIST, RETR, STOR) -------------------> Server (Port 21)


Server (Port 21)  -------------------220, 230, 227 (PASV response with server data port)-------------------> Client (Port X)


Client (Port Z)  -------------------SYN-------------------> Server (Port N)  (Data Connection - Passive mode)
Client (Port Z)  <-------------------SYN-ACK------------------- Server (Port N)
Client (Port Z)  -------------------ACK-------------------> Server (Port N)
Client (Port Z)  <-------------------Data------------------- Server (Port N)

Explanation:

  1. The client initiates a TCP connection to the FTP server on port 21 (Control Connection).
  2. The client authenticates with username and password.
  3. For each file transfer, a separate data connection is established.
  4. In Active Mode, the server connects back to the client on a port specified by the client.
  5. In Passive Mode, the client connects to a port specified by the server. This is more common in modern networks due to firewall considerations.
  6. The file is transferred over the data connection.
  7. The data connection is closed after the transfer.
  8. The control connection remains open for subsequent commands.

4. Protocol Details

Section titled “4. Protocol Details”

FTP Commands (Examples):

CommandDescriptionExample
USERSpecifies the username.USER anonymous
PASSSpecifies the password.PASS user@example.com
PASVEnters passive mode.PASV
PORTSpecifies the port for the data connection (Active Mode).PORT 192,168,1,1,4,20
LISTLists files in the current directory.LIST
RETRRetrieves a file.RETR myfile.txt
STORStores a file on the server.STOR myfile.txt
CWDChanges the working directory.CWD /path/to/directory
PWDPrints the current working directory.PWD
QUITCloses the connection.QUIT
TYPESpecifies the transfer type (ASCII or Binary).TYPE A (ASCII), TYPE I (Binary)
AUTHSpecifies the authentication mechanism (e.g., TLS).AUTH TLS

FTP Response Codes (Examples):

CodeDescription
1xxPreliminary reply (rarely seen by the user)
2xxPositive completion reply (e.g., 220 Service ready, 230 User logged in)
3xxPositive intermediate reply (e.g., 331 User name okay, need password)
4xxTransient negative completion reply (e.g., 425 Can’t open data connection)
5xxPermanent negative completion reply (e.g., 530 Not logged in, 550 File not found)

Example FTP Session (Passive Mode - Snippet):

220 (vsFTPd 3.0.3)
USER testuser
331 Please specify the password.
PASS password
230 Login successful.
SYST
215 UNIX Type: L8
PWD
257 "/" is the current directory
PASV
227 Entering Passive Mode (192,168,1,10,195,120).  <-- Server IP and Port (195 * 256 + 120 = 50040)
LIST
150 Here comes the directory listing.
drwxr-xr-x    2 1000     1000         4096 Jul 27 14:32 testdir
-rw-r--r--    1 1000     1000            10 Jul 27 14:32 testfile.txt
226 Directory send OK.
QUIT
221 Goodbye.

5. Real-World Examples

Section titled “5. Real-World Examples”
  • Web Server Deployment: Developers use FTP clients (FileZilla, Cyberduck, WinSCP) to upload website files (HTML, CSS, JavaScript, images) to a web server.
  • Data Backup: Businesses automate FTP transfers to back up critical data to offsite servers. Often using lftp which has better automation capabilities.
  • Software Distribution: Software vendors use FTP servers to distribute software updates and patches to users.
  • Anonymous File Sharing: Universities and research institutions provide anonymous FTP servers for sharing public datasets and research papers.
  • Network Device Configuration Backup: Network engineers often use FTP to back up router and switch configurations to a central server.

6. Common Issues

Section titled “6. Common Issues”
  • Firewall Issues: Firewalls often block the data connections, especially in active mode. Solution: Use passive mode or configure the firewall to allow connections on the data port range.
  • Incorrect Credentials: Double-check username and password.
  • Incorrect File Permissions: Ensure the FTP user has the necessary permissions to read or write files.
  • Connection Timeout: Increase the timeout settings in the FTP client or server.
  • Data Corruption: Ensure the correct transfer mode (ASCII or Binary) is used.
  • Security Vulnerabilities: FTP is inherently insecure as it transmits data in cleartext. Solution: Use SFTP or FTPS.
  • Passive Mode Configuration: The FTP server must be configured to allow passive mode connections, and the firewall must allow connections on the passive port range.
  • NAT Issues: Network Address Translation (NAT) can cause problems with active mode FTP. Passive mode is generally preferred.

Troubleshooting Commands:

  • netstat -an | grep 21: Check if the FTP server is listening on port 21.
  • tcpdump -i eth0 port 21 or port 20: Capture FTP traffic to analyze the communication (replace eth0 with your network interface). For passive mode, capture traffic on the passive port range specified by the server.
  • traceroute <ftp_server>: Trace the route to the FTP server to identify any network connectivity issues.

7. Configuration Examples

Section titled “7. Configuration Examples”

vsftpd (Very Secure FTP Daemon) Configuration (Linux):

/etc/vsftpd.conf (Example):

listen=YES
anonymous_enable=NO
local_enable=YES
write_enable=YES
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=NO  # Use passive mode
xferlog_file=/var/log/vsftpd.log
xferlog_std_format=YES
chroot_local_user=YES      # Restrict users to their home directory
listen_address=192.168.1.10 # Listen on a specific IP address
pasv_min_port=50000       # Passive port range
pasv_max_port=50100
rsa_cert_file=/etc/ssl/certs/vsftpd.pem  # For FTPS
ssl_enable=YES  #Enable SSL
force_local_data_ssl=YES
force_local_logins_ssl=YES

Firewall Configuration (iptables - Linux):

Terminal window
# Allow FTP control connection
iptables -A INPUT -p tcp --dport 21 -j ACCEPT


# Allow FTP passive data connections (example port range)
iptables -A INPUT -p tcp --dport 50000:50100 -j ACCEPT


# Allow established connections
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

FileZilla (FTP Client) - Setting Passive Mode:

  1. Go to “Edit” -> “Settings”.
  2. Navigate to “Connection” -> “FTP” -> “Passive Mode”.
  3. Select “Use the server’s external IP address instead”. Or “Default” if the server is on the same network.

LFTP (Command Line FTP Client):

Terminal window
lftp ftp://user:password@ftp.example.com
lftp> ls
lftp> cd /path/to/directory
lftp> get filename.txt
lftp> put localfile.txt
lftp> mirror -R localdir remotedir  #Recursive download
lftp> bye

8. Interview Questions

Section titled “8. Interview Questions”

Q: What is FTP and how does it work?

A: FTP is a standard network protocol used to transfer files between a client and a server. It uses two TCP connections: a control connection (port 21) for commands and responses, and a data connection (port 20 in active mode or dynamically assigned in passive mode) for the actual file transfer. The client initiates the control connection, authenticates, and then uses commands like LIST, RETR, and STOR to manage files.

Q: Explain the difference between Active and Passive FTP modes.

A: In Active Mode, the client tells the server its IP address and a port number to use for the data connection. The server then initiates a connection to the client on that port. This can be problematic with firewalls. In Passive Mode, the client requests a port from the server, and the server responds with a port number. The client then initiates the data connection to the server on that port. Passive mode is generally more firewall-friendly.

Q: What are the security concerns with FTP and how can they be addressed?

A: FTP transmits data, including usernames and passwords, in cleartext, making it vulnerable to eavesdropping and man-in-the-middle attacks. To address these concerns, use secure alternatives like:

  • FTPS (FTP over SSL/TLS): Encrypts the control and data connections using SSL/TLS.
  • SFTP (SSH File Transfer Protocol): Transfers files over an SSH connection, providing encryption and authentication.

Q: What is the difference between FTPS and SFTP?

A: FTPS is FTP with added SSL/TLS encryption. It’s still based on the FTP protocol but adds a layer of security. SFTP, on the other hand, is a completely different protocol that runs over SSH. SFTP is generally considered more secure and easier to configure than FTPS. SFTP uses a single port (22) for both control and data, simplifying firewall configuration.

Q: How do you troubleshoot FTP connection problems?

A: Troubleshooting steps include:

  • Verify network connectivity: Ping the FTP server.
  • Check firewall rules: Ensure that ports 21 (control) and the data port range (for passive mode) are open.
  • Check FTP server configuration: Verify that the server is running and configured correctly (e.g., passive mode settings).
  • Verify credentials: Double-check the username and password.
  • Use a packet sniffer (e.g., Wireshark): Capture FTP traffic to analyze the communication and identify any errors.
  • Check FTP logs: Examine the FTP server logs for error messages.
  • Try different FTP clients or modes (active/passive): Rule out client-specific issues.
  • Check for NAT issues: If behind NAT, ensure the FTP server is configured for passive mode and the NAT device is correctly configured.

Q: What is the purpose of the TYPE command in FTP?

A: The TYPE command specifies the type of data being transferred. TYPE A indicates ASCII mode, which is used for text files and performs character encoding conversion. TYPE I indicates binary mode, which is used for all other file types (images, executables, etc.) and transfers the data byte-for-byte without any conversion.

Section titled “9. Related Concepts”
  • TCP/IP Protocol Suite: FTP relies on TCP for reliable data transfer.
  • SSL/TLS: Used by FTPS to encrypt the communication.
  • SSH: Used by SFTP to establish a secure connection.
  • Network Address Translation (NAT): Can affect FTP connections, especially in active mode.
  • Firewalls: Need to be configured to allow FTP traffic.
  • Packet Sniffing (Wireshark): Useful for analyzing FTP traffic and troubleshooting issues.
  • SCP (Secure Copy): Another secure file transfer protocol based on SSH.

Further Reading: