Common Questions

Support

All

Dongle not working over Network?

In order for your protected application to find the Security Dongle over the network it must either be compiled using Kfunc32MTn or Kfunc32MDn(32-bit)/ Kfunc64MTn or Kfunc64MDn (64-bit) or use the networking DLL (NWKL2_32.DLL(32-bit), NWKL2_64.DLL(64-bit)) These files are compiler dependent and can be found in the sample code for the corresponding compiler.

We strongly recommend that you use the latest version of our installer in order to make sure that you always install the latest versions of our DLLs. Click here to download the latest version of the installer.

Is the 'subnet mask' set the same for both the server and clients?

Please note that it is strongly recommended on a TCP/IP network that the 'subnet mask' be set the same for both the server and clients. Network 'properties' can be used to acquire the subnet mask. Another method to acquire the subnet mask and other platform related data is to issue the command 'ipconfig -all'.

In some cases it may be possible to communicate across subnets using TCP/IP networking. The details are dependent upon your specific network configuration, so we can not provide specific recommendations concerning how to implement communication across subnets. As a starting point, however, we recommend that you try using a TCPIPSVR.DAT file to point the client to the server.

Is the TCP/IP dongle server klserver.exe installed and running?

Check to make sure that klserver.exe is installed in \Windows\System32 (32-bit OS) or \Windows\SysWow64 (64-bit OS) and that it is running as an automatic service.

You can check to make sure that klserver is running by going to Command Prompt, typing 'net start klserver', and pressing Return. The system should respond that the klserver service has already been started. If you get a response that the klserver service has been started successfully, go to Control Panel>Administrative Tools>Services and make sure that klserver is listed and that it is set to automatic to make sure that it starts each time the machine is booted. 

Is there is a firewall, router, or security software setting blocking communication between client and server?

In order for a client application to communicate with a dongle server via TCP/IP, verify that no firewalls or security software on client or server or routers settings is blocking communications.

All firewalls, security software, and routers must be set up to allow klserver.exe to communicate via TCP/IP, and must allow communications via TCP/IP port 4242. In addition, if you are not using a TCPIPSVR.DAT file to point the client to a specific server, all firewalls, security software, and routers must be set up to allow UDP communications between client and server.

How can I point the client to a specific server?

Use a TCPIPSVR.DAT file on the client.

In order to have an application running on a client machine point to a specific server, place a file named TCPIPSVR.DAT in the \Windows\System32 directory. TCPIPSVR.DAT should be a standard ASCII text file (such as those created by Notepad) and should contain one line with either the full IP address or network name of the server. The placement of the file is architecture dependent. 64-bit OS require placement of this file in either \sysWOW64 or \system32 depending upon the architecture of the application.

You can also use the install utility to create a TCPIPSVR.DAT file. When you install the client software, click the Set Server button. The utility will then allow you to either enter a network name or IP address manually or select the desired dongle server from a list of dongle servers currently active on the network.

Pages