The File Transfer Protocol and firewalls do not co-exist well. Luckily, firewalls, NAT devices, load-balancers, and proxies are handling FTP and its quirks better each year. Please see our article titled "The FTP and Your Firewall / NAT / Load-Balancing Router" for details on the problems and what you can do about them.

In Domain settings - > Router/firewall, you should set item "Router/Firewall's WAN IP or Domain" to router/firewall's WAN IP, also note the passive port range in Server Settings - > General, you should properly set your router/firewall, open the port 21 and ports in the passive port range, make it forward all packets on these ports to your server computer.

Generally, making FTP work through the firewall is done either using a proxy server such as the firewall toolkit's ftp-gw or by permitting incoming connections to the network at a restricted port range, and otherwise restricting incoming connections using something like ''established'' screening rules. The FTP client is then modified to bind the data port to a port within that range. This entails being able to modify the FTP client application on internal hosts.

If your server is behind a firewall or router you will need to allow the relevant ports for the FTP server through. The ports that must be configured for firewalls and routers include port 21 (standard FTP port) and port 990 (for implicit SSL). If you have changed these default port values on your FTP server then you should forward your port values instead. When FTP clients are using PASV mode for files transfers, the FTP server needs to be able to open additional ports.

eCare uses the HTTP port (port 80) for initial communications and services between the Support Agent and the Client. The SSL port (port 443) is used for the View Remote User and Control Remote User features. Because of this, firewalls and/or proxies do not have to be reconfigured to enable online support, thus maintaining the safety of the corporate network.

If you are running through separate proxies for each service, you shouldn't need to do anything. If you are working through sockd, you will need to "socksify" your application. Details for doing this can be found in the package itself, which is available at:

CDEveryWhere supports most major FTP servers. Most Unix (and clones), Microsoft Internet Information Server and AS/400 are supported. If your server is not supported, please send email to support@cdeverywhere.com with the following information:

WS_FTP is a commonly used file transfer program with a graphical interface. The screen consists of three major areas: the "Local System", or your hard drive, and the "Remote System", or the machine you're connecting to, and the smaller status window at the bottom which tells you the status of your connection to the remote system. Click on the WS_FTP Tutorial link below for screen shots and instructions on configuring to use with our service.

You can't have the DHCP server listening for requests directly from the users. This is because the relay agent is used to distribute the request to the right server, and in this case the server would answer to the user anyway. The Right Way to do it is to have the DHCP server in another machine located in the upstream network. Blocking requests from the users by filtering out any IP except for the relay agent in the firewall doesn't work either.

Yes, you can log into iaXX.us.archive.org (where XX is a number), with the username anonymous and use your email address as the password. Each recording's details page will have a link for FTP that will tell you which number server the show is on, and in which directory. Here is a thread with an example. The first file gets created when you submit the import form to the collection. If that file does not exist, you can create it by editing the details page and clicking Update.

curl ftp://ftp.sunet.se/%2ftmp/ or the not-quite-kosher-but-more-readable way, by simply starting the path

All firewalls work on a 'gateway' principle. The client connects to the firewall and sends a request to open a connection to any remote FTP server. Therefore, this property is not the same as the name of the FTP server specified when running the OsaSync connection wizard. Please note the properties that need to be set when using firewalls: Firewall Hostname as the remote firewall server, Firewall Port as the server's port, and the Type of firewall.

This depends upon how your firewall / NAT server is configured. Please ask your network administrator if your firewall (or NAT server) is configured to allow PING and TRACERT to work (which use ICMP ECHO, ECHO REPLY, and TTL EXPIRED packets). You can test this yourself by running these programs on your computer (For example, try "tracert www.visualware.com"). If these programs work, VisualRoute should work just fine on your computer.

A firewall, router, or proxy server is designed to be located between a user's machine and the internet. It will hide the IP address of the user's machine from view, thereby preventing direct access by external users or programs, some of whom may be malicious. ISMail Pro operates on a very restricted set of ports and contains a number of security safeguards. It can be exposed for access to the SMTP (port 25), POP3 (port 110), and IMAP4 (port 143) protocols.

If due to the security policy accepted in your corporate network or by your host provider you cannot connect to your MySQL server directly through TCP/IP (for example a firewall prevents this), you can use SSH or HTTP tunneling feature of SQL Manager to fulfill your task.

A firewall, router, or proxy server is designed to be located between a user's machine and the internet. It will hide the IP address of the user's machine from view, thereby preventing direct access by external users or programs, some of whom may be malicious. ISMail operates on a very restricted set of ports and contains a number of security safeguards. It can be exposed for access to the SMTP (port 25), POP3 (port 110), and IMAP4 (port 143) protocols.

You can use PanTilt Pro with a firewall or proxy server, as long as the ports needed to communicate to remote users are open. Make sure ports 8080 through 8888 are open to bi-directional traffic. If you also use Network Address Translation (NAT) in your network, you may still have problems getting PanTilt Pro's data to and from your computer correctly. We are currently working on a solution for this problem.

If due to the security policy accepted in your corporate network or by your host provider you cannot connect to your PostgreSQL server directly through TCP/IP (for example a firewall prevents this), you can use SSH or HTTP tunneling feature of SQL Manager to fulfill your task.