30.01.2015 Views

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

Administrator's Guide - Kerio Software Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

22.9 Filter Log<br />

• 8000-8099 — HTTP cache errors (errors when reading / writing cache files, not enough<br />

space for cache, etc.)<br />

• 8100-8199 — errors of the <strong>Kerio</strong> Web Filter module<br />

• 8200-8299 — authentication subsystem errors<br />

• 8300-8399 — anti-virus module errors (anti-virus test not successful, problems when<br />

storing temporary files, etc.)<br />

• 8400-8499 — dial-up error (unable to read defined dial-up connections, line<br />

configuration error, etc.)<br />

• 8500-8599 — LDAP errors (server not found, login failed, etc.)<br />

• 8600-8699 — automatic updates and product registration issues<br />

• 8700-8799 — dynamic DNS issues (unable to connect to the server, failed to update<br />

the record, etc.)<br />

• 9000-9099 — Bandwidth Limiter errors<br />

• 10000-10099 — web interface issues<br />

• 10100-10199 — crashdumps<br />

• 10200-10299 — NTP client issues (time synchronization with the server)<br />

• 10300-10399 — the <strong>Kerio</strong> Control Administration web interface errors<br />

• 11000-11099 — intrusion prevention system issues<br />

Note: If you are not able to correct an error (or figure out what it is caused by) which is<br />

repeatedly reported in the Error log, do not hesitate to contact our technical support. For<br />

detailed information, refer to chapter 26 or to http://www.kerio.com/.<br />

22.9 Filter Log<br />

This log gathers information on web pages and objects blocked/allowed by the HTTP and FTP<br />

filters (see chapters 13.2 and 13.5) and on packets matching traffic rules with the Log matching<br />

packets option enabled (see chapter 7) or meeting other conditions (e.g. logging of UPnP traffic<br />

— see chapter 18.2).<br />

Each log line includes the following information depending on the component which generated<br />

the log:<br />

• when an HTTP or FTP rule is applied: rule name, user, IP address of the host which<br />

sent the request, object’s URL<br />

• when a traffic rule is applied: detailed information about the packet that matches the<br />

rule (rule name, source and destination address, ports, size, etc.)<br />

297

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!