For information about Globalscape, visit www.globalscape.com.
Many of these controls are intended for advanced users only. For example:
The REST/APPE sequence is only intended for problem servers that do not 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.
To access transfer settings
On the main menu, click Tools > Global Options (or press ALT+F7).
Expand the Transfer node. The Transfer options appear.
Configure options as described below.
In the Transfer method box, specify one of the following methods:
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.
Binary files cannot be transferred in ASCII mode, but ASCII files can be transferred in Binary mode.
Auto - 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.
PORT - 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.
If you connect in PORT mode, your session becomes vulnerable to "Port theft," which means that a third party can interfere with transfers.
EPRT - An extension of PORT command designed for communicating the client’s data connection IPv6 address and port, but used presently used in CuteFTP for communicating its IPv4 address and port. It is useful for negotiation through NAT firewalls..
EPSV - An extension of PASV command designed for requesting the server’s data connection port; present CuteFTP assumes IPv4 network protocol and is useful for negotiation through NAT firewalls.
EPRT and EPSV were designed for communicating IP and data port information for IPv6 addresses. Until IPv6 is supported in CuteFTP this feature is primarily used for improving firewall traversal of NAT firewalls for secure (FTPS) connections. Read RFC 2428 for more details. Note that each site in the Site Manager is currently able to either inherit global settings for Data Mode or define its own. Therefore the EPRT and EPSV choices are also available at the site level (Site Properties | Type tab).
Select the Allow transfers to occur over the existing (browse) session check box to transfer files 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.
Clear the check box to transfer files 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 this could cause a problem is when the server either refuses to allow multiple connections or is slow to log into.
If you select the check box, then press CTRL when transferring files, 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
In the When selecting MAX in a multi-part transfer use box, specify the number of parts to split a file into when a max multi-part transfer is requested.
In the Reconnect and resume in box, specify 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).
In the Roll back (retry at byte offset) box, specify 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 the Send REST command prior to APPE when resuming a transfer 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.
In the Receive buffer and Send buffer boxes, specify the number of bytes for the send and receive buffers. The 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, refer to Improving Slow Transfers.
Click Apply if you are going to make changes to other pages; click OK to save changes and close the Global Options dialog box.