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

Questions about WkLAN


Normally, the use of WIBU-KEY within heterogenous TCP/IP networks causes no problem. Only a WIBU-KEY server process must be started on a server PC. After doing so each WIBU-KEY client should be able to use this server automatically via Boradcast provided that the clients are located in the same subnet.

The following questions serve as guideline for problems with WkLAN on different operating systems:



Questions about Windows 95, 98, Me, NT, 2000, XP, Server 2003



Questions about Mac OS 8, 9



Questions about Mac OS X



Questions about Linux




Windows 95, 98, Me, NT, 2000, XP, Server 2003

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". The WIBU-KEY server process must be started as an application.

Are all necessary driver files correctly installed?
Do you use the same WIBU-KEY driver version on the WIBU-KEY server and the Clients?
This is necessary for a "trouble-free" operation.

Are all WIBU-BOXes that are attached to the local system displayed properly?
This is necessary for a proper release of all network licenses. If problems occur please have a look at The local WIBU-BOX is not detected.

Is the WIBU-KEY network server displayed with the correct DNS name and the correct IP address?
Please check this by double clicking the network icon on page "Contents" in the WIBU-KEY control panel applet.
If this works, the drivers are correctly installed. In this case the problem is due to the configuration of the serverprocess or the server itself.

Was a new WIBU-BOX connected or a connected WIBU-BOX updated?
In this case, please restart the WIBU-KEY server process in order to reread all necessary data.

Does the number of free network users correspond with the number of licenses you want to have?
Please check this by using the WIBU-KEY network monitor.
You find the WIBU-KEY network monitor at > [Start- Programs- WIBU-KEY- Network Monitor]
After having searched for all WIBU-KEY servers they should be displayed in the WIBU-KEY network monitor with the appropriate licenses.

Is the WIBU-KEY server recognized on the client PCs?
Please move to page "Contents" and double click the network icon checking if the WIBU-KEY server is found.

Are the WIBU-KEY server and Client located in the same subnet?
If not, then enter the IP address of the WIBU-KEY server in the Server Search List on the Network page in the control panel applet.

Test possibilities via the command line.
Does WKU32 NET SERVERS work?
Can you do a WKU32 LIST AT <server address>?
Does the command work as well with the IP address as with the computer name?

If there are problems when specifying the machine name you should check the DNS/WINS settings..

Further possible reasons of problems.
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.

If there are time-out errors at the server, you can start the server using command START/HIGH WKSVW32.EXE with a higher priority.

Is the TCP/IP protocol correctly installed and activated?
Do you use TCP/IP as default protocol in your network?
Does the name of the Windows workstation differ from the name of the Computer in the TCP/IP (DNS entry)?
Does a Ping work between the Computers in both directions, with DNS name as well as with IP address (PING <server address>)?
Do you use a firewall which blocks the interface used by WkLAN (default: 22347)?



Mac

Mac OS 8, 9

You can only use the WIBU-BOX/A for the ADB interface and the WIBU-BOX/U for the USB interface.

Are you using the same WIBU-KEY driver version on both WIBU-KEY server and Clients?

This is necessary for a "trouble-free" operation.

Is the WIBU-BOX locally detected on the concerning WIBU-KEY server?
You can check this with our tool WkMacList. The WIBU-BOX should be listed under the appropriate interface.

Is the WIBU-KEY server recognized on the WIBU-KEY server and on the Client PCs?
You can check this whith our WkMacList when clicking the network icon. Of course, it must be ensured that a WIBU-KEY server process (WkSvMac) has been started.

Is the concerning WIBU-BOX to be found in our Webserver tool?
Just enter the URL: http://[Name or IP address of the server]:22347 into any browser.

Is the WIBU-KEY server and the Client located in the same subnet?
If not, please edit the file WIBUKEY.ini on all Clients as follows:


..
[WkLAN Client]
Server1 = [IP address of the WIBU-KEY server]
..



Has another WIBU-BOX been connected or a yet connected WIBU-BOX been updated?
In this case please restart the WIBU-KEY server process in order to reread all necessary data.



MAC OS X

You can only use the WIBU-BOX/U variant for the USB interface.

