2b. Will HyperChem run as networked on Windows?

General Comments

Yes, in general, HyperChem runs in networked mode. HyperChem uses "network license server" technology to obtain one of a fixed number of floating licenses in a network situation. In particular, HyperChem 5 can use any of the following transport protocols to obtain a license from a license server: NetBIOS/NetBEUI/NetAPI, IPX/SPX, TCP/IP. HyperChem 4 and 4.5 cannot use TCP/IP.

If you are setting up HyperChem in networking mode, you will have to install (a) the hardware lock driver and (b) a license server program.

(a) The hardware lock driver is analogous to a printer driver. It is software which controls a device attached to your computer port. It just has to be installed once and does not have to be running constantly. Information on the driver is available in the "Drivers" folder on the HyperChem 5 CD.

(b) The license server program is the software which controls the number of people who can access HyperChem at any given time. The license server will have to be installed on a machine on the network; this machine will also have the hardware lock attached. The network setup is described in more detail in the "Network Administrator's Guide" (releases 4 and 4.5) plus the accompanying addendum sheet (in the case of HyperChem 5). These items, along with the network dongle, are included in the networked HyperChem package.

Please note that the server program must always be running during the time that HyperChem 4, 4.5 or 5 will be accessed by any of the network machines. The correct server program to run depends on the operating system of the server machine, i.e. the one to which the hardware lock is attached:

These network servers are described in the Network Administrator's Guide booklet... except for the new 32-bit server, NSRVGX which we discuss below in more detail.

The hardware lock (dongle) and the software to drive it, AND the license server program are all manufactured by a third party -- Rainbow Technologies, Inc. Information on the latest update for the driver or server software can be obtained from the Hypercube Support Desk ( support@hyper.com) or Rainbow's web site, http://www.rnbo.com/TECH.

NSRVGX (32-bit server)

NSRVGX is the license server program running in a common networking situation: networking on Windows 95 or Windows NT. You can run networked HyperChem 4, 4.5 or 5 on such a platform.

To run NSRVGX, place it in a "Servers" folder on your main drive. After the HyperChem software and the hardware lock driver are installed double-click on NSRVGX.EXE (in Win 95 or WinNT). You will see a box appear with the message "Loading... please wait" message.

After a minute or maybe five, depending on the complexity of your network, this box disappears and you will just have "NetSentinel" displayed. It will show license requests in its panel. It can be shrunk down to appear in the Status panel if you prefer by clicking once on the "resize" box.

To test the license server display panel, go to where you have installed HyperChem on another network machine. If you are installing HyperChem 5, access the File/Preferences/Network License dialog box, select one transfer protocol option which applies to your network, and then close this dialog. (If you have an earlier version of HyperChem, it is not possible to specify the transfer protocol via a dialog box.) Then try access the license by choosing a menu item such as Help/About HyperChem. You should see "Hardware lock not detected. Attempting to acquire a network license to run HyperChem" in the status line of the HyperChem window. This will last for a minute, maybe more, maybe less, depending on the size and complexity of your network. Then the "About box" will be displayed, and you will know that HyperChem is accessing its lock properly.

After a minute or two the NetSentinel license manager should update its display to show one license is in use.

Now you are running networked HyperChem!

Notes and known bugs:

(1) the license manager may not show an instance of HyperChem being run on the same machine - this has no effect on running HyperChem;

(2) in some cases, the HyperChem network license manager may not handle multiple protocols designated under File/Preferences/Network License - this may be overcome by designating only *one* of the available protocols;

(3) if you are using the net lock as a "stand-alone" it acquires the license through "Local Access" so you do not have to be running NSRVGX to acquire a license although the dongle must be in place - you will notice "Local Access" has been automatically set in the File/Preferences/Network License dialog;

(4) occasionally the server does not release a license properly. In this case, start up "winmon" (also in the "License" folder on the HyperChem 5 CD) and force it to release. (Winmon is a diagnostics program provided by Rainbow Technologies.);

(5) For Windows NT 4, we have observed that the dongle device driver must be running on the Client machine as well--even though the net dongle is installed on the Server machine.

NetSentinel WIN32 Server Command Line Options:

/DN:string - Department Name, change name of server to string.
/H:num - Defines the number of entries in handle table.
/MS:num - Defines a maximum number for the number of servers running on the network.
/N:string - Server name override
/ST - Strict timeout enforcement.
/SN:num - Define number of NetBIOS/NETBEUI sessions (threads).
Default is 4 sessions. /SN:0 = no NetBIOS support.
/SW:num - Defines number of NWLINK(IPX/SPX) sessions (threads).
Default is 4 sessions. /SW:0 = no NWLINK support.
/SI:num - Defines the number of TCP/IP sessions.
Default is 4 sessions. /SI:0 = no TCP/IP suport.
/SL:num - Defines the number of entries in sub-license table.
/BI:mask - Override the default "Find-Server" UDP broadcast mask
(current set at 255.255.255.255). The form is "255.255.255.0" as an example...
/RI:num - Defines the number of times to retry finding the currently specified Rainbow TCP/IP servers running on the network.
/TI:num - Defines the timeout value when attempting to locate other Rainbow TCP/IP servers running on the network.
/W: - defines the delete handle password.

NetBIOS/NETBEUI Lana Num Configuration on Server and Client PCs:

If you are using the NetBIOS or NETBEUI protocols, you must configure the network setting for Lana Number 0 the same on all machines talking to a server including the server PC.

The 16-bit NetSentinel Servers and 16-bit NetSentinel Client Libraries use ONLY Lana Number 0.

How to view and modify the Lana Number Settings:

Go into Control Panel. Start the Network Icon applet. A dialog box titled "Network Settings" will appear.

In the list box titled "Installed Network Software" select "NetBIOS Interface". Click on the Configure button.A new dialog will display the current Lana Number Settings. The Nbf protocol is NETBEUI and the NwlnkNb protocol is NWLINK NetBIOS.

Security Servers

[Products] [Sales] [Support] [Science] [News] [Corporate] [Search] [Home]

(c) 2003, Hypercube, Inc. All Rights Reserved.
1115 NW 4th Street, Gainesville, FL 32601 USA
Phone (352) 371-7744 Fax (352) 371-3662 email info@hyper.com