TCP-IP Troubleshooting

hollowtabernacleNetworking and Communications

Oct 26, 2013 (4 years and 8 months ago)


TCP/IP Troubleshooting

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.


Configure security settings.
For TCP/IP networking there needs to be a clear TCP/IP connection between the client and the
server. The port used for communication is 4242 and must be open. Firewalls and security
software must be set to allow klserver.exe and the protected application to communicate. If you
are not using a TCPIPSVR.DAT file on the clients to point to a specific server, firewalls, security
software, and routers must also be set to allow UDP communication between client and server.

3. Is the TCP/IP dongle server klserver.exe is 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 a command (C:\>) 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.

4. Subnet

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.

5. Make sure the protected application is compiled using the networking object (OBJ) file or using
the networking DLL
In order for your protected application and find the Security Dongle over the network it must either be
compiled using KFUNC32N.OBJ(32-bit)/KFUNC64N.OBJ(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.


Run VerifyNetworkKey.exe

On the CD there is a utility (VerifyNetworkKey.exe) that can be used to ensure an application can
communicate with the dongle. This utility can be found on the cd in the Networking directory.


With the dongle attached run this application from the KEYLOK Server Machine


If the dongle is NOT found, download the latest Install.exe
and refer to How can I
remove all drivers and dongle-related software


If the dongle was found on server, run VerifyNetworkKey on the KEYLOK Client Machine

If the dongle is found from the client machine the issue is most likely one of the following

1) Interface File out of date

The interface file (KL2DLL32.DLL, NWKL2_32.DLL or KFUNC32x_xx.obj) used to
interface with the KEYLOK API is not in sync with the driver. If you are using a dll
download follow these steps for Step 4 above to download the latest install and
reinstall the KEYLOK files. If you are using an object file please contact support to
a request the latest version of the object file for the development tool you are
using. Be sure and indicate which development tool you are using including the
version number

 Using DEMO codes with a Company Unique Dongle

 There may be an issue in the calls to the KEYLOK API

Compare the calls in the protected application with the API calls in the sample

If you are still having issues please contact technical support at
or call 303-228-0288