FTP Error 200: Command Okay
FTP reply code 200 is the general-purpose success response confirming that the server processed the command. It is used for commands that do not have a more specific success code — such as TYPE (setting transfer mode), MODE, STRU, PORT, NOOP, and SITE commands. Unlike 250 (which specifically confirms file/directory operations), 200 confirms protocol-level commands that configure the session. For example, TYPE I returns 200 to confirm binary transfer mode is set, and NOOP returns 200 to confirm the connection is still alive.
Status
200 Command OkayExample
220 ftp.example.com FTP server ready
USER alice
331 Password required
PASS ****
230 User alice logged in
TYPE I
200 Type set to I
NOOP
200 NOOP okHow to Troubleshoot
No troubleshooting needed
Code 200 is a success response. If you are receiving it, the command was executed correctly. Continue with the next command in your FTP workflow.
Verify transfer mode is correct
If files are being corrupted during transfer, check the TYPE response. Use TYPE I for binary files (images, archives, executables) and TYPE A only for plain text files.
curl -v ftp://ftp.example.com/ -Q 'TYPE I'
Common Causes
Transfer type set successfully
highThe client sent TYPE I (binary) or TYPE A (ASCII) and the server confirmed the transfer mode was set. This is issued before every file transfer to ensure the correct encoding.
NOOP keep-alive acknowledged
highThe client sent NOOP to prevent the server from timing out an idle connection. The server responds with 200 to confirm it is still alive and the connection is active.
PORT command accepted
mediumIn active mode, the client sends PORT to tell the server which IP and port to connect back to for data transfers. A 200 response confirms the server accepted the address.
SITE command executed
lowThe client sent a server-specific SITE command (such as SITE CHMOD to change permissions) and the server executed it successfully. SITE commands are vendor-specific extensions.
Related Error Codes
References
| Specification | Section |
|---|---|
| RFC 959 | RFC 959 §4.2 |
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.