FAQ - Network Support / Network License Control (LCS)

Which network components are required for the CRYPTO-BOX installation on the client computer?

For AutoCrypt, the required CRYPTO-BOX library "fmteos.dll" (resp. fmteos64.dll for 64 bit applications) is generated in the same folder where AutoCrypt has stored your protected application.

For API implementation you need the CRYPTO-BOX library which usually comes with your protected application (e.g. static library for C++ or Delphi, or CBIOS4NET library for C#).

Installation of the CRYPTO-BOX driver, or other network components are not required.

Which network components are required for the CRYPTO-BOX installation on the server side?

On the server side, the installation of the  CRYPTO-BOX driver (for Windows systems only) and the CBIOS Network Server are required.

The easiest way is to use our CBIOS Network Server Setup (for Windows Platforms). It automatically installs both, the CRYPTO-BOX driver and the Network Server, on the target system.

The latest version of this setup can be downloaded here.

I cannot connect to the CBIOS Server / I always get CBIOS:ERR_CONN_REFUSED and/or "ERR: proc_request: Can not get encryption parameters" message in server log file

This error can have different reasons:

1. In most cases this is a configuration/firewall issue. Please check your network and firewall settings or try to disable your firewall temporary to test connection. You can also use MARX Analyzer to test your network configuration

2, Assuming evertyhing worked fine before and you suddenly receive CBIOS:ERR_CONN_REFUSED on the client side and "ERR: proc_request: Can not get encryption parameters" message in server log file. In that case the connection between server and client was interrupted for longer time than the KeepAliveTimeout setting (180 sec by default), or the server was restarted. In such situations, the CBIOS Server will close all connections to that client (and release any locked licenses). If the client still tries to connect, it will get CBIOS:ERR_CONN_REFUSED message as answer from server. To solve this issue, the client needs to reconnect. See the "Network Licensing" White Paper at chapter 4.1.4 for more details

3. Settings for Packet Filtering are too restrictive, see point 3.9 in the "Network Licensing" White Paper for details.