Reply Code

Typical Reply Text

Description

110

Restart marker reply.

Used as part of the marker restart feature when transferring in block mode.

120

Service ready in “nnn” minutes.

“nnn” indicates the number of minutes until the service will be available.

125

Data connection already open; transfer starting.

150

File status okay; about to open data connection.

200

Command okay.

Sometimes the text indicates the name of the command that was successful.

202

Command not implemented, or superfluous at this site.

211

System status, or system help reply.

Will contain system-specific status or help information.

212

Directory status.

213

File status.

214

Help message.

Includes help information of use to a human user of this server.

215

“NAME” system type.

“NAME” is the name of a type of operating system. Often sent as a reply to the SYST command.

220

Service ready for new user.

Sent when the command channel is established before the USER command is sent.

221

Service closing control connection.

A “goodbye” message sent when the session is closed.

225

Data connection open; no transfer in progress.

226

Closing data connection.

Sent after a successful file transfer or a file abort.

227

Entering Passive Mode (h1,h2,h3,h4,p1,p2).

Sent in reply to the PASV command, indicates the IP address and port to use for the data connection.

230

User logged in, proceed.

Sent after successful USER and PASS authentication. Systems often include additional “greeting” or other information with this code after a login.

250

Requested file action okay, completed.

The text description will provide more details about what was successfully done, such as confirming a change of directory or deleted file.

257

“PATHNAME” created.

“PATHNAME” is replaced by the path created.

331

User name okay, need password.

Intermediate result after sending USER but before sending PASS.

332

Need account for login.

350

Requested file action pending further information.

421

Service not available, closing control connection.

Sometimes sent if the FTP server is in the process of shutting down.

425

Can't open data connection.

426

Connection closed; transfer aborted.

450

Requested file action not taken. File unavailable.

The file is not available; for example, it may be locked by another user. Contrast to reply code 550.

451

Requested action aborted: local error in processing.

452

Requested action not taken. Insufficient storage space in system.

The file system is full.

500

Syntax error, command unrecognized.

Bad or excessively long command line was sent.

501

Syntax error in parameters or arguments.

502

Command not implemented.

503

Bad sequence of commands.

504

Command not implemented for that parameter.

530

Not logged in.

Sent if authentication fails due to a bad user name or incorrect password.

550

Requested action not taken. File unavailable.

File was not found or user does not have access to it. This error code may be sent in reply to any file transfer command if the user has not successfully logged in yet. Contrast to reply code 450.

551

Requested action aborted: page type unknown.

552

Requested file action aborted. Exceeded storage allocation.

553

Requested action not taken. File name not allowed.