The Ultimate FTP Command List

best ftp command list | | FTP

Looking for a one-stop place for FTP commands? Look no further. This list of FTP commands should help you if you’re responsible for the day-to-day management of your FTP server, or if you have to batch files to your FTP server.

Included are both FTP commands and the FTP command line. If you’re interested in a printer friendly version to hang by your desk (so you don’t need to keep coming here!) or a way to share it with your colleagues, just click here and we’ll send it over to you!

By the way, we know this isn’t a complete list, but if there are any additional FTP commands you think should be added to this FTP command list, please let us know by leaving a comment! Continue reading

The Big List of FTP Server Response Codes

ftp server codes | | FTP

FTP server response codes are helpful for system administrators in charge of their company’s FTP server. Often times, users might see these response codes listed in their favorite FTP client, such as FileZilla.

When troubleshooting a file transfer problem, it’s often helpful to identify the FTP response code that is being thrown around. It’s also important to ask what time of connection they’re using (ie FTP, SFTP, FTPS, etc…).

This guide will help you understand each element of the FTP server response code so you can better understand what’s happening. It will also give you a full listing of each error code.

FTP Server Response Codes: The First Digit

The first digit in the FTP server code lets you know whether or not the that step was successful. They also tell you what you should expect next. For instance, a 100 level code tells you that the process has started and to expect another code shortly.

Range Purpose

Positive Preliminary Reply

The request is being initiated and you should expect another reply before proceeding with a new command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command.


Positive Completion Reply

The request was successfully completed. A new request may now be initiated.


Positive Intermediate Reply

The command was accepted, but the request is being held in abeyance, pending receipt of further information. The user should send another command specifying this information. This reply is used in command sequence groups.


Transient Negative Completion Reply

The command wasn’t accepted and the request didn’t occur, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to “transient”, particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.)


Permanent Negative Completion Reply

The command wasn’t accepted and the requested action didn’t occur. The User-process is discouraged from repeating the exact request (in the same sequence). Even some “permanent” error conditions can be corrected, so the human user may want to direct his User-process to reinitiate the command sequence by direct action at some point in the future (e.g., after the spelling was changed, or the user has altered his directory status.)


Protected Reply

The RFC 2228 introduced the concept of protected replies to increase security over the FTP communications. The 6xx replies are Base64 encoded protected messages that serves as responses to secure commands. When properly decoded, these replies fall into the above categories.

FTP Response Codes: The Second Digit

The second digit in the FTP server code lets you know what group or category the request belongs too. For instance, it tells you if it’s regarding connections or if it’s regarding authentication.

Range Purpose


These replies refer to syntax errors, syntactically correct commands that don’t fit any functional category, unimplemented or superfluous commands.



These are replies to requests for information, like help or support.



Replies regarding the control and data connections.


Authentication and accounting

Replies for the login process and accounting procedures.


Unspecified as of RFC 959.


File system

Indicates the status of the Server file system vis-a-vis the requested transfer or other file system action.

FTP Server Codes: The Third Digit

The third digit in the FTP serve code gives further explanation on what exactly is causing this code. Usually it’s the final piece of the puzzle.

Looking For a User-Friendly FTP Alternative?
Get our guide to a more secure and easier-to-use FTP replacement:
Get the Guide

FTP Server Codes: List of Error Codes

Here is a full list of known FTP server error codes:

Code Explanation
100 Series

The request is being initiated, expect another reply before proceeding with a new command.


Restart marker replay. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server’s equivalent marker (note the spaces between markers and “=”).


Service ready in xxx minutes.


Data connection already open; transfer starting.


File status okay; about to open data connection.

200 Series

The request was successfully completed.


Command not implemented, superfluous at this site.


System status, or system help reply.


Directory status.


File status.


Help message.On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.


NAME system type. Where NAME is an official system name from the registry kept by IANA.


Service ready for new user.


Service closing control connection.


Data connection open; no transfer in progress.


Closing data connection. Requested file action successful (for example, file transfer or file abort).


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


Entering Long Passive Mode (long address, port).


Entering Extended Passive Mode (|||port|).


User logged in, proceed. Logged out if appropriate.


User logged out; service terminated.


Logout command noted, will complete when transfer done.


Specifies that the server accepts the authentication mechanism specified by the client, and the exchange of security data is complete. A higher level nonstandard code created by Microsoft.


Requested file action okay, completed.


“PATHNAME” created.

300 Series

The command was accepted, but the request is on hold, pending receipt of further information.


User name okay, need password.


