USB NetHASP Network License
USB NetHASP Mastercam Network License Remote Access
When using Mastercam from home rather than at your workplace, you can take advantage of the remote access capability of the red USB NetHASP network license key. This requires access to the license server, which is achieved via a VPN (Virtual Private Network) connection. Additionally, you need to modify the nethasp.ini file to directly point to the NetHASP server's IP address. Each installed version of Mastercam requires separate modification of its .ini file, as each installation is independent of the others.
Instructions:
- Download the necessary files:
Download nethasp.zip from this link: https://downloads.mastercam.com/public/drivers/nethasp.zip - Extract the nethasp.ini file to either the Documents folder or your desktop.
- Edit the nethasp.ini file: Right-click the file and select Edit. The file will open in Notepad.
- Update the IP address at NH_SERVER_ADDR = to correspond to the NetHASP server's IP address.
- Save the changes: click File > Save As, ensure the file name is nethasp.ini and the file type is All Files.
- Move the modified file: Copy the modified nethasp.ini file and paste it into the Mastercam main directory (C:\Program Files\Mastercam 202X\Mastercam).
- When prompted with "A file named nethasp.ini already exists in this location," choose Replace the file in the destination.
Notes:
License Server Changes:
Remote access does not require changes on the license server. If the license works throughout the network and VPN clients can access ports 475 and 1947 on the server, remote use of Mastercam from the license server is possible. Check firewall settings to ensure remote and local connections are handled in the same manner.
Local Use:
If you wish to use the USB NetHASP key locally, the machine must have the license management software. Download the installer from here. During installation, choose to install the license server as a service.
RDP Connection:
An RDP remote desktop connection (Remote Desktop Protocol) can be used on the office machine. This works because the remote machine maintains a direct connection to the network's license server, though it is not the optimal solution.