3.5  Connection Errors

This chapter provides description of the most frequent errors which are reported if connection to a server application fails.

Note: If an error which is not described here is reported, please contact Kerio Technologies technical support (all contacts can be found at http://www.kerio.com/).

Remote computer not found

This error is reported in case that the specified remote computer (server) could not be found (is not available).

Connection failed: Server not found

Figure 3.11. Connection failed: Server not found


Possible reasons of the error:

  • Wrong specification of IP address or DNS name of the server .

    Make sure that you use a correct IP address or that the DNS name you use is still valid (e.g. using the nslookup system tool).

  • Destination host is not available (e.g. for a network communication failure or because the traffic is blocked by a firewall).

    Test availability of the destination host by the ping command, or change your firewall settings.

Server application is not running

If the Administration Console cannot establish network connection to the server application on a corresponding computer, then the Server application is not running error is reported.

Connection failed: Server application is not running

Figure 3.12. Connection failed: Server application is not running


Possible reasons of the error:

  • Server application is not running.

    Check whether the Kerio WinRoute Firewall or the Kerio WinRoute Firewall service is running on the host you are connecting to.

  • Connection to a corresponding application port cannot be established (the communication is blocked by a firewall).

    Try to use the Telnet command to establish connection with a particular port (see chapter 4  Network communication of the Administration Console) and change firewall configuration if necessary.+

User authentication failed

If the Administration Console establishes connection to the server successfully and there is a problem with user authentication, the Authentication failed error is reported.

Connection failed: Authentication failed

Figure 3.13. Connection failed: Authentication failed


Possible reasons of the error:

  • Invalid username or password.

    Check whether your login data has been inserted correctly. If this error is arises when connecting through a bookmark, try to connect through New Connection by re-inserting all login data (for example, the user password could be changed and the bookmark may use an old password).

  • Remote administration of the server application is disabled or it is available from a certain range of IP addresses only (your computer does not belong to this group). For details refer to a corresponding server application's user guide.

  • User has not appropriate access rights.

    User account through which it is possible to connect must have the Read/Write access right (for administration), or the Read only access right (for configuration viewing).

  • Authentication at the server failed.

    An error occurred at the server that caused that the usual method of user authentication cannot be performed (e.g. in the Active Directory). For connection to the administration we recommend you to create a special user account in the internal user database (for details, see corresponding server application user guides).

Unsupported version of server

This error is reported in case that the Administration Console cannot find an administration module corresponding with the used version of server application (e.g. Kerio WinRoute Firewall 6.1.x is installed at the server, whereas the administration module is available for version 6.0.x only).

Connection failed: The server version is not supported

Figure 3.14. Connection failed: The server version is not supported


When this error is reported, install a corresponding administration module (or copy it into the Admin directory). It is highly recommended to use the same installation package from which the server application was installed.