Check FTP logs

The Site FTP log
When you connect to a server using Dreamweaver's FTP feature, Dreamweaver generates an FTP log. This log lists the transactions that occurred between Dreamweaver and the server during the connection. To explain the transactions, the log displays line-by-line standard codes and commands.

Many FTP problems can be identified by reading the codes and commands in this log. Below you'll find information that will assist you in reviewing and interpreting FTP logs, as well as links to Macromedia TechNotes, which offer troubleshooting tips for specific FTP difficulties:

Accessing the Site FTP log


In the Site window, choose Advanced > FTP log.

In the Site window, choose Advanced > FTP log.

An FTP log example
In the sample FTP log below, you'll see numbers (such as 220) that are referred to as "series codes." Interspersed throughout the series codes are commands (such as MKD).

220 FTP server (ms-ftpd(16) Thu Feb 27 18:32:59 EST 1997) ready.
USER jmacro
331 Password required for jmacro
230-Checking disk usage, please wait.
230- Your disk quota is: 5.00 megabytes.
230- Your disk usage is:
230- Home/WWW: 1.23 megabytes
230- FTP: 0.00 megabytes
230- Total: 1.23 megabytes (25% of quota)
230 User logged in.
215 UNIX Type: L8 Version: BSD-198911
257 "/jmacro" is current directory.
257 MKD command successful.
200 Type set to A.
PORT 10,11,1,80,18,238
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls

FTP codes and actions
The series code (the number) at the beginning of some lines of the FTP log describes the action that took place between your computer and the server in the FTP process. The table below offers a description of these FTP codes and actions.

FTP series codes

Code Description
100 Series Codes The requested action is being initiated, expect another reply before proceeding with a new command.
110 Restart marker reply.
120 Service ready in nnn minutes.
125 Data connection already open, transfer starting.
150 File status okay, about to open data connection.
200 Series Codes The requested action has been successfully completed.
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. (Where NAME is an official system name from the list in the Assigned Numbers document.)
220 Service ready for new user.
221 Service closing control connection. Logged out if appropriate.
225 Data connection open; no transfer in progress.
226 Closing data connection. Requested file action successful (for example, file transfer or file abort).
227 Entering Passive Mode
230 User logged in, proceed.
250 Requested file action okay, completed.
257 "PATHNAME" created.
300 Series Codes The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information.
331 User name okay, need password.
332 Need account for login.
350 Requested file action pending further information.
400 Series Codes The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again.
401 This service is not accepting users now. User quota filled. Try again later.
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.
431 Log-in unsuccessful. User name and/or password invalid.
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. Insufficient storage space in system.
453 File transfer incomplete. Insufficient storage space.
500 Series Codes The command was not accepted and the requested action did not take place.
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. File unavailable (e.g., file not found, no access).
552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
553 Requested action not taken. File name not allowed.

Note: Bear in mind that some of these codes may have different meanings with different servers.

Common FTP commands
Some text commands describe actions, as explained in the following table:

FTP commands and actions

ABOR abort a file transfer
CWD change working directory
DELE delete a remote file
LIST list remote files
MDTM return the modification time of a file
MKD make a remote directory
NLST name list of remote directory
PASS send password
PASV enter passive mode
PORT open a data port
PWD print working directory
QUIT terminate the connection
RETR retrieve a remote file
RMD remove a remote directory
RNFR rename from
RNTO rename to
SITE site-specific commands
SIZE return the size of a file
STOR store a file on the remote host
TYPE set transfer type
USER send username