Sie sind auf Seite 1von 6

--------------------------------------------------------------------------Red Network Hardware Lock Setup Instructions

--------------------------------------------------------------------------Table of Contents
A. General information about Red Network ESLs.
B. Procedure if the Red Network ESL is attached to a Windows NT4/2000/XP/2003 m
achine.
C. Procedure if the Red Network ESL is attached to a Novell 4.x/5.x/6.x Server
D. What Operating Systems do different versions of COADE programs support.
E. What protocols do different versions of COADE programs support.
F. How do I determine what protocols are running on my machine.
G. Steps to perform if you are having trouble accessing the Red Network ESL.
--------------------------------------------------------------------------A. General information about Red Network ESLs.
--------------------------------------------------------------------------1. The Red Network ESL should be setup by a person who is FAMILIAR with
Windows based networks such as your Network Administrator. If you are
not familiar with concepts such as Network Protocols, Broadcast,
IP Addresses, TCP, UDP, and Windows Services, please do not attempt
to setup the Red Network ESL.
2. The Red Network ESL does NOT have to be attached to the Network Server.
COADE recommends attaching the Red Network ESL to a machine that is
always up and running, can be re-booted without impact to users,
and is not the primary machine for any user on the network.
3. The information provided in this file is a supplement to the
NetHasp Documentation file called NETHASP.PDF in the "..\ASSIDRV"
directory. Please review NETHASP.PDF file for any issues not
addressed in this file.
4. If you install a COADE application on a network drive for many users
to access, please make the ..\SYSTEM directory under the COADE
application directory has read/write privileges for all users.
COADE applications write temporary files to the ..\SYSTEM directory
that pertain to the install. For CADWorx, the ..\SUPPORT directory
also needs to have read/write privileges for all users.
5. Some of the steps below are automatically performed by the installation.
They are listed here for your reference only. All files referenced
can be found in the "..\ASSIDRV" directory under the program directory.
-------------------------------------------------------------------------------B. Procedure if the Network ESL is attached to a Windows NT/2000/XP/2003 machin
e
-------------------------------------------------------------------------------1. You must have ADMINISTRATOR level privileges to perform these steps.
2. Attach the Red ESL key to the parallel port or USB port of the machine.
3. Execute "LMSETUP.EXE" on the machine where the key is attached.
Follow the on screen instructions. Install the NetHASP License Manager as
a service.

4. The NetHasp License Manager will automatically start every time the
user re-boots the machine. This occurs because the NetHasp License
Manager is setup as a start up service inside Windows NT/2000/XP/2003.
To verify that this has occurred, go to
Windows Start Button->Settings->Control Panel->Services Icon.
In the Services dialog box, there should be an entry called "HASP Loader".
The HASP Loader Service will start even if no one logs into the machine.
6. Determine what protocols the NetHasp License Manager is listening to.
The NetHasp License Manager will display a message such as:
"Server is listening to IPX : Loaded"
"Server is listening to TCP/IP : Loaded"
"Server is listening to NetBIOS : loaded"
7. The "loaded" means that this protocol is active on the machine.
Hit the Activity Log pull down menu. This will bring up the activity
log which will confirm what protocols are loaded. Do not be alarmed
if the activity log says that "NHSRV.INI" file not found.
8. The Activity Log has a box in the top left that will allow you to
bring up just the information specific to each protocol. Bring up the
Activity Log for the protocol you want to use. Make sure there are
no error messages here.
a. For NetBIOS protocol, the Activity Log should say something like
"Listening on Lananum-> 0, 1 ".
b. For IPX protocol, the Activity Log should say something like
"haspaddr.dat were created" and "Listening ...".
c. For TCP/IP Protocol, the Activity Log should say something like
"Server IP address: 111.111.111.111"
"Server Host Name: PDC_NT01"
9. Determine what protocol you want to use for accessing the key.
10. To speed up response time to the Network key, you may "unload"
the any protocols that you are not planning on using with the
NetHasp License Manager. This can be done from the Remove pull down menu.
11. Follow the instructions below for the protocol you want to use:
i. TCP/IP Protocol procedure:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a. To configure this protocol, you must know the IP address
of the machine where the Red Network Key is attached.
Example: 111.111.111.111
b. Modify the NETHASP.INI file in the "..\ASSIDRV" directory with
the following changes.
[NH_COMMON]
NH_TCPIP = Enabled
[NH_TCPIP]
NH_SERVER_ADDR = 111.111.111.111
NH_USE_BROADCAST = Disabled
You may also have to modify other entries in [NH_TCPIP] Section
depending on your network setup. The most common entries to
modify are: NH_TCPIP_METHOD
c. Copy the NETHASP.INI file into the program executable directory.
Example: (C:\CAESAR, C:\TANK, C:\CODECALC, C:\PVELITE).
For CADWorx, copy into AutoCAD EXE (Acad.exe) directory.
Example: AutoCAD 2002 - (C:\Program Files\AutoCAD 2002)
Example: AutoCAD 2004 - (C:\Program Files\AutoCAD 2004)
Example: AutoCAD 2005 - (C:\Program Files\AutoCAD 2005)