Need account for login.


Requested file action pending further information

400 Series

The command wasn’t accepted and the requested action didn’t occur, but the error condition is temporary and the action may be requested again.


Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.


Can’t open data connection.


Connection closed; transfer aborted.


Invalid username or password.


Requested host unavailable.


Requested file action not taken.


Requested action aborted. Local error in processing.


Requested action not taken. Insufficient storage space in system.File unavailable (e.g., file busy).

500 Series

Syntax error, command unrecognized and the request did not take place. This may include errors such as command line too long.


Syntax error in parameters or arguments.


Command not implemented.


Bad sequence of commands.


Command not implemented for that parameter.


Not logged in.


Need account for storing files.


Request not taken. File unavailable (e.g., file not found, no access).


Request aborted. Page type unknown.


Requested file action aborted. Exceeded storage allocation (for current directory or dataset).


Requested action not taken. File name not allowed.

600 Series

Replies regarding confidentiality and integrity


Integrity protected reply.


Confidentiality and integrity protected reply.


Confidentiality protected reply.

10000 Series

Common Winsock Error Codes


Connection reset by peer. The connection was forcibly closed by the remote host.


Cannot connect to remote server.


Cannot connect to remote server. The connection is actively refused by the server.


Directory not empty.


Too many users, server is full.

Looking for an FTP Alternative? Get Our Full Guide!

Get Your Guide

  Learn the 5 Ways FTP Fails You (Security, Scripting, etc…)
  Identify Things to Look for in an FTP Alternative (Accessibility, Scalability, etc…)
  Discover Available Alternatives that Make Your Job Easier

Sources: SmartFile’s I.T. Personnel, Wikipedia

Designing Awesome IT Dashboards

it dashboards | | Industry Thoughts

Dashboards are powerful visual tools that help various aspects of your business identify key performance indicators (KPIs), outlying data points, uptime and downtime, and other various goals. Creating an IT dashboard can be helpful for your day-to-day business and for long-term strategy.

When creating your dashboard, there are a few things to keep in mind. Audience, actionable metrics, and readability. These 3 factors are important when creating any IT dashboard. Continue reading

New Visualization and Trending Tools

SmartFile new visualization and trending tool released feature | | SmartFile News

SmartFile has added new visualization and trending tools for our Enterprise customers. This feature release helps account administrators visualize and monitor audit trails, such as successful and failed login attempts, trending network file activity and all other SmartFile audit data points.

This new tool gives administrators new ways to monitor and ensure compliance. They can view past and real time audit data, enabling them to quickly identify unusual behaviors and outlying events.

The view can be filtered down to look at the user’s IP address or specific usernames to see the actions that were performed. Administrators can use this to see exactly when breach activities are occurring and what accounts are targeted.

With the new visualization and trending tool, reports and data can also be exported for additional business analysis through 3rd party tools.

Here’s a closer look at the new visualization tool: Continue reading

6 Hidden Costs During the Outsourcing Transition Period

hidden costs of it outsourcing | | Industry Thoughts

With every project, there are hidden costs we didn’t expect. With 542,000 IT jobs moving overseas in 2015 (Source), there will be a lot of hidden outsourcing costs not anticipated by CIO’s. One major area that get’s underestimated is outsourcing transition costs.

What are outsourcing transition costs? They occur during your transition period, usually 3-12 months after you’ve agreed to outsource. They aren’t contract related, and many are opportunity costs.

There are 6 key areas during the transition period that can blow up your budget. During this period of the outsourcing processes, you should not expect to save money. In fact, you’re going to incur heavy expenses. Per, you should expect at least 2 – 3% of your signed agreement costs to occur during this transition period.

Here are the 6 areas you need to make sure you factor appropriately when budget time comes around… Continue reading

Is the XY Problem Giving You a Shellacking?

xy problem | | Industry Thoughts

The XY Problem is an issue for every organization — caused by poorly executed problem solving techniques. A person is trying to accomplish X, and they come up with a workaround using Y solution. Little did this person know, the original problem could be solved with relative ease — but figuring out their own solution is more difficult or less accurate.

The XY Problem gives I.T. departments a shellacking because you waste time solving the wrong issue. Usually it takes way longer to solve Y than it does to solve the original problem.

This article will show you how the XY problem can cause issues for an entire business proposition, which would cause major IT headaches (aka, get out of Dodge now!). It will also illustrate the XY Problem as a departmental issue. Finally, I’ll show you a few ways to identify if you’re dealing with an XY Problem. Continue reading