| Support Main | Back to CuteFTP Tutorials |
From the menu, choose Tools > Global Options.
SelectTransfer.
Choose Auto-detect to have CuteFTP decide the transfer method based on the file and server type.
Choose ASCII to transfer text files, web pages or other text type files.
Choose Binary to transfer pictures, programs or executable files.
Note:
Binary files cannot be transferred in ASCII mode, but ASCII files can be transferred in Binary mode.
Choose Auto and CuteFTP makes connections in PASV mode. If the PASV connection fails, CuteFTP attempts to connect in PORT mode automatically.
PASV helps avoid conflicts with security systems. PASV support is necessary for some firewalls and routers, because with PASV, the client opens the connection to an IP Address and port that the server supplies.
Choose PORT when connections or transfer attempts fail in PASV mode, or when you receive data socket errors. When an FTP client connects using PORT, the server opens a connection to an IP Address and port that the client supplies.
EPRT is an extension of PORT that allows the server to give an Ipv6 address to the client for negotiation through NAT firewalls.
EPSV is an extension of PASV that allows the server to give an Ipv6 address to the client for negotiation through NAT firewalls.
Used as an alternative to PASV or PORT commands for the traversal of NAT firewalls for secure (FTPS) connections. Read RFC 2428 for more details. Common Add EPRT and EPSV to the existing Data mode drop-down (combo) located under Global Options | Transfer pane. Note that each site in the site manager is currently able to either inherit global settings for Data Mode or define their own. Therefore the EPRT and EPSV choices must also be available on a site basis (Site Properties | Type page).
Note:
If you connect in PORT mode your session becomes vulnerable to "Port theft," where a third party can interfere with transfers.
This feature controls the sessions that files are transferred on.
If Allow transfers to occur over the existing (browse) session is:
Checked, files transfer over new and existing sessions. CuteFTP uses the browse session and if available, additional connections. For example, If you define a per site max limit of five connections and then transfer five files, CuteFTP checks the browse connection first to see if it is busy, and if not busy, transfers the 1st file over the browse connection. The subsequent four files are transferred over four additional sessions. CuteFTP automatically adjusts for allowed connections (both from the client and server perspective) and whether or not it can use the browse session.
Checked + CTRL key, files transfer over the existing session only. To use this, select the files you want to transfer, then press and hold the Ctrl key while you drag and drop the files into the destination folder. This forces CuteFTP to transfer all the files on the existing session. Transferring files using only the currently logged in session can reduce overhead in certain situations. For example, a transfer of a large number of small HTML files can often be done much faster if limited to the current connection rather than performing a full TCP/IP connection and FTP login (and possibly FEAT/CWD/LIST) sequence first
Cleared (unchecked), files transfer over new sessions only. Use this option if your server allows multiple connections, is quick to respond, and you want to navigate the site while downloading. All transfers are forced over new connections, freeing up the browse session so you can continue to navigate. The only time may pose a problem is when the server either refuses to allow multiple connections or is slow to log into.
Select the Turbo mode check box to compress the files when transfer is initiated. Compression of files increases the transfer speed. Additionally, it splits a large file into multiple parts depending on the size of the file to increase the transfer speed when uploading a file to a server or downloading a file from a server.
Select the time that CuteFTP waits to try again after an interrupted or failed download. Select a time between 0 and 1,000 seconds (about 17 minutes).
Select the number of bytes prior to the transfer failure CuteFTP resends when attempting to finish an interrupted transfer. Select between 0 and 65536 bytes.
Select this check box to send the REST (Restart) command to resume a transfer, before sending the APPE (Append) command.
Clear this check box to send the APPE (Append) command to resume a transfer without first sending the REST (Restart) command.
Default setting for both send and receive is 65536 bytes. It is unlikely you will ever need to adjust these settings, but if you have problems with dropped transfers, you can use them to fine tune transfers over high latency or lossy connections like those over satellite links or with legacy CDMA wireless connections. For more, see Tweak the send and receive buffers in Improving Slow Transfers.
Tip:
Most of these controls are intended for advanced users only. For example, the REST/APPE sequence is only intended for problem servers that don't support the proper resume sequence. Transfer type should only be changed when you need to force files to transfer a certain way. The data port mode should only be changed if you are having problems establishing a data connection (on LIST or RETR for example). Limiting the local port range can have adverse affects when transferring many small files over a narrow range of ports