Understanding the FTP Voyager Log - KB Article #1223Related Articles --
The following is a copy of FTP Voyager's log. This example shows a file being downloaded after connecting to a public FTP server.
STATUS:> Connecting to "ftp.cat-soft.com" on port 21
220-Serv-U FTP Server v4.1 for WinSock ready...
220-Welcome to ftp.cat-soft.com, home of Serv-U!
220-This server supports secure transfers through SSL/TLS!
220-Local time is 10:18:00, and 2770 users have visited over the last 24 hours
220-This server has been up for 4 days, 19 hours, 57 min. and 2 sec.
220- Users logged in: 4540 total
220- Current users: 2
220- Kb downloaded: 3096352 Kb
220- Files downloaded: 1738
220- Average throughput: 7.426 Kb/sec
220- Current throughput: 0.000 Kb/sec
In this part of the log, FTP Voyager successfully locates the FTP server. The FTP server then displays a welcome message to FTP Voyager. Each line beginning with 220 is a part of the welcome message sent by this particular FTP server.
STATUS:> Connected. Logging into the server
COMMAND:> USER anonymous
331 User name okay, please send complete E-mail address as password.
COMMAND:> PASS ********************
230 User logged in, proceed.
After FTP Voyager connects to the server and receives the welcome message, the FTP server then requires the client to login with a username and password. In this example, an anonymous login is used. This means that the user name is “anonymous” and the password can be any e-mail address. Most public FTP servers will allow for anonymous connections.
STATUS:> Login successful
This line confirms that the username and password have been accepted.
MDTM YYYYMMDDHHMMSS[+-TZ] filename
The FEAT command is an optional extension to the FTP protocol supported by FTP Voyager and Serv-U. This command is used to ask the server for additional commands that it supports outside the basic FTP protocol defined in RFC 959.
COMMAND:> REST 100
350 Restarting at 100. Send STORE or RETRIEVE.
COMMAND:> REST 0
350 Restarting at 0. Send STORE or RETRIEVE.
STATUS:> Server supports resume
FTP Voyager sends the REST command to see if the FTP Server it is connecting to supports resume. If the server supports, resume FTP Voyager remembers this and allows the option to be used on any broken transfers.
257 "/" is current directory.
COMMAND:> CWD /
250 Directory changed to /
These commands are FTP Voyager navigating to the home directory.
COMMAND:> TYPE A
200 Type set to A.
227 Entering Passive Mode (24,199,157,58,39,218)
FTP Voyager now establishes a data connection. The data connection has to be established before any data can be sent between the FTP client and the FTP server. After FTP Voyager issues the PASV command, the FTP server replies with an IP Address and port number. The first four digits in the 227 numbered response from the server are the IP Address of the server (18.104.22.168). The last two digits tell FTP Voyager what port number to establish the data connection on. To figure out what port number is being used, multiply the first number by 256 and add the second number to the result. The port number being used in this example is (39 * 256) + 218 = 10202.
More details on PASV and PORT can be found in Knowledge Base Article 1138.
COMMAND:> LIST -T
150 Opening ASCII mode data connection for /bin/ls.
226 Transfer complete.
The first data connection is used to transfer the directory listing. The directory listing tells the client the contents of the current directory. If the connection hangs before you see "226 Transfer complete", then the data connection failed to be established. If you see a PORT command rather then a PASV command, try and switch to using PASV mode. This option is under the Advanced button, Connection area, PASV Mode. Make sure there is a black and white checkmark in this field and then try the connection again.
STATUS:> Receiving: /ServUSetup.exe -> C:\ServUSetup.exe
This is a status message from FTP Voyager indicating it is about to being the requested file transfer. The requested file (ServUSetup.exe) is being downloaded from the user's home directory on the server (/) to the local C:\ path.
COMMAND:> TYPE I
200 Type set to I.
Most FTP servers support the two basic transfer methods: binary and ASCII. TYPE I is binary, and TYPE A is ASCII. An excellent website that talks about the differences between the two is located at http://www.htmlgoodies.com/beyond/ftp.html.
227 Entering Passive Mode (24,199,157,58,39,220)
COMMAND:> RETR ServUSetup.exe
150 Opening BINARY mode data connection for ServUSetup.exe (2993875 bytes).
226 Transfer complete.
To transfer the requested file, FTP Voyager first establishes a new data connection again using the PASV command. The RETR command is used to download files. If this log showed a file being uploaded, a STOR command would be used instead.
STATUS:> Received 2,993,875 bytes.
STATUS:> Transfer buffer size 5,120 bytes.
STATUS:> Transfer time: 00:06:12; 7.86KB/sec
Finally, FTP Voyager displays a confirmation that the file has transferred successfully. There is also some useful information about the total amount of data received, the buffer size used in the transfer, and the total transfer time.