CAMNET
Server
CAMNET server is a complete NT service. All expected service operations, like install and uninstall, can be done directly from it. When run as a service -- to install, uninstall, start, or stop, from the command line -- you need to be an adminstrator. Once installed as a service, you generally have no direct interaction with the service. To run as a console application you can use any user account; just start it like any other application.

[ camnet server ]
If you installed CAMNET to run as a service, it has already been installed and it is running and ready. You can also, at any time, control the service from the command line. You must elevate to an administrator to directly control the service operations (-service stop, etc.).

To configure the service, from Control Panel, System and Security, Administrative Tools, select Services, find and select _CNS (usually the first service if listed alphabetically). Right click, Properties. The images below are what awaits.

If CAMNET server and the client are on different machines, at the server machine you must allow CAMNET server through the firewall. If not, the client reports that the connection attempt timed out (rc= 10060).

[ camnet server ]
The default account to run the CAMNET server when run as a service is the Local Service account. Normally, this is all you need (this is not the Local System account; Local Service has limited permissions, and there is no password for the Local Service account). To access a NAS, or storage on another machine (e.g., using a UNC share "\\WIN864\sharename"), you need to provide the account credentials. Do that in the service properties dialog. The account can be any user account that has permission to access the NAS/share from the machine on which the CAMNET service is running.

[ camnet server ]
If the CAMNET service were to crash, the operating system automatically restarts the service after 1 minute.

[ camnet server ]
The event viewer is used to review messages generated by the CAMNET service. The default log level includes errors and warnings. The loglevel.txt file in the camnet directory can be used to change the log level to generate more, or fewer, log messages. When run as a console application, the messages are sent to the console output.

[ camnet server ]
One CAMNET server can control from 1 to 20 cameras. To control more than 20 cameras on a machine, install or run CAMNET server using a different name (the -name option switch). You could have 10, 20, 30 servers, each controlling one camera, or each controlling up to 20. You can also have CAMNET servers on different machines, located anywhere, all managed by a single client. The CAMNET service manager (the client) also handles up to 20 cameras; it can mix and match cameras from different CAMNET servers. You can rename/copy the camnetsvcmgr.exe to a new name and then manage an additional 20 cameras for each, differently-named, instance of the client.

The CNX64FREE package does not expire and does not need registration. It has two restrictions: The included license.pid is for one camera, and for one server instance.

The third line of the license.pid file has the following:

:00000000000000000000000000000000:

Use this to create your own encryption key. Each digit is a hexadecimal digit (0-9, and A-F) and each adds 4 bits to your crypto key, for a total of 128 bits. For example,

:0123456789abcdef01234567890abcef:

Make this change before doing any CAMNET set up because files are encrypted using this. Save any change you make to the license.pid file; once CAMNET server starts it encrypts the license.pid, and renames it to license.mid. Many CAMNET data files are encrypted using this, so if you change the license.pid file, keep a copy of the changes secured away so you can restore it, if needed. Access to recordings (if encrypted) and many data files requires this license.pid key.

Since license.pid is encrypted after CAMNET server starts, and the service is started by default using the installation package, you need to re-install the package (do the install to a different location), this time not installing as a service. Stop any existing service. Copy the license.pid from the new install to the original install location. Make any changes to the key. Copy the changes to a secure location so you can restore the changes if needed. Start the service again (or the console application). Existing files that were encrypted using the original crypto key cannot be used. If you don't care about sharing a crypto key with all other CNX*FREE installations you do not need to make any changes. This crypto key is only used for local files; network encryption uses one-time keys to encrypt the transmission, as well as SSL around that.
 

To install or start more than one CAMNET server, use the -name switch, and a different port. For example:

   C:\camnet\bin>camnetserver -service install
   C:\camnet\bin>camnetserver -service install -name camnetserver2 -port 4056
The first uses -name camnetserver and -port 4040. The -port range extends from the port specified to that +15, hence the second server using 4056. The first server uses the directory at c:\camnet\camnetserver and the second uses c:\camnet\camnetserver2. You can share server database files (.udb, .cdb, .sdb, .rdb, and .xdb) by using a redirect; see the Log on entry in this guide for details.