Port and Firewall


For the Binfer 6 application to function properly, external networks must be able to connect to the server. This includes port and firewall requirements.

Port The Binfer 6 Service needs a port on the system to be reserved for file transfers. A few important notes to remember are:

NOTE: We recommend whitelisting the entire Binfer domain via the wildcard option, which entails replacing "www" with "*" as see below:



To allow external clients and networks to connect to the internal machine where the BinferServer is installed, a network firewall rule must be created. An example configuration is as follows:

Example IP and Port

In this example, a rule should forward all traffic (two way) on public IP port 1212 to the internal Binfer server on port 1212. If there is no firewall but there is an IIS server on the public IP, a reverse proxy rule will work as well.

If updating domain and port values on an existing BinferServer installation, the domain and port values set earlier will need to be cleared and replaced once the mapping is complete. This can be done in SETTTINGS>NETWORK.

NOTE: It is strongly recommended that a domain name/subdomain name be used instead of the actual public IP. An existing domain can be used, which will allow for easier portability should the server ever need to be moved to another location in the future.


To confirm the ports have been opened and the firewall has been configured correctly, follow the below connection verification instructions after the installation of the Binfer 6 server: