Skip to main content

Support

Support Request

Common Questions

Install Utility Command Line Arguments

Install.exe Utility

Delimiters Valid command line delimiters are ‘/’ or ‘\’ or ‘-‘

A space is required before each delimiter and options cannot be combined (i.e. ‘/QN’ is illegal, but ‘/Q /N’ is legal).
/A

Install both parallel port and USB driver files

Note: This option will result in a parclass error 0x37 if a parallel port dongle is not attached during the installation process.
/B Install USB driver files only 
/C

Install network Client files and USB drivers

Allows local USB dongle or remote USB or parallel port dongle
/F Install Fortress files only
/NP Install parallel port TCP/IP server networking drivers to allow remote access to a parallel port dongle via a TCP/IP network
/NB Install USB TCP/IP server networking drivers to allow remote access to a USB dongle via a TCP/IP network
/NF Install Fortress TCP/IP server networking files to allow remote access to a Fortress dongle via a TCP/IP network.
/P Install parallel port driver files only 
/Q Quiet mode install – displays only fatal errors
/S:<IP address> Valid only for a network client install. Forces the client to attempt to connect to the dongle server at <IP address>. You may also specify the network name of the server instead of its IP address.
/U

Uninstall 

Removes all previously installed files


 

Cause: For security reasons some machines are built with no C:\ drive and KEYLOK Installer by default looks for C:\ drive to install the driver, causing the error you're experiencing.

Solution: To install on a machine with no C:\ drive. Copy the USBKey.sys or USBKey64.sys and USBKey.inf or USBKey64.inf, located on KEYLOK SDK “Send to End-Users\Optional Manual Installation Files”, to DriveLetter\Windows\System32. Edit the USBKey.inf or USBKey64.inf so the bottom line reads DISKID1= “Hard Driver YOUR DRIVE LETTER” instead of “DiskID1 = HARD Drive C:” and save the file. Go to the Device Manager, plug in the Key and when it appears in Device Manager Right-Click and select Update Driver and Select Install from specific location then navigate to System 32 and click on Install Driver. This should resolve the issue.

Cause: The issue that you are experiencing can be caused for various reasons. KEYLOK driver is not installed at all or not installed properly. If it’s a network key, an install is required on both Client and Server machines.

Solution: Check to see if the proper driver is installed. Go to the device Manager on your machine by Right-Clicking on “My Computer ->Manage->Device Manager” and if you see an exclamation mark next to USB Dongle – Software Protection Device then right-click on it and “Update Driver”.

If the problem persists, perform the following steps:

  • Download the latest driver (install.exe) from our website here.
  • Run the downloaded installer with the “uninstall” option first. Please make sure that the key is NOT plugged in during this entire process.
  • Once Uninstall is complete reboot your machine.
  • Then run install.exe again and follow the prompts and plug in the key when prompted.

This should resolve the issue and the key should show up as follows in your device manager:

In a network environment there can be many reasons the key is not being recognized by the application. To request our Network Troubleshooting Guide, please contact Technical Support.

Quick Start Guide for KEYLOK2 dongle

Quick Start Guide for KEYLOK3

To run your existing application with KL3, you will need to compile your application with the latest libraries. These libraries can be found on the SDK that came with your KL3. For more details please email support@keylok.com to request our KL3 Migration Guide.

KL3 is fully cross-platform, meaning it works on Windows, Mac and Linux and does not require drivers.

KEYLOK3 (KL3) is a driverless key that works using native Windows HID drivers. No external drivers are needed to run the key.

Try the following steps: 

  1. Be sure you can ping from the client to the server.
    Example: From a Command Prompt: ping "servername"
    or
    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.

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.