Problem 1: The PC used as a network plug server has Windows 95 operating system, and plug driver should be started manually after server reboot

Solution: On the server, copy NHSRVW32.EXE to the SYSTEM directory in the  Windows root directory (c:\WINDOWS\SYSTEM).

Create NHSRVW32.EXE shortcut in the Startup group of the Start menu. (Open Windows Explorer, find and select c:\WINDOWS\SYSTEM\NHSRVW32.EXE file. Right-click on Start button, choose Explore, open folder Programs, then subfolder Startup. Drag&Drop c:\WINDOWS\SYSTEM\NHSRVW32.EXE file to StartUp folder.)

Restart the computer. Now you may remove insalation CD from server, and HASP manager should start automatically after login to windows (please note - not after server OS loading, as in WinNT, but after successful user login).

 

Problem 2: “HASP Plug can’t be found” on Windows 2000, XP

Installation is completed, but RAM Commander can’t be started and gives error message about Local and Network Plugs.

Solution:

You should install new HASP plug drivers. If you have our installation CD, open folder “\HASP\Driver Ver. 4.99" and start file HDD32.EXE. Install the driver for Parralel port and reboot your computer. If you have no CD, please ask your RAM Commander suppliers for the new plug driver version 4.99.

If 4.99 version driver does not help, please try to install HASPUserSetup.exe driver from the installation CD “\HASP\Driver HL” folder.

Another option is to download the latest HASP driver from ALD web site: https://www.aldsoftware.com/download/download/HASPUserSetup_6x21.exe.

 

Problem 3: “HASP Plug can’t be found” in segmented network / VLAN

Solution:

License Manager developers give the following solution:

  a) There is a file nethasp.ini.

  b) Place this file to RAMC32\BIN folder.

  c) Open this file with Notepad.

  d) Find section [NH_TCPIP] (line 96), find key NH_SERVER_ADDR = 111.111.111.111,

  e) modify its value to the License server's IP address, for example NH_SERVER_ADDR = 192.114.176.65

  f) save the file

RAM Commander should be able to find the plug.

 

There could be some more surprises in the network:

 

The server has more than 1 network adapter

If after steps from a) to f) you still have the same message about "plug not found", and you have a possibility that some computers are connected through other network adapter, do the following:

 

  g) There is a file nhsrv.ini.

  h) On the server, place this file to license manager folder, where the executable is.

  i) Open this file with Notepad.

  j) Find section [NHS_SERVER] (line 12), find key NHS_ADAPTER_IP, remove ";" comment sign from the left site, and write network adapter data like is shown in comments (<IpAddr-SubMask> [, <IpAddr-SubMask> ...]). Network administrator should assist you.

  k) save the file

  l) reboot the server

 

If after steps from a) to l) you still have the same message about "plug not found", there could be problems with server ports.

You should consult the network administrator about specific ports.

In the file nethasp.ini there are key NH_PORT_NUMBER (exactly after the key NH_SERVER_ADDR we modified in paragraph 3). Remove ";;" from the left side and set the TCP/IP port number. This is optional. The default number is 475.