| Home | Installation | Local | Printer | WkLAN | WkNet | Encrypt | FAQ | Imprint | | German | English |

Questions about WkNet

The following points should be checked when problems with WkNet occur:

General
Which version of the WIBU-KEY software are you using?
What kind of WIBU-BOX are you using?


Server Side

What kind of operating system are you using?
Windows 95, 98, ME are only restrictedly suitable for the server operation because they don't offer "services".

Are all necessary driver files correctly installed?
Can you start the WIBU-KEY Control Panel Applet without an error message? Are all WIBU-BOXes that are attached to the local system displayed properly?

If all driver files are correctly installed the problem must be the configuration of the server process.

Restart the server process:
Are the local WIBU-BOXes displayed?
Does the number of free network users correspond with the number of licenses you want to have?
Has the WkNet process been started properly?
Does the information displayed for the WkNet process correspond with the entries you want to have?

Have the necessary parameters (Firm Code, User Code, Selection Code, Timeout, Refreshtime and Path to WkNet file) been correctly displayed on the page "ServerWkNet" of the WIBU-KEY Control Panel Applet?
Can the Server and each Client access the concerning WkNet file "for reading and writing"?

If there are still problems, you can shut down the server and restart it using the Option /V3 command line. This command line gives more information about the status of the server process and possible problems.
Are additional error messages displayed? If so what do they say?
If you get the message "0 users maximum": Are you sure that the server process can access the WkNet file for reading and writing?
If you get the message "0 users maximum": Check the WkNet file with WKNETLST - are you accessing the same file? To be sure create another WkNet.dat file, restart the Server and check the WkNet file again with WKNETLST. If the error message "not initialised" is displayed, the server did not access the data WkNet.dat.

Client Side

What kind of operating system are you using?
Can you start the WIBU-KEY Control Panel Applet without an error message? Are all WIBU-BOXes that are attached to the local system displayed properly?
Have the necessary parameters (Path to WkNet file, internal application name) been set on the "Network" page of the WIBU-KEY Control Panel Applet?
Do the network client settings in the WIBUKEY.INI match the settings on the server side?
Is the given path to the WkNet file correct? Can the client access the WkNet file for reading and writing?
Has the WKBACCESS structure been filled with the correct information? Correspond application name, Firm Code, User Code, Selection Code and the encryption sequence?

Are you trying to start a client on the same machine where the server process is running? This may result in problems when both applications try to access the WIBU-BOX - you should disable the local subsystem on the network page of the WIBU-KEY Control Panel Applet.