All FTP replies consist of three-digit numbers with an optional text message following the number. Each of the three-digit numbers has special significance.
The NV4IP FTP Error Log displays all reply codes where 250 = UNTRUE.
There are five values for the first digit of the reply code. "1-3" in the first digit indicates the three function groupings of Positive replies. "4-5" in the first digit indicates the two groupings of Negative replies (errors).
The value for the first digit in the reply code (1-5) indicates the following:
1 |
Positive Preliminary Reply. The requested action is being initiated and you should expect another reply before proceeding with a new command. |
2 |
Positive Completion Reply. The requested action has been successfully completed and you can enter a new command. The command has been accepted, but the requested action is being held in abeyance pending receipt of further information. You should send another command specifying this information. |
3 |
Positive Intermediate Reply. |
4 |
Transient Negative Completion Reply. This is a temporary error condition. You should attempt to enter the command again. |
5 |
Permanent Negative Completion Reply. The command was neither accepted nor executed. You should not attempt to enter the same command again (in the same sequence). |
The value for the second digit in the reply code (0-5) indicates the following:
0 |
Syntax |
1 |
Information |
2 |
Connections |
3 |
Authentication and Accounting |
4 |
An unspecified value |
5 |
File System |
The value for the third digit in the reply code provides a finer gradation of meaning in each of the function categories specified by the second digit.
The following list displays typical error codes in numeric order, with message strings following each number. The message string associated with each reply may be server-dependent, so it is likely to vary for each reply code. The reply code itself, however, must strictly follow the specifications described in this section.
Error Code |
Message String |
110 |
Restart marker reply. In this case,
the text is exact and not left to the particular implementation; it must
read: |
120 |
Service ready in nnn minutes. |
125 |
Data connection already open; transfer starting. |
150 |
File status okay; about to open data connection. |
200 |
Command okay. |
202 |
Command not implemented, superfluous at this site. |
211 |
System status, or system help reply. |
212 |
Directory status. |
213 |
File status. |
214 |
Help message |
215 |
NAME system
type. |
220 |
Service ready for new user. |
221 |
Service closing control connection. |
225 |
Data connection open; no transfer in progress. |
226 |
Closing data connection. |
227 |
Entering passive Mode (h1, h2, h3, h4, pl, p2). |
230 |
User logged in, proceed. |
250 |
Requested file action okay, completed. |
257 |
"PATHNAME" created. |
331 |
User name okay, need password. |
332 |
Need account for login. |
350 |
Requested file action pending further information. |
421 |
Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down. |
425 |
Can't open data connection. |
426 |
Connection closed; transfer aborted. |
450 |
Requested file action not taken. File unavailable (e.g., file busy). |
451 |
Requested action aborted: local error in processing. |
452 |
Requested
action not taken. |
500 |
Syntax error, command unrecognized. This may include errors such as command line too long. |
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. |
532 |
Need account for storing files. |
550 |
Requested action not taken. |
551 |
Requested action aborted: page type unknown. |
552 |
Requested file action aborted. |
553 |
Requested action not taken. |