- This topic has 0 replies, 1 voice, and was last updated 19 years ago by
.
-
Posts
-
Windows95 NetHASP License Manager
Last edited: January 04, 2004 08:17 AM
This document explains how to install and use NetHASP License Manager for Windows 95. This application is the equivalent of the DOS HaspServ program and must be used in it’s place on a Windows 95 computer. (The DOS HaspServ program will not run properly on a Windows95 computer.)
Topics covered are:
Installation
Using NetHASP
Technical InformationInstallation
To install the NetHASP License Manager on a Windows 95 computer:
Using NetHASP
We are configuring Windows 95 to automatically load the NetHASP license manager on startup by placing a shortcut to it in the StartUp folder. Startup means logging on. At this time NetHASP can not be loaded prior to a user logon. This means that in order to obtain HASP authorization, someone must be logged on to the system. If you leave the computer at the Windows Logon dialog, NetHASP is not running.
To run NetHASP License Manager:
Select the shortcut to NetHASP License Manager you created in the installation.
Once the NetHASP Server is running, other workstations will be able to get HASP authorizations from the HASP key.
There is limited help in the Help section.
The Activity Log shows the activity for each protocol. (whether is was loaded or not and any errors)
To remove NetHASP License Manager:
Choose Remove from the NetHASP License Manager main menu. (If you are supporting multiple protocols, select the protocol you want to remove.)
Technical InformationBelow is an excerpt from the NetHasp.TXT file included with the NetHASP installation files.
INSTALLING NETHASP ON A NETWORK
This document describes the steps required to install NetHASP and adapt the stations in the network to the NetHASP system.
Along with the protected application, your software vendor should supply you with:
* A NetHASP key
* All the NetHASP License Managers – applications that communicate with the protected application and the NetHASP
* The HASP Device Driver – an interface between the protected application and the NetHASP
* The NetHASP test utilities – diagnostic tools for the NetHASP system
* The NetHASP Monitor – a utility that lets you monitor the NetHASP License Managers on the network and applications that have performed a NetHASP LOGIN
* The NetHASP Configuration File – lets you change the NetHASP default settings
* Nethasp.txt – this fileNETWORKS SUPPORTED BY NETHASP
NetHASP supports the following networks: 3Com, Banyan Vines, D-Link, DEC Pathworks, Netware Lite, Novell 3.x, Novell 4.x, LANtastic, LanManager, OS/2 Lan Server, and any other network that uses the protocols listed below.
PROTOCOLS SUPPORTED BY NETHASP
NetHASP supports the IPX, TCP/IP, and NetBIOS network communication protocols.
IPX Support
NetHASP under IPX supports the following advertising mechanisms:
* SAP – Service Advertising Protocol
* Broadcast – while stations broadcast to the network, the NetHASP License Manager constantly listens in
* IPX without SAP – advertising the NetHASP License Manager through a file mechanism (address files)TCP/IP Support
In environments that support TCP/IP, NetHASP operates in two modes:
* TCP – the NetHASP License Manager address is specified
* UDP – the NetHASP License Manager address is not specifiedNetBIOS Support
NetHASP supports various types of NetBIOS including Microsoft NetBEUI.
THE NETHASP LICENSE MANAGER
You can connect the NetHASP to any computer on the network, providing you activate the correct NetHASP License Manager. This computer does not necessarily have to be the network file server.
The NetHASP License Manager is not dependent on the NetHASP or the protected application, but functions as a link between the two. Regardless of the environment in which the protected application is activated – DOS, Windows, Win32, or OS/2 – you can activate any one of the NetHASP License Managers to communicate with the protected application and the key.
One NetHASP License Manager can communicate with up to 250 protected applications running in any environment.
When several applications are protected with different NetHASP keys, we recommend you daisy-chain all keys to a single computer. Alternatively, you can connect the keys to different computers but then you have to activate the NetHASP License Manager on each of these computers.
Note: The NetHASP License Manager must remain active as long as any network station is running a protected application.
The NetHASP License Manager you use should comply with the operating system of the computer it is loaded on. The following table lists the various NetHASP License Managers and shows which protocols they support.
NetHASP License Manager protocol support:
NetHASP License Manager IPX TCP/IP NetBIOS
DOS (haspserv.exe) X X
Windows and Win32s (nhsrvwin.exe) X X X
Windows 95 and Windows NT (nhsvrwnt.exe)X X X
Netware 486 and 386 file servers (haspserv.nlm) X
OS/2(nrsrvos2.exe) XNote: The NetHASP License Manager for Win32:
* Works with IPX (without SAP) on Windows 95 and Windows NT. It cannot run under Win32s.
* By default, listens to all three protocols at once.The following sections describe the activation procedure for the NetHASP License Manager on various stations and file servers in the network.
NetHASP on a DOS Station
The NetHASP License Manager for DOS is haspserv.exe.
To load the NetHASP License Manager:
1. Connect the NetHASP to the station.
2. Run haspserv.exe. A message appears informing you that the NetHASP License Manager is loaded. The message also shows which protocol is being used.Note: To load the NetHASP License Manager automatically, add its filename to the autoexec.bat file.
To remove the NetHASP License Manager:
1. Run haspserv.exe -r.
2. Alternatively, delete the call line from the autoexec.bat file and reboot the station.NetHASP on a Windows or Win32s Station
The NetHASP License Manager for Windows is nhsrvwin.exe.
To load the NetHASP License Manager:
1. Connect the NetHASP to the station.
2. Run nhsrvwin.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocol is being used.Note: To load the NetHASP License Manager for Windows automatically, add its icon to the StartUp group.
To remove the NetHASP License Manager:
1. Choose Remove from the NetHASP License Manager menu bar.
NetHASP on a Novell Netware 386/486 File Server
The NetHASP License Manager for Novell Netware file servers is haspserv.nlm.
To load the NetHASP License Manager:
1. Connect the NetHASP to the station.
2. Copy haspserv.nlm to the SYSTEM directory of the file server.
3. Load the NetHASP License Manager, by entering:load haspserv
The NetHASP License Manager screen appears showing the protocol that is being used.
Note: To load the NetHASP License Manager automatically, add the line load haspserv to the autoexec.ncf file in the sys:system directory.
To remove NetHASP License Manager:
1. Enter unload haspserv.
NetHASP on a Windows 95 Station
The NetHASP License Manager for Windows 95 is nhsrvw32.exe.
To load the NetHASP License Manager:
1. Install the HASP Device Driver by activating hinstall -i.
2. Connect the NetHASP to the station.
3. Activate nhsrvw32.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocols are being used.To remove the NetHASP License Manager:
1. Choose Remove from the NetHASP License Manager main menu and choose the protocol support you want to remove.
NetHASP on a Windows NT Station
The NetHASP License Manager for Windows NT is nhsrvwn32.exe.
To load the NetHASP License Manager:
1. Install the HASP Device Driver by activating hinstall -i.
2. Connect the NetHASP to the station.
3. If you are using Windows NT version 4.0, skip to step 4. With Windows NT versions prior to version 4.0, you need to optimize the NetHASP License Manager response by setting the Tasking Option. This procedure causes Windows NT to give an equal time slice to foreground and background processes, and ensures that the NetHASP License Manager functions properly even if it is a background process.
1. Double-click the System icon in the Control Panel window.
2. Click the Tasking button in the System window.
3. In the Tasking window Foreground/Background Responsiveness frame, click:
Foreground and Background Applications Equally Responsive
4. Click OK to save your settings.
4. Activate nhsrvw32.exe. A window appears with a message informing you that the NetHASP License Manager is loaded. It also shows which protocols are being used.To remove the NetHASP License Manager:
1. Choose Remove from the NetHASP License Manager main menu and choose the protocol support you want to remove.
AUTOMATIC ACTIVATION OF NHSRVWNT.EXE
Under Windows NT, you can load the NetHASP License Manager automatically before user log on. You implement this with hinstall.exe.
Hinstall installs a HASP NT Loader implemented as a Windows NT service. This loader automatically loads the NetHASP License Manager. With the HASP NT Loader, you do not have to log on or interact with the Windows NT system.
To install the HASP NT Loader:
1. Log on as a user with Administrator Privileges.
2. Run hinstall -is.
3. Copy the NetHASP License Manager for Win32 to the SYSTEM32 directory in the Windows NT root directory.
4. Restart the system. The HASP NT Loader will automatically load the NetHASP License Manager.Note: When you install the NT Loader, the HASP Device Driver is also installed, and you can skip step 1 in the previous section. .
Since the NetHASP License Manager loads automatically before the user logs on, the HASP NT Loader and the NetHASP License Manager messages do not appear on the screen until you log on.
For example, if you try to load the NetHASP License Manager without a connected HASP, you do not see the “HASP not found” error message until you log on.
To remove the HASP NT Loader:
1. Log on as a user with Administrator Privileges.
2. Run hinstall -rs.
3. Restart the system.Note: This procedure does not remove the HASP Device Driver.
VIEWING THE ENTRY IN THE SCMANAGER
If the HASP NT Loader was properly installed, you can see its entry in the Windows NT SCManager (Service Control Manager).
To see the entry in the SCManager:
1. In the Control Panel, double-click the Services icon. The HASP NT Loader entry appears in the Services list.
2. Check that the Status field is empty, and that the Startup field is set to Automatic.NetHASP on an OS/2 Station
The NetHASP License Manager for OS/2 is nhsrvos2.exe.
To load the NetHASP License Manager:
1. Connect the NetHASP to the station.
2. Run nhsrvos2.exe.To load the NetHASP License Manager automatically at boot time:
1. Add the following line to the startup.cmd file:
start nhsrvos2
To remove the NetHASP License Manager:
1. Switch to the session running the NetHASP License Manager and press
.
Adapting NetHASP to the Network Protocol
The most critical stage in NetHASP system installation is ensuring that the NetHASP client (the station activating the protected application) finds the NetHASP License Manager. A communication session can begin only after the NetHASP License Manager is found. Each protocol has its own search mechanism. This section explains how to adapt the NetHASP system under each protocol to ensure successful communication between the NetHASP client and the NetHASP License Manager.
Adapting NetHASP to All Protocols under Win32s
Before activating a NetHASP-protected Win32 application from a Win32s station, copy hasput16.dll to the application directory. Otherwise, if you try to load the application, you receive NetHASP error 1.
Adapting NetHASP to IPX with SAP
With SAP (Service Advertising Protocol), the NetHASP client automatically finds the NetHASP License Manager.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager with the -ipx switch.
To adapt the NetHASP client:
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_IPX=Enabled
2. Copy the NetHASP Configuration File to the application directory.Adapting NetHASP to the IPX Broadcast Mechanism
The Broadcast mechanism enables the NetHASP License Manager to constantly listen in while the stations broadcast to the network.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager with the -broadcast switch.
To adapt the NetHASP client:
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_IPX=Enabled * In the [NH_IPX] section, set NH_USE_SAP=Disabled * In the [NH_IPX] section, set NH_USE_BROADCAST=Enabled
2. Copy the NetHASP Configuration File to the application directory.Adapting NetHASP to IPX without SAP
Under this mechanism, the NetHASP License Manager address is located in two files. To establish communication, the NetHASP client has to read the address.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager with the -ipxnosap switch. Two files are created, haspaddr.dat and newhaddr.dat, containing the address of the NetHASP License Manager.
Note: Once created, the address files are located in the same directory as the NetHASP License Manager. With haspsrv.nlm, they are located in the root of the file server SYS volume.
To adapt the NetHASP client:
Copy the address files to the application directory. You can bypass this step, by using the -addrpath switch when loading the NetHASP License Manager (see appendix D).
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_IPX=Enabled * In the [NH_IPX] section, set NH_USE_SAP=Disabled * In the [NH_IPX] section, set NH_USE_BROADCAST=Disabled
2. Copy the NetHASP Configuration File to the application directory.Note: Be sure to delete the address files, haspaddr.dat and newhaddr.dat, after:
Moving the NetHASP License Manager to another directory
Loading it on another PC
Rebooting the computer where the NetHASP is connectedIf you do not delete the address files, the speed of the protected application will be compromised, or the application may not run at all.
Adapting NetHASP to TCP/IP in TCP Mode
Under TCP, specify the NetHASP License Manager address in the NetHASP Configuration File.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager with the -tcpip switch.
To adapt the NetHASP client:
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_TCPIP=Enabled * In the [NH_TCPIP] section, set NH_TCPIP_METHOD=TCP * In the [NH_TCPIP] section, set NH_SERVER_ADDR=
, where is the IP address of the NetHASP License Manager
2. Copy the NetHASP Configuration File to the application directory.Note: The NetHASP License Manager defaults to port number 475.
If you want it to listen to another port:
1. Load the NetHASP License Manager with both the -tcpip and -portnum=
switches.
2. Make the following additional change to the NetHASP Configuration File:
In the [NH_TCPIP] section, set NH_PORT_NUMBER =Adapting NetHASP to TCP/IP in UDP Mode
Under UDP, the NetHASP client sends a packet to every station on the network while the NetHASP License Manager permanently listens.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager with the -tcpip switch.
To adapt the NetHASP client:
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_TCPIP=Enabled * In the [NH_TCPIP] section, set NH_TCPIP_METHOD=UDP
2. Copy the NetHASP Configuration File to the application directory.Note: The NetHASP License Manager defaults to port number 475.
If you want it to listen to another port:
1. Load the NetHASP License Manager with both the -tcpip and -portnum=
switches.
2. Make the following additional change to the NetHASP Configuration File:In the [NH_TCPIP] section, set NH_PORT_NUMBER =
Adapting NetHASP to NetBIOS
WHEN NETBIOS IS THE ONLY PROTOCOL
This section explains adaptation steps required in network environments where NetBIOS is the only protocol installed.
To adapt the NetHASP License Manager:
1. Load the NetHASP License Manager.
To adapt the NetHASP client:
* Edit the NetHASP Configuration File by setting NH_NETBIOS=Enabled in the [NH_COMMON] section.
WHEN MULTIPLE PROTOCOLS ARE AVAILABLE UNDER WINDOWS NT AND WINDOWS 95
This section explains adaptation steps required if multiple protocols are installed and the NetHASP License Manager is loaded on a Windows NT or Windows 95 station.
To adapt the NetHASP License Manager:
1. Load nhsrvwnt.exe.
Note: By default, the nhsrvwnt.exe listens to lana numbers (communication channels) 0 to 6. To change the default, use the -uselananum=
or-maxlananum= switch. To adapt the NetHASP client:
1. Edit the NetHASP Configuration File as follows:
In the [NH_COMMON] section, set NH_NETBIOS=Enabled.
2. Copy the NetHASP Configuration File to the application directory.WHEN MULTIPLE PROTOCOLS ARE AVAILABLE UNDER WINDOWS FOR WORKGROUPS AND WIN32S
If other protocols are installed, and the NetHASP License Manager is loaded on a Windows for Workgroups or Win32s station, synchronize the protocols between the NetHASP clients and the NetHASP License Manager.
To adapt the NetHASP License Manager:
1. On the computer where the NetHASP is connected, choose IPX/SPX compatible transport with NetBIOS to be the default protocol (see below for details).
2. Load nhsrvwin.exe, the NetHASP License Manager for Windows, with the -netbios switch.To adapt the NetHASP client:
1. Set the default protocol on all stations to IPX/SPX compatible transport with NetBIOS (see below for details).
2. Edit the NetHASP Configuration File as follows:In the [NH_COMMON] section, set NH_NETBIOS=Enabled
3. Copy the NetHASP Configuration File to the application directory.SETTING THE DEFAULT PROTOCOL
To change the default protocol on a station, follow the instructions below.
DOS STATIONS
Load the protocol drivers. DOS stations can work with only one active protocol.
WINDOWS AND WIN32S STATIONS
Load the protocol drivers in DOS.
WINDOWS FOR WORKGROUNDS STATIONS
1. Choose Network from the Program Manager.
2. Choose Network Setup to open the Network Setup dialog box.
3. Click Drivers to open the Network Drivers dialog box.
4. Select the desired protocol and click Set As Default Protocol.
5. Click Close then click OK.
6. Restart your system.WINDOWS 95 STATIONS
1. Choose Network from the Control Panel to open the Network dialog box.
2. Double-click the protocol name on the Configuration tab.
3. Choose the Advanced tab.
4. Check Set this protocol to be the default protocol and click OK.
5. Restart your system.WINDOWS NT STATIONS
1. Choose Network from the Control Panel.
2. Choose the Services tab.
3. Double-click the NetBIOS Interface to open the NetBIOS Configuration dialog box.
4. Edit the lana numbers so the default protocol you want will be associated with lana number 0000 and click OK.
5. Restart your system.Note: Nbf is NetBEUI. NwlnkNb is IPX/SPX-compatible with NetBIOS. NetBT is TCP/IP.
ADAPTING NETHASP TO THE NETWORK
Defining the Range of Stations under IPX
To learn how address files are used as an advertising mechanism, read the section “Adapting NetHASP to IPX without SAP” above.
To allow only some of the stations to access the key in an IPX- based network:
1. Load the NetHASP License Manager with the -ipxnosap switch. This ensures that the address of the NetHASP License Manager is not advertised via the SAP but saved in the haspaddr.dat and newhaddr.dat address files.
2. Copy both address files to a location where all stations in the required range have read permission.
3. Copy the NetHASP Configuration File to the application directory. Set the NetHASP Configuration File as follows:In the [NH_COMMON] section, set NH_IPX=Enabled * In the [NH_IPX] section, set NH_USE_SAP=Disabled * In the [NH_IPX] section, set NH_USE_BROADCAST=Disabled
4. This instructs the protected application running on stations in the range to search for the two address files and read the address of the NetHASP License Manager.Defining the Range of Stations under NetBIOS
To allow only some of the stations to access the key in a NetBIOS-based network:
1. Load the NetHASP License Manager with the -nbname switch set to a name of your choice (up to 8 characters, not case-sensitive). This defines the NetBIOS name of the NetHASP License Manager.
For example, to load haspserv.exe and define the NetBIOS name of the station as firstsrv, enter:
haspserv -nbname=firstsrv
2. Copy the protected application and the NetHASP Configuration File to the same directory. Make sure that each station in the range, and only stations in the range, load the application from this directory.
3. Set the NetHASP Configuration File as follows:* In the [NH_COMMON] section, set NH_NETBIOS=Enabled * In the [NH_NETBIOS] section, set NH_NBNAME=
,
whereis the name assigned to the NetHASP License Manager.
This links the stations to the NetBIOS name.Note: You cannot have two stations with the same NetBIOS name. If you want to load the NetHASP License Manager on more than one station, you must define a different NetBIOS name for each NetHASP License Manager.
Adapting the Timeout Length
The NetHASP License Manager cannot serve more than one request at a time. The timeout length determines how long a protected application repeatedly tries to access the NetHASP License Manager before giving up.
In almost all networks, the default timout values are sufficient, so you only need to change the default values in networks that have a NetHASP connected to a slow or busy station.
To define the timeout length:
In the appropriate section of the NetHASP Configuration File, set:
* NH_SESSION=
* NH_SEND_RCV= where m and n are measured in seconds. By default, m is 30 seconds and n is 5 seconds.
Defining the Number of Protected DOS Applications Served
The NetHASP License Manager for DOS allocates memory space for 250 protected applications (about 4KB). If necessary, you can save memory space by changing this default value.
To change the default memory space allocation:
* Load the NetHASP License Manager as follows:
haspserv -userlist=n
where n is the maximum number of protected applications.
Novell Local Networks and Internetworks
This section describes Novell networks that consist of several interconnected networks using the IPX protocol.
With the NetHASP system, local network is a flexible term. The NetHASP License Manager and NetHASP client (the protected application) refer to the local network differently. The NetHASP License Manager refers to the local network as all the segments directly connected to the NetHASP License Manager. The NetHASP client refers to the local network as the current segment.
An internetwork is a group of two or more local networks linked together.
The example below shows how you can set the NetHASP client and NetHASP License Manager to work on either a local or internetwork.
Adapting the NetHASP License Manager
The internetwork in our example has two file servers: File Server 1 and File Server 2. File Server 1 has two segments with network numbers 111 and 222. File Server 2 has two segments with network numbers 333 and 444.
By default, the NetHASP License Manager loaded on either File Server 1 or File Server 2 serves the entire internetwork. That means that if you load the NetHASP License Manager with no switches, it serves network segments 111, 222, 333, and 444.
If you want the NetHASP License Manager to serve only stations in the File Server 1 local network (stations on segments 111 and 222):
* On File Server 1, load haspserv.nlm with the -localnet switch as follows:
load haspserv -localnet
Now the NetHASP License Manager will not serve stations on segments 333 and 444.
If you want the NetHASP License Manager to serve only stations in segment 222:
* On File Server 1, load the NetHASP License Manager with the additional switch, -net, as follows:
load haspserv -localnet -net 222
Now the NetHASP License Manager will serve stations on segment 222, but not those on segments 111, 333, or 444.
Adapting the NetHASP Client
By default, a protected application searches for the NetHASP License Manager throughout the internetwork.
If you want the protected application to search only its local network for a NetHASP License Manager:
* Set the NetHASP Configuration File as follows:
In the [NH_IPX] section, set NH_SEARCH_METHOD=Localnet
If the protected application is running on a station in segment 222, the application finds the NetHASP License Manager on segment 222 only. The application does not search for a NetHASP License Manager that may be active in other local networks.
Related Documents
[color=red:364g81z1][u:364g81z1][b:364g81z1]HASPSERV Copy Protection Utility for
RAP HASP Programming Utility[/b:364g81z1][/u:364g81z1][/color:364g81z1][/url:364g81z1]
[color=red:364g81z1][u:364g81z1][b:364g81z1]Virtual HASP Copy Protection for Standalone[/b:364g81z1][/u:364g81z1][/color:364g81z1][/url:364g81z1]
- You must be logged in to reply to this topic.