Configuring Remote Filtering settings
Use the
page to configure what happens if any Remote Filtering Client instance cannot communicate with Remote Filtering Server.- By default, Remote Filtering Client permits all HTTP, SSL, and FTP requests while it continues attempting to contact Remote Filtering Server (fails open). When the communication is successful, the appropriate filtering policy is enforced.
- Select the Block all requests... check box to prevent users from accessing the Internet when Remote Filtering Client cannot communicate with Remote Filtering Server (fail closed).
When Remote Filtering Client is configured to fail closed, a timeout value is applied (default 15 minutes). The clock begins running when the remote computer is started. Remote Filtering Client attempts to connect to Remote Filtering Server immediately and continues cycling through available Remote Filtering Servers until it is successful.
If the user has Internet access at startup, during the timeout period, all requests are permitted until Remote Filtering Client connects to the Remote Filtering Server.
If Remote Filtering Client cannot connect within the configured timeout period, all Internet access is blocked (fail closed) until connection to Remote Filtering Server can be established.
Note: If Remote Filtering Server cannot connect to Filtering Service for any reason, an error is returned to the Remote Filtering Client, and all requests are permitted (fail open).This timeout period allows users who pay for Internet access when traveling to start the computer and arrange for connection without being locked out. If the user does not establish Web access before the 15 minute timeout period expires, the user must restart the computer to begin the timeout interval again.
For detailed information about how remote filtering works, which components are involved, and how to deploy components, see the Remote Filtering Software technical paper.