My http requests are being categorized/filtered, but I don't get the "Access Denied" block page.


This article applies to:

  • R3000

Question:

My http requests are being categorized/filtered, but I don't get the "Access Denied" block page.

Reply

Go through the following checklist.  If you need assistance with any of these items, please reference our FAQs or contact our technical support staff for additional help:
  • If you are using a custom block page, ensure that your web server is up and running.  Are you able to browse directly to your web server from your workstation?
  • Check your firewall to verify that the R3000 can send the “URL redirect” to users on TCP port 81, and that users can connect to the R3000 on port 80 to download the block page.
  • Verify that your workstation can communicate with the R3000 to download the block page by typing this in your web browser:  http://X.X.X.X:81/cgi/block.cgi (note: replace the “X’s” with the IP address of your R3000’s block page interface. Failure to download the block page from the R3000 might indicate a routing or firewall issue between the R3000 and the users.
  • If you are using an http proxy server, be sure that the URL redirect and block page is not going through the proxy server.  To accomplish this, set up an exception in your web browser’s proxy settings.  For example, if you’re using Internet Explorer, go to Internet Options -> Connections -> LAN Settings -> Advanced -> Exceptions.  In the “Exceptions” list, enter the IP address of your R3000’s block page interface, and the R3000’s hostname.  If you are using a custom block page, you should enter the IP address and hostname of your web server, in addition to the IP address and hostname of the R3000.  You will have to make this simple modification on every workstation that’s being filtered.  Normally, you can push this out as a Policy from your Active Directory server.

This article was previously published as:
8e6 KB 276590

Last Modified 2/16/2010.
https://support.trustwave.com/kb/KnowledgebaseArticle12398.aspx