Do you use the same WIBU-KEY driver version on the WIBU-KEY server and the Clients?
This is necessary for a "trouble-free" operation. Is the WIBU-BOX locally detected on the concerning WIBU-KEY server? You can check this with our tool WkConfig.

Is the concerning WIBU-BOX found in our Tool WkConfig via the network?
Of course, it must be ensured that a WIBU-KEY server process (WkSvMacX) has been started.
You can also check this with our web server tool. Just enter the URL URL: http://[Name or IP address of the server]:22347 into any browser

Has another WIBU-BOX been connected or a yet connected WIBU-BOX been updated?
In this case, please restart the WIBU-KEY server process.

Is the WIBU-KEY server and the Client located in the same subnet?
If not, please use the Wkconfig Tool and enter the IP-Address or the DNS-Name of the WIBU-KEY Server into the Server search list on the "Client" page, or edit the file WIBUKEY.ini on all clients as follows:


..
[WkLAN Client]
Server1 = [IP address of the WIBU-KEY server]
..





Linux

You can only use Linux distributions with a Kernel > 2.4.x . The Linux kernel 2.6.x (like SuSE Linux 9.1) will be supported on WIBU-KEY Version 4.11 or later.

You can only use the WIBU-BOX variant for the USB and LPT interface, in detail the WIBU-BOX/U, WIBU-BOX/U+, WIBU-BOX/RU, WIBU-BOX/RU+, WIBU-BOX/P, WIBU-BOX/P+, WIBU-BOX/RP, WIBU-BOX/RP+.

What kind of Linux distributions are supported?
At the moment a lot of different Linux distributions are existing. WIBU-SYSTEMS tested WkLAN support for the current versions of the distributions from SuSE, Red Hat, Mandrake and Debian. Depending on the Linux system there should generally be other distributions applicable. Primary important is only the version of the used Linux kernel as well as system libraries such as glibc and libstdc++. If you are not sure, please make sure that you are using the WIBU-KEY network server on a Linux distribution, which is explicit named in relation to the driver version, for example: WIBU-KEY 5.0.510 for SuSE 9.3.

What kind of WIBU-BOX can be used? The type of WIBU-BOX you can use for the WIBU-KEY network server depends only on the WIBU-KEY server not on the client. At the moment you can only use the WIBU-BOX variant for the USB interface and not the WIBU-BOX/ST.

Do you use the same WIBU-KEY driver version on the WIBU-KEY server and the clients?
In general not. It is strongly recommended to use the same versions of the WIBU-KEY network server and WIBU-KEY client. Just then new functions or improvements can be used to the full extent. Therefore you should use the same driver versions.

Is the WIBU-BOX locally detected on the concerning WIBU-KEY server?
With the tool "WkConfigLin" you can check, which WIBU-BOX is available local or in the network . For example is a local connected WIBU-BOX/U (USB) not found, please check the rights of access (normally done by the so called "hotplug").

Has another WIBU-BOX been connected or has a present connected WIBU-BOX been updated?
If you have local started a WIBU-KEY network server and a WIBU-BOX has been connected or updated, please restart the WIBU-KEY server process.

Is the TCP/IP protocol correctly installed and activated?
If there are problems with the network communication, the following questions should be checked:
  1. Does your linux kernel support TCP/IP?
  2. Does your network connection between server and client work? You can test it for example with a "Ping". This should work with the direct IP address as well as the DNS name.
  3. Do you use a firewall which blocks the port used by WkLAN (default: 22347)?
  4. Do you use TCP/IP as default protocol in your network?
  5. Does the name of the Windows workstation differ from the name of the computer in the TCP/IP (DNS entry)?
  6. Is on sites of the Linux clients the environment variable "WKSYSTEM" (default: export WKSYSTEM='Kernel,WkLan') defined?


What is the difference between WkLAN and WkNet?
WkNet is a network subsystem that realizes data based protection. Therefore a file server saves a WkNet server file. The WIBU-KEY server as well as WIBU-KEY-clients can access asynchronous on the WkNet server file. WkNet is not available for Linux computers.

WkLAN is an protocoll based protection constitutive on TCP/IP. On Linux with WkSvLin a WIBU-KEY network server is available, which operates the requests of the WIBU-KEY-client in a synchronous and asynchronous way.