USB Network Locks
There are three basic steps in the hardware lock installation process:
- Installing the hardware lock software
- Installing the lock itself
- Running the Enable Wizard
An explanation of each of these steps is outlined below.
NOTE – The hardware lock contains an electronic circuit board, so handle it with care throughout the installation process or at any time when it becomes necessary to transfer or handle the lock.
STEP 1:
Hardware Lock Software Installation
You can download the latest drivers (Sentinel Protection Installer 7.5.0) for your server here. This software needs to be installed once on the computer where the hardware lock resides (server computer) - No drivers are necessary on the computers that will run your modeling-software (personal computer) as long as you have a working netenble.001 file. For the formatting of the netenble.001 file, see below.
Action:
- Download the Sentinel Protection Installer from the link above and run on the server computer.
- Follow the prompts and select the complete installation.
- Select Yes to allow firewall modification when prompted to.
- Close any programs currently in use as you will have to restart the machine after the installation in order for the new drivers to take effect.
- Check the netenble.001 files on all of the personal computers that have your modeling software installed.
STEP 2:
Installing the lock itself
Connect the lock to the USB port on your computer.
Action:
Attach the hardware lock to the USB of your server computer.
You can check to see if your personal computer is properly set up to detect the hardware lock on the server computer by opening a internet browser on your personal computer and type in the following address including your server computer's IP address: http://(server IP address):6002
For example if your server computer's IP address is 111.222.3.44 then the address would read : http://111.222.3.44:6002
To find your server computer's IP address you can follow these steps in Windows:
- Click the start menu and select Run…
- Type "cmd" to open a DOS command Prompt
- Type "ipconfig" into the command prompt and view the IP address listed below
STEP 3:
Verify the Installation using the Enable Wizard
The enable wizard automatically enables your modeling package. It will search
for your hardware lock and the associated drivers. Once they have been found, your software is configured to work according to the modules that you purchased.
Action:
- Start the XMS software.
- If the Enable Wizard doesn't appear, go to File | Register.
- Click the Enable Wizard button.
- Select Network hardware lock and click Next.
- Set the desired network lock settings. Consult the troubleshooting guide for more information.
- Click Next and then click Finish.
Troubleshooting
If you have followed the above instructions, and the XMS software will not enable, it is most likely that you either have a password file that is conflicting with the hardware lock, or your netenble.001 file is missing or formatted incorrectly.
Password files in GMS:
Search your computer for a file called gmspass.txt and rename or delete it.
Password files in WMS 8.0 or older:
Search your computer for a file called wmspass.txt and rename or delete it.
Password files in WMS 8.1:
1. Go to Start | Run and type "regedit"
2. Navigate to HKEY_CURRENT_USER | Software | EMRL
3. You should see an entry called wmspassword81
4. Delete or rename it to something like _wmspassword81 (that way if you need it again in the future you can recover it)
Password files in SMS 9.2:
1. Go to Start | Run and type "regedit"
2. Navigate to HKEY_LOCAL_MACHINE | Software | EMRL
3. You should see an entry called smspassword92
4. Delete or rename it to something like _smspassword92 (that way if you need it again in the future you can recover it)
Password files in SMS 10.0:
1. Go to Start | Run and type "regedit"
2. Navigate to HKEY_CURRENT_USER | Software | EMRL
3. You should see an entry called smspassword100
4. Delete or rename it to something like _smspassword100 (that way if you need it again in the future you can recover it)
Netenble.001 File
With SMS 10.0, GMS 6.5, and WMS 8.1, users can specify the IP address of the server as the first word of the netenble.001 file, or they can be registered as an exception in the windows firewall if they prefer to search for a server.
Occasionally an administrator installs the XMS software, and a different user without administrative privileges tries to enable the software but is unable to do so because he/she cannot write to the Program Files directory. If this is the case, an administrator will have to enable the software using the enable wizard or create the netenble.001 file by hand.
The netenble.001 file can also be created by hand in a text editor and saved with the .001 extension. Here are the full instructions in the .001 file.
111.222.3.44 (Get license from this IP address or host name only.) *
DEFAULT (Use default mode, same as an empty file.) ***
RNBO_SPN_ALL_MODES (Get license from local lock, then from network broadcast.) *,**
RNBO_SPN_SERVER_MODES (Get license from network broadcast only.) *,**
RNBO_SPN_LOCAL (Get license from local network lock server only.) ****
RNBO_STANDALONE (Get license from local lock only)
RNBO_SPN_DRIVER (Get license from local lock only)
The netenble.001 file can contain the above lines in any order, but only the first word of the file specifies the mode of lock access. If that mode of access fails, then DEFAULT is tried. If DEFAULT fails, then ALL_MODES is tried.
A writable netenble.001 file is overwritten with the mode which succeeds in order to shorten the next attempt
* Network requires a network lock server to be running on some host
** Broadcasting requires a client firewall exception for the application.
*** DEFAULT uses the sntlconfig.xml file if it exists, otherwise it uses the NSP_HOST environment variable if it is set, otherwise it uses RNBO_SPN_ALL_MODES
**** LOCAL requires a lock server to be running on the local system
This file no longer accepts content similar to:
PROTOCOL:IPX/SPX
PROTOCOL:NETBIOS/NETBUI
PROTOCOL:LOCAL
PROTOCOL:
MASK:255.255.255.0
xmslicensing.txt
If your hardware lock is still not working for you, create a file called xmslicensing.txt on C:\. This works for software build dates of June 2008 and later. If this file is present when XMS starts, diagnostic information about licensing will be appended to the file. After opening your xms software, send a copy of this file to tech support for troubleshooting. When finished, be sure to delete the file, otherwise the file will just grow bigger and bigger each time XMS is started.
If you were unsuccessful in enabling your software, please contact Tech Support.
