Common Questions


TCP/IP Troubleshooting Tips

Try the following steps: 

  1. Be sure you can ping from the client to the server.
    Example: From a Command Prompt: ping "servername"
    ping "IP Address"
    If pinging is not possible all communications may be disabled between the client and server. Ensure that there is a "Trusted Zone" defined in the firewall settings for the connection between the KEY-LOK client and the server.
  2. Configure security settings.
    All firewalls, security software, and routers must be set up to allow klserver.exe and your application (yourapp.exe) to communicate via TCP/IP.
  3. Communications must be allowed via TCP/IP port 4242.
    This is generally allowed if a program has permissions to communicate but it may be necessary to open this port manually on the firewall for both the incoming and outgoing TCP port.

Unblock incoming and outgoing UDP ports.
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 as unblocked incoming and outgoing UDP ports to allow UDP communications between client and server.

What is TCP/IP Networking?

TCP/IP networking allows you to access a dongle mounted on a central dongle server machine from an application running on a remote client via a TCP/IP network.

You can use KL2, KL3, and Fortress keys with our TCP/IP networking solution. We currently have multi-user keys available that will support from 3 to an unlimited number of simultaneous users. You can also access our regular single-user keys over a network, but can only have one user connected to the key at a time.

Our install utility, install.exe, will install all of the necessary software and drivers for either a dongle server or a client.

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.