Administrator's Guide - Kerio Software Archive

25.3 Automatic user authentication using NTLM
Status files
In addition, Kerio Control generates other files and directories where certain status
information is saved:
Files:
dnscache.cfg
DNS files stored in the DNS module’s cache (see chapter 9.1).
leases.cfg
IP addresses assigned by the DHCP server.
This file includes all information available in section Configuration → DHCP Server, the
Leased Addresses tab (see chapter 9.2).
stats.cfg
Interface statistics (see chapter 20.2) and user statistics (see chapter 20.1) data.
vpnleases.cfg
IP addresses assigned to VPN clients (see chapter 23.2).
Directories:
logs
The logs directory stores all Kerio Control logs (see chapter 22).
star
The star directory includes a complete database for statistics of the Kerio Control web
interface.
Handling configuration files
We recommend that Kerio Control Engine be stopped prior to any manipulation with the
configuration files (backups, recoveries, etc.)! Information contained within these files is
loaded and saved only upon starting or stopping the engine. All changes to the configuration
performed while the Engine is running are only stored in memory. All modifications done
during Engine performance will be overwritten by the configuration in the system memory
when the Engine is stopped.
25.3 Automatic user authentication using NTLM
Kerio Control supports automatic user authentication by the NTLM method (authentication
from web browsers). Users once authenticated for the domain are not asked for username and
password.
This chapter provides detailed description on conditions and configuration settings for correct
functioning of NTLM.
365