CFS: Custom filtering (trusted or forbidden domains) is not working

Description

CFS: Custom filtering (trusted or forbidden domains) is not working

Resolution

If custom filtering is not working correctly, please check the following:

  1. Trusted and forbidden domains work only for web sites. It will not block sites accessed using other protocols, such as FTP. Access to sites using other protocols will have to be blocked using other means, such as defining rules on the Access/Rules page.

  2. Verify that you have enabled filter list customization on the Filter/Customize page, and that the Use Filter Option on the Filter/Categories page is set to log and block, not just log.

  3. Make sure that you have entered the name of the site correctly, and that there are no spaces or other improper characters in the entry. Enter only the name of the domain and not the protocol indicator. For example, "www.yahoo.com" is a valid entry, but "http://www.yahoo.com/" is not.

  4. Check for redundancy. For example if you already have an entry to block access to "yahoo.com" you do not need a second entry to block access to www.yahoo.com.
  5. The site accessed is an HTTPS site. CFS can only identify the domain accessed from http traffic, when access to an HTTPS site needs to be blocked/allowed, the IP address should be used in the Trusted, Allowed and Forbidden domains.



 

Related Articles

  • SSH password authentication fails after OpenSSH upgrade
    Read More
  • Where can I download SonicWall stencils?
    Read More
  • Configuring High Availability Monitoring settings
    Read More
not finding your answers?