Technical Notes |
|
This technical note explains how to configure Reflection FTP Client to connect through different types of firewalls.
The Reflection FTP Client is a component of many Reflection products and suites. For information about Reflection Suites components, see Technical Note 3000.
A firewall is a network security device used to protect organizations from unauthorized connections. Firewalls can be configured to restrict FTP file transfers in various ways, depending on the vendor and configuration. For example, some firewalls can be configured to support FTP transfers in a way that is transparent to users. Other firewalls, however, are more restrictive and allow only pre-authenticated and/or passive-mode FTP connections.
The FTP protocol establishes two distinct connections between the FTP client and FTP server:
Some firewalls may block the inbound FTP data connection from the server, while others may block both the inbound and outbound connections.
The following symptoms may indicate that a firewall is blocking FTP connections:
If you are experiencing any of the above symptoms or you suspect that there is a firewall between Reflection and the FTP server you are attempting to connect to, check with the network administrator to determine the type of firewall and how it is configured. Then, use the instructions below to configure Reflection FTP Client to connect to your FTP server through the firewall.
If you are unable to determine the firewall configuration, you still may be able to establish an FTP connection by experimenting with the various configurations described below.
Passive mode FTP transfers use only outward connections for both control and data connections. If you suspect your firewall is blocking inbound connections, follow the steps below to configure Reflection FTP Client for passive mode connections.
SOCKS proxy servers use the SOCKS protocol between the FTP client and the proxy server. Reflection FTP Client includes support for SOCKS V4 servers. SOCKS V5 servers are supported only when they are configured to use V4 features.
To configure Reflection FTP Client to support a SOCKS proxy server, follow the steps below that correspond to your version of Reflection.
See the online help for more information about configuring Reflection for multiple SOCKS proxy servers.
Passthrough servers differ from other proxy servers in that they use the FTP protocol to communicate between the FTP client and the firewall. To configure Reflection FTP Client to support common FTP Passthrough servers, follow the steps below.
Beginning in Reflection FTP Client version 10.0, support for other styles of firewall has been added: USER-PASS-ACCT, Transparent, and Challenge/Response. For detailed information about Firewall styles, search the FTP Client online help topic index for "Style."
There is no industry-standardized format for connecting through an FTP passthrough server. Because of the wide variation in authentication methods, you may need to experiment with the information you enter in the passthrough server and general site properties fields in Reflection.
For example, you may need to enter your firewall user name instead of your FTP server user name on the General tab of the Site Properties. Consult your firewall documentation for the required syntax.
Firewalls that support HTTP proxy connections require client applications to use the Web HTTP protocol and to understand HTML. Reflection FTP Client does not support this type of proxy. Contact your network administrator to determine if your firewall can be configured to support SOCKS or FTP passthrough proxy connections instead of or in addition to the HTTP proxy.