Remote Filtering Communication Screen

Custom Deployment > Installing Web Security components > Remote Filtering Communication Screen

Remote Filtering Communication Screen

Applies to

Web Filter v7.6

Web Security v7.6

Web Security Gateway v7.6

Web Security Gateway Anywhere v7.6

Description

This Web Security installer screen appears if Remote Filtering Server is selected for installation.

The external IP address or host name of the firewall or gateway must be visible from outside the network. If you enter a host name, it must be in the form of a fully-qualified domain name: <machine name>.<domain name>

Important

Remember whether you entered an IP address or a host name here. When installing the Remote Filtering Client on user machines, you must enter this address in the same form (IP address or domain name).

Note

It is a best practice to use IP addresses, rather than host names, unless you are confident of the reliability of your DNS servers. If host names cannot be resolved, Remote Filtering Clients will be unable to connect to the Remote Filtering Server.

The external communication port can be any free port in the range 10-65535 on this machine. This port receives HTTP/HTTPS/FTP requests from external Remote Filtering Client machines (i.e. user machines, running Remote Filtering Client, outside the network). The default is 80. If a Web server is running on this machine, it may be necessary to use a different port.

Note

The external network firewall or gateway must be configured to route traffic, typically via PAT or NAT, from Remote Filtering Client machines to the internal IP address of this machine.

The internal communication port can be any free port in the range 1024-65535 on this machine. The default is 8800. This is the port to which remote client heartbeats are sent to determine whether a client machine is inside or outside the network. The external network firewall must be configured to block traffic on this port. Only internal network connections should be allowed to this port.

For more information, see the Remote Filtering Software technical paper.

	Important Remember whether you entered an IP address or a host name here. When installing the Remote Filtering Client on user machines, you must enter this address in the same form (IP address or domain name).

	Note It is a best practice to use IP addresses, rather than host names, unless you are confident of the reliability of your DNS servers. If host names cannot be resolved, Remote Filtering Clients will be unable to connect to the Remote Filtering Server.

	Note The external network firewall or gateway must be configured to route traffic, typically via PAT or NAT, from Remote Filtering Client machines to the internal IP address of this machine.

Quick Links

Custom Deployment > Installing Web Security components > Remote Filtering Communication Screen