Question/Problem: How do I use WS_FTP Pro
with a proxy or firewall?
General proxy and firewall information
WS_FTP will work with a proxy server or firewall as long as the proxy server or firewall
is a "true" FTP proxy or firewall -- not one that substitutes FTP protocol with
HTTP. (Note that Web browsers convert FTP to HTTP commands which is why a browser might
work with a firewall when WS_FTP will not.)
If you are behind a [proxy server or] firewall, fill in the Firewall is
tab in the Connection screen. To enter firewall information, you'll need to
get information about your firewall from your network administrator; depending on the type
of firewall, you'll need the following information:
For a "SITE hostname" firewall type, you'll need Host Name (or Address) and User
Name (ID).
For a "Transparent" firewall type, you'll need User Name (ID) and Password.
For "USER with no logon" or "Proxy OPEN" firewall types, you'll need
the Host Name (or Address). (The User Name and Password are ignored.)
For "USER after logon," "USER remoteID@remoteHost fireID," "USER
fireID@remoteHost," or "USER remoteID@fireID@remoteHost" firewall types,
you'll need Host Name (or Address), User Name (ID), and Password.
SOCKS Proxy
If the proxy is a SOCKS proxy, you will need to use a third party redirector. We recommend
SocksCap from NEC; you can download it from http://www.socks.nec.com/.
MS Proxy information
If the MS Proxy Server type is
2.0, there is no need to configure anything on the WS_FTP client systems to go through the
proxy.
The Proxy Client should be installed on the Proxy
Server. Once WS_FTP Pro sends out the request it will be intercepted by
the Proxy Client which in turns sends it to the Proxy Server.
If the proxy is an MS Proxy version earlier than 2.0, you will need to install the
Microsoft WinSock Proxy Client on EACH client system and disable the firewall.
The user should first check to see if they have the
Microsoft WinSock
Proxy Client. Do they have the WSP Client icon in their Control Panel? If not, this is a big indication
that the Proxy setup is not complete for their workstation. They can run the installation over their network by going to
//PROXYSERVER/mspclnt/Setup.exe">
<\\\\PROXYSERVER\\mspclnt\\Setup.exe> ,
where PROXYSERVER is the name of the machine that MS Proxy was installed
on.
The FTP portion of MS Proxy may not work if the REST command is not implemented properly.
Before starting the file transmission, the REST command must do a file position at the
value specified after opening the file. If your
specific proxy or firewall is not mentioned, contact your proxy or
firewall vendor for further assistance.
This information comes from a customer: Proxy Server has been discontinued,
although it's still popular. It has been replaced with ISA 2000 SERVER. Under this
configuration, you should use the "TRANSPARENT setting". But it should be noted that when specifying the user and
password, this should be the SAME as when setting up the connection (i.e.
the user/password combination setup on the FTP SERVER), not the user/password used to connect to the
proxy (ISA), which is often the windows logon/password. Also, the default port is 8080 on
ISA (not 80), and this must be specified in the Firewall properties of WS_FTP. The remote port
probably remains at 21. Finally, there is no need to change the browser connection settings, which may be tempting,
to reflect a different port for FTP. |
