By systematically working through the eight steps outlined above—license validation, enabling the engine, checking DNS and NTP, configuring an upstream proxy, and clearing corrupted caches—you can restore full web filtering in minutes.
| Preventive Measure | Why | |--------------------|-----| | Set up monitoring alerts | Receive email notification if categorization stops. | | Regularly check license expiry | Add a calendar reminder 30 days before renewal. | | Use redundant DNS servers | Prevents single-point-of-failure resolution issues. | | Document upstream proxy changes | Any proxy change requires updating Kerio. | | Test after updates | Category servers change IPs; test every quarter. | Q1: Can I use Kerio Control without cloud categorization? Yes, but only with static URL lists, IP-based rules, or by disabling web filtering entirely. Dynamic filtering will not work. By systematically working through the eight steps outlined
Yes. Use Kerio’s test tool (if installed): /usr/local/kerio/winroute/bin/kwfmgr --test-categorization example.com | | Use redundant DNS servers | Prevents
Article ID: KC-WF-001 Product: Kerio Control (formerly WinRoute) Affected Versions: 9.x, 8.x, and legacy 7.x Symptoms: Web filtering fails, content rules are ignored, and the administration interface shows a warning that categorization is disabled. Introduction Kerio Control is a robust unified threat management (UTM) appliance that provides firewall, VPN, and web content filtering. One of its most valuable features is the ability to block or allow websites based on dynamic URL categorization (e.g., “Social Networking,” “Adult Content,” “Streaming Media”). | Q1: Can I use Kerio Control without cloud categorization