Network Driver Installation Notes
Network Driver Installation NotesFor Digital Formation, Inc. applications that support network users, there are network drivers available for the following server platforms:
Each section will provide information on setting up the driver(s) necessary to share the protected application on the network. Please refer to the appropriate section for where the network executables will be installed. The workstation platform does not matter for these instructions.
To run a CrypKey-protected program from a local drive on a Windows NT/2000 platform, you must install the Windows NT Stealth drivers on that machine. The drivers are required because Windows NT does not allow programs to directly access the computer hardware, which is necessary for the CrypKey to function. The standard Digital Formation, Inc. installation programs will properly install the CrypKey drivers, as appropriate.
This file and all of the additional files referred to in this document are stored by default in the \Product\Bin\Network directory.
Overview
This system uses a Windows network driver program, WCKSERVE.EXE, that can be run in any Windows environment to allow the computer to act as a server for CrypKey protected programs. WCKSERVE.EXE runs in the background and is transparent to the operation of the computer.
There are 2 ways to tell the driver where the protected application(s) can be found.
Where "dir" is the path to the directory that holds a CrypKey protected program. If there is more than one CrypKey protected program on the computer, a path must be given for each directory separated by a semi-colon. By default, each product directory will be \Product\Bin.
To configure WCKSERVE.EXE to automatically start-up and run in the background, just add WCKSERVE.EXE to the Startup group. When Windows is restarted, the driver will be running.
To uninstall the protection, remove the environment variable if you set it in the AUTOEXEC.BAT, remove any reference to the WCKSERVE.EXE from your Startup group, and delete WCKSERVE.EXE.
Details
The server must give READ and WRITE permission to its clients for the directory/directories where the protected software will reside. If WRITE permission is not given, all network access requests will be denied.
Overview
This system uses a Novell NetWare NLM (Network Loadable Module), which must be loaded into a NetWare server machine that is hosting CrypKey protected programs with network (floating) licenses. This driver is compatible with Microsoft Netware Clients. Digital Formation, Inc. has available the Novell Patch Level #5 for Novell 3.x, which is the minimum patch level required to run CKSERVER.NLM on Novell 3.x.
The NLM is called CKSERVER.NLM, and will automatically list itself in the AUTOEXEC.NCF file for automatic start-up when the server is rebooted. The NLM must be given READ, WRITE, CREATE, ERASE, MODIFY and FILESCAN permissions for the server machine it will be servicing. The NLM can only service the local file server that it is installed on, which includes the SYS volume and all other volumes on the server.
CKSERVER.NLM is self-configuring and will detect any CrypKey protected programs on the server it is running on. It does not require any interaction or configuration from the administrator once it has been loaded.
NetWare 3.x servers:
CKSERVER.NLM requires NetWare 3.x to be at the service pack level of at least the LIBUP5 patch, and DIRECTFS.NLM must also be loaded.
NetWare 4.x servers:
No special requirements.
Details
These NLMs have been tested on various different Novell servers, with various different upgrade patches and customizations. The success rate has been 100% on NetWare 4.x, and similarly, with only a couple of exceptions, on NetWare 3.x.
The two current test servers are configured as follows:
NetWare 3.12
- standard installation
- 32K hard-drive clusters
- Novell LIBUP5 patch installed
NetWare 4.1
- standard installation
- suballocation activated
- 32K hard-drive clusters
- no patches or upgrades of any kind installed
The NetWare clients that have been tested under include the Microsoft 16-bit Windows 95 client, the new Novell 32-bit Windows 95 client, and the Microsoft 32-bit Windows NT client.
NetWare 4.11 has also been tested successfully.
Troubleshooting
Certain errors can occur on Novell networks using either NLM.
Overview
This system has a fully automated installation script to perform the installation of the Windows NT/2000 driver necessary for the operation of protected software on a Windows NT system. The driver will be automatically installed when installing a Digital Formation, Inc. product under NT/2000.
The NT Driver setup (SetupEx.EXE) will automatically run when the Digital Formation, Inc. application is installed, if you are installing to NT/2000. No interaction by the user is necessary.
If re-installation is necessary, obtain and copy the SetupEx.EXE and CKS.EXE files to the \Products\Bin directory, and run the SetupEx.EXE program. These files are available from Digital Formation, Inc. The SetupEx.EXE program will install all of the necessary driver components, and install the reference to the appropriate application directory.
The list of directory names to be serviced is handled by the C:\WinNT\CKCONFIG.EXE program ("CrypKey Server V5.2 for NT"). Using this program, directories can be added and removed from the list. Be sure to be logged in as Administrator for running the configuration application.
These instructions must be followed for single workstation users running Windows NT/2000, as well as for Windows NT/2000 servers. The drivers will be automatically loaded when the system is restarted.
To uninstall the protection, run SetupEx.EXE /D, and then delete the files copied. This will uninstall the protection for all applications using this form of protection.
Details
This uses 2 driver files, CRYPSERV.EXE and CKLDRV.SYS, and uses CKCONFIG.EXE for configuration. Users must have READ and WRITE permissions for the protected application directory. These are Intel binaries only. Please contact Digital Formation, Inc. for other platforms.
The files installed can be found in the following locations:
C:\WinNT\System32\CRYPSERV.EXE C:\WinNT\System32\CKLDRV.SYS C:\WinNT\CKCONFIG.EXE
Troubleshooting
Two error log files are maintained by the Windows NT CrypKey driver. If you are having problems with the Windows NT driver, you can help us to help you faster by sending (by e-mail or fax) the two files that the driver creates. The two files are C:\WinNT\ERROR.LOG and C:\WinNT\System32\ERRORD.LOG. Please also include the configuration file C:\WinNT\CrypKey.INI, and just the time/date/size of the C:\WinNT\System32\CklDrv.SYS and C:\WinNT\System32\CrypServ.EXE driver files.
If you get an 'error 0x02', this is because of a failure to start the CrypKey Service. This can occur if you are not logged in as the Administrator, or if the permissions are blocking new NT services from starting. Check your Administrator tools and User Manager to verify the proper permissions.
Supported Versions of Windows NT/2000
CrypKey currently supports Windows NT 3.5 (Build 807), Windows NT 3.51 (Build 1057), Windows NT 4.0 (Build 1381), and all versions of Windows 2000. Currently, only the Intel binaries are being shipped. Contact Kenonic Controls for up-to-date platform support. Windows NT versions predating version 3.5 are not supported.
6000 E. Evans Ave., Suite 1-400 General: Info@DigitalFormation.com Denver, CO 80222-5415 Sales: Sales@DigitalFormation.com Tel: (303) 770-4235 Customer Support: Support@DigitalFormation.com Toll-free: (888) 747-5372 (US & Canada only) FTP Site: ftp://ftp.DigitalFormation.com/pub Fax: (303) 770-0432 Web Site: http://www.DigitalFormation.com