Operating Systems: All supported Operating Systems
Products: COMPRESS (versions 7140 and older)
HASP License Manager for Win32 is the application/service that is required to be running on the key server computer (the computer that has the red network key attached to it).
This can be installed as an application or as a service. The COMPRESS Setup installs HASP License Manager for Win32 as a service. The service executable is nhsrvice.exe and it resides in the %SystemRoot\System32 folder. The service name is "HASP Loader".
Older versions of COMPRESS installed HASP License Manager for Win32 as an application. The application executable is NHSRVW32.exe which is installed to the %SystemRoot\System32 folder.
HASP License Manager for Win32 can also be installed by running the HASP License Manager (lmsetup.exe), available from the HASP USB Security Key Utilities Downloads Area (must sign in for link to work).
COMPRESS client computers communicate with the HASP License Manager for Win32 on the key server computer. The default communication port is UDP port 475. By default, the TCP/IP broadcast mechanism is enabled. If your network has HASP License Manager for Win32 running on multiple computers, COMPRESS could randomly get a response from a HASP License Manager for Win32 that may not have the Codeware key attached to the key server. This results in an error message that says "COMPRESS cannot find a network (red) key attached to the key server computer".
You must configure your nethasp.ini file on all COMPRESS client machines under the following conditions (newer versions of COMPRESS do this automatically) :
See How do I obtain and customize the Nethasp.ini file on the COMPRESS "client" computers to specify the network address of the Key Server? for more information on configuring a nethasp.ini.
The COMPRESS Setup creates Windows Firewall rules to allow HASP LM traffic on TCP/UDP port 475. If you have any other firewall running on the server or network, you will have to permit traffic on these ports and/or allow nhsrvice.exe traffic. The communication port and protocol can be customized in the nethasp.ini file. If you do change the communication port, make sure the firewall permits traffic on that port.