Administrator's Guide - Kerio Software Archive
Administrator's Guide - Kerio Software Archive Administrator's Guide - Kerio Software Archive
Introduction Figure 2.2 Disabling colliding system services during installation Note: 1. Upon each startup, Kerio Control detects automatically whether the Windows Firewall / Internet Connection Sharing is running. If it is, WinRoute stops it and makes a record in the Warning log. This helps assure that the service will be enabled/started immediately after the Kerio Control installation. 2. On Windows XP Service Pack 2, Windows Server 2003, Windows Vista, Windows Server 2008 and Windows 7, Kerio Control registers in the Security Center automatically. This implies that the Security Center always indicates firewall status correctly and it does not display warnings informing that the system is not protected. 2.5 Initial configuration wizard (Windows) Using this wizard you can define all basic Kerio Control parameters. It is started automatically by the installation program for Windows. Setting of administration username and password Definition of the administration password is essential for the security of the firewall. Do not use the standard (blank) password, otherwise unauthorized users may be able to access the Kerio Control configuration. 18
2.5 Initial configuration wizard (Windows) Figure 2.3 Initial configuration — Setting of administration username and password Password and its confirmation must be entered in the dialog for account settings. Name Admin can be changed in the Username edit box. Note: If the installation is running as an upgrade, this step is skipped since the administrator account already exists. Remote Access Immediately after the first Kerio Control Engine startup all network traffic will be blocked (desirable traffic must be permitted by traffic rules — see chapter 7). If Kerio Control is installed remotely (i.e. using terminal access), communication with the remote client will be also interrupted immediately (Kerio Control must be configured locally). Within Step 2 of the configuration wizard, specify the IP address of the host from which the firewall will be controlled remotely to enable remote installation and administration (provided that the Kerio Control Engine is started). Thus Kerio Control will enable all traffic between the firewall and the remote host. Note: Skip this step if you install Kerio Control locally. Allowing full access from a point might endanger security. Enable remote access This option enables full access to the Kerio Control computer from a selected IP address Remote IP address IP address of the computer from where you will be connecting (e.g. terminal services client). This field must contain an IP address. A domain name is not allowed. 19
- Page 1 and 2: Kerio Control Administrator’s Gui
- Page 3 and 4: Contents 1 Quick Checklist . . . .
- Page 5 and 6: 13 HTTP and FTP filtering . . . . .
- Page 7 and 8: 26 Technical support . . . . . . .
- Page 9 and 10: 8. Enable the intrusion prevention
- Page 11 and 12: 2.2 Conflicting software Warning: S
- Page 13 and 14: 2.3 System requirements met). 2.3 S
- Page 15 and 16: 2.4 Installation - Windows • TCP/
- Page 17: 2.4 Installation - Windows Warning:
- Page 21 and 22: 2.6 Upgrade and Uninstallation - Wi
- Page 23 and 24: 2.7 Installation - Software Applian
- Page 25 and 26: 2.7 Installation - Software Applian
- Page 27 and 28: 2.10 Kerio Control Engine Monitor (
- Page 29 and 30: 2.11 The firewall’s console (Soft
- Page 31 and 32: 3.1 Kerio Control Administration we
- Page 33 and 34: 3.2 Administration Console - the ma
- Page 35 and 36: 3.3 Administration Console - view p
- Page 37 and 38: Chapter 4 License and Registration
- Page 39 and 40: 4.3 License information User is def
- Page 41 and 42: 4.4 Registration of the product in
- Page 43 and 44: 4.4 Registration of the product in
- Page 45 and 46: 4.4 Registration of the product in
- Page 47 and 48: 4.4 Registration of the product in
- Page 49 and 50: 4.6 Subscription / Update Expiratio
- Page 51 and 52: Chapter 5 Network interfaces Kerio
- Page 53 and 54: 5.3 Viewing and editing interfaces
- Page 55 and 56: 5.3 Viewing and editing interfaces
- Page 57 and 58: 5.5 Advanced dial-up settings Figur
- Page 59 and 60: 5.6 Supportive scripts for link con
- Page 61 and 62: 6.1 Persistent connection with a si
- Page 63 and 64: 6.1 Persistent connection with a si
- Page 65 and 66: 6.2 Connection with a single leased
- Page 67 and 68: 6.3 Connection Failover Advanced di
Introduction<br />
Figure 2.2<br />
Disabling colliding system services during installation<br />
Note:<br />
1. Upon each startup, <strong>Kerio</strong> Control detects automatically whether the Windows Firewall /<br />
Internet Connection Sharing is running. If it is, WinRoute stops it and makes a record in<br />
the Warning log. This helps assure that the service will be enabled/started immediately<br />
after the <strong>Kerio</strong> Control installation.<br />
2. On Windows XP Service Pack 2, Windows Server 2003, Windows Vista, Windows Server 2008<br />
and Windows 7, <strong>Kerio</strong> Control registers in the Security Center automatically. This implies<br />
that the Security Center always indicates firewall status correctly and it does not display<br />
warnings informing that the system is not protected.<br />
2.5 Initial configuration wizard (Windows)<br />
Using this wizard you can define all basic <strong>Kerio</strong> Control parameters. It is started automatically<br />
by the installation program for Windows.<br />
Setting of administration username and password<br />
Definition of the administration password is essential for the security of the firewall. Do not<br />
use the standard (blank) password, otherwise unauthorized users may be able to access the<br />
<strong>Kerio</strong> Control configuration.<br />
18
Change language