Example: AutoCAD 2006 - (C:\Program Files\AutoCAD 2006)


d. Start the COADE application.
ii. NetBIOS Protocol procedure:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a. Modify the NETHASP.INI file in the "..\ASSIDRV" directory with
the following changes.
[NH_COMMON]
NH_NETBIOS = Enabled
You may also have to modify the [NH_NETBIOS] Section
depending on your network setup.
b. Copy the NETHASP.INI file into the program executable directory.
Example: (C:\CAESAR, C:\TANK, C:\CODECALC, C:\PVELITE).
For CADWorx, copy into AutoCAD EXE (Acad.exe) directory.
Example: AutoCAD 2002 - (C:\Program Files\AutoCAD 2002)
Example: AutoCAD 2004 - (C:\Program Files\AutoCAD 2004)
Example: AutoCAD 2005 - (C:\Program Files\AutoCAD 2005)
Example: AutoCAD 2006 - (C:\Program Files\AutoCAD 2006)
c. In the Control Panel, double click the Network Icon. In the Network
dialog box, hit the services tab. Double click the
"NetBIOS Interface"
d. This will bring up the NetBIOS configuration dialog box with
the Lana numbers associated with each protocol. Lana Number
"000" has to be associated with "Nbf" The "Nbf" stands for NetBIOS.
If "Nbf " is not with "000", swap it out with what is set to "000".
After completing, hit "Ok" on the NetBIOS configuration box.
e. Hit "Ok" on the Network Dialog box.
f. Steps c, d, and e may need to be repeated on all machines that want
access to the Red Network ESL.
g. Start the COADE application.
iii. IPX Protocol procedure:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a. This protocol requires a address data file to work.
b. The data file is created in the directory from where
the NetHasp License Manager was started on the Novell Server.
The file is called HASPADDR.DAT.
c. Modify the NETHASP.INI file in the "..\ASSIDRV" directory with
the following changes.
[NH_COMMON]
NH_IPX
= Enabled
You may also have to modify the [NH_IPX] Section
depending on your network setup.
d. Copy HASPADDR.DAT file and the NETHASP.INI into the Executable director
y.
Example: (C:\CAESAR, C:\TANK, C:\CODECALC, C:\PVELITE).
For CADWorx, copy into AutoCAD EXE (Acad.exe) directory.
Example: AutoCAD 2002 - (C:\Program Files\AutoCAD 2002)
Example: AutoCAD 2004 - (C:\Program Files\AutoCAD 2004)
Example: AutoCAD 2005 - (C:\Program Files\AutoCAD 2005)
Example: AutoCAD 2006 - (C:\Program Files\AutoCAD 2006)
e. The HASPADDR.DAT file is regenerated every time the NetHasp License
Manager is started and stopped. Thus, the user may have to copy
the file to the executable directory every time they shut-down and
re-start the Novell Server. This is why we recommend that the key
be attached to a machine that is never shut down.
f. Start the COADE application.
-------------------------------------------------------------------------------

C. Procedure if the Red Network ESL is attached to a Novell Server 4.x/5.x/6.x


------------------------------------------------------------------------------1. The NetHASP License Manager for Novell NetWare servers is HASPSERV.NLM
Only the IPX protocol can be used with Novell Server 4.x/5.x.
IPX or TCP/IP can be used Novell Server 6.x.
2. Copy HASPSERV.NLM to the SYS:SYSTEM directory of the Novell file server.
3. Load the NetHASP License Manager, by entering: LOAD HASPSERV
The NetHASP License Manager screen appears showing the
that the IPX protocol is being used.
4. To load the NetHASP License Manager automatically, add the line
LOAD HASPSERV to the AUTOEXEC.NCF file in the SYS:SYSTEM directory.
5. By default, a NetHASP address file (HASPADDR.DAT)
is created in the directory of the NetHASP LM. When using
HASPSERV.NLM, the address file is created in the server root
directory. The COADE program may require this file to quickly access
the Red Network Lock. The COADE program searches for the address
file in the following order:
a. Current directory
b. Windows directory
c. Windows system directory
d. Directory from where the application is activated.
e. Path
f. NetWare search map
6. Modify the NETHASP.INI file in the "..\ASSIDRV" directory with
the following changes.
[NH_COMMON]
NH_IPX = Enabled
You may also have to modify the [NH_IPX] Section
depending on your network setup.
7. Copy HASPADDR.DAT file and the NETHASP.INI into the Executable directory.
Example: (C:\CAESAR, C:\TANK, C:\CODECALC, C:\PVELITE).
For CADWorx, copy into AutoCAD EXE (Acad.exe) directory.
Example: AutoCAD 2002 - (C:\Program Files\AutoCAD 2002);
Example: AutoCAD 2004 - (C:\Program Files\AutoCAD 2004)
Example: AutoCAD 2005 - (C:\Program Files\AutoCAD 2005)
Example: AutoCAD 2006 - (C:\Program Files\AutoCAD 2006)
8. The HASPADDR.DAT file is regenerated every time the NetHasp License
Manager is started and stopped. Thus, the administrator may have to copy
these files from the Server to the executable directory every
time they shut-down and re-start the Novell Server. The directory of the
DAT files can be specified in the NETHASP.INI file if you do not wish
to copy the DAT files.
[NH_IPX]
NH_DATFILE_PATH = <path>
--------------------------------------------------------------------------D. What Operating Systems do different versions of COADE programs support.
--------------------------------------------------------------------------|-------------|----------------|--------------------------------------------|
|Program
|Version
| Operating System
|
|-------------|----------------|--------------------------------------------|

|CAESAR II
|4.00 or Later | Windows 95/98/ME or NT4/2000/XP/2003
|
|CODECALC
|6.00 or Later | Windows 95/98/ME or NT4/2000/XP/2003
|
|PV Elite
|3.10 or Later | Windows 95/98/ME or NT4/2000/XP/2003
|
|CADWorx
|2.00 or Later | Windows 95/98/ME or NT4/2000/XP/2003
|
|TANK
|2.00 or Later | Windows 95/98/ME or NT4/2000/XP/2003
|
|-------------|----------------|--------------------------------------------|
|CAESAR II
|3.24
| DOS, Windows 3.1x, 95, NT 3.51, NT 4.00
|
|CODECALC
|5.60
| DOS, Windows 3.1x, 95, NT 3.51, NT 4.00
|
|PV Elite
|3.00
| DOS, Windows 3.1x, 95, NT 3.51, NT 4.00
|
|CADWorx
|1.10
| DOS, Windows 3.1x, 95, NT 3.51, NT 4.00
|
|TANK
|1.51
| DOS, Windows 3.1x, 95, NT 3.51, NT 4.00
|
|-------------|----------------|--------------------------------------------|
|CAESAR II
|3.23 or Earlier | DOS
|
|-------------|----------------|--------------------------------------------|
Note:
Operating System support only applies to the hardware lock.
Older versions of COADE products may not work on a new operating system.
--------------------------------------------------------------------------E. What protocols do different versions of COADE programs support.
--------------------------------------------------------------------------|-------------|----------------|---------|---------|---------|
|Program
|Version
| TCP/IP | NETBIOS | IPX |
|-------------|----------------|---------|---------|---------|
|CAESAR II
|4.00 or Later | YES | YES | YES |
|CODECALC
|6.00 or Later | YES | YES | YES |
|PV Elite
|3.10 or Later | YES | YES | YES |
|CADWorx
|2.00 or Later | YES | YES | YES |
|TANK
|2.00 or Later | YES | YES | YES |
|-------------|----------------|---------|---------|---------|
|CAESAR II
|3.24 or Earlier | NO
| YES | YES |
|CODECALC
|5.60 or Earlier | NO
| YES | YES |
|PV Elite
|3.00 or Earlier | NO
| YES | YES |
|CADWorx
|1.10 or Earlier | NO
| YES | YES |
|TANK
|1.51 or Earlier | NO
| YES | YES |
|-------------|----------------|---------|---------|---------|
--------------------------------------------------------------------------F. How do I determine what protocols are running on my machine.
--------------------------------------------------------------------------Windows 95/98/ME procedure:
~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Go to the Windows Start Button->Setting->Control Panel
2. Double Click on the Network Icon in the Control Panel
3. In the Network Dialog that appears, click on the Configuration tab.
4. A box will appear that will list the Network Protocols that are installed
a. "NETBEUI" means that NETBIOS Protocol is installed.
b. "TCP/IP" means that TCP/IP Protocol is installed.
c. "IPX/SPX-compatible Protocol" means that IPX Protocol is installed
5. If a protocol that you want to use is missing than, you may have to use
"Add Button" to add it to this machine.
Windows NT/2000/XP/2003 procedure:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Go to the Windows Start Button->Setting->Control Panel

2. Double Click on the Network Icon in the Control Panel


3. In the Network Dialog that appears, click on the Protocols tab.
4. A box will appear that will list the Network Protocols:
a. "NETBEUI Protocol" means that NETBIOS Protocol is installed.
b. "TCP/IP Protocol" means that TCP/IP Protocol is installed.
c. "NWLink IPX/SPX Compatible Transport" means that IPX Protocol is
installed
5. If a protocol that you want to use is missing than, you may have to use
"Add Button" to add it to this machine.
--------------------------------------------------------------------------G. Steps to perform if you are having trouble accessing the Red Network ESL.
--------------------------------------------------------------------------1. Verify that the NetHasp License Manager is running on the machine where
the Red Network ESL is attached.
2. Verify the Protocols that NetHasp License Manager is broadcasting.
Make sure that these protocols are installed on the Client machines.
For example, if NetHasp License Manager is broadcasting only on NetBIOS,
the Client machine must also have NetBIOS installed.
3. Run the Monitor Utility that is in the ".\ASSIDRV\Monitor\" directory.
If Monitor cannot find the Red Network ESL, than the COADE application
will not find the Red Network ESL
---------------------------------------------------------------------------===