Network License - Frequently Asked Questions

A: If you have a network license and your client computer is running Windows Vista, you simply need to enter the license server IP address or name into the lshost.txt file in the product folder on the Windows Vista client computer. This is the same as that on Windows XP.

If you are evaluating PCA software on Windows Vista, the software must run with administrator credentials. Please follow the steps below (the followings use pcaColumn as an example): (1) Click Windows Start | All Programs | PCA Programs | pcaColumn (2) Right click on pcaColumn menu group item (3) Select Run As Administrator from the pop-up menu. You will be prompted by the User Account Control. If you are a limited user on the computer, at this point you will need to type in administrator credentials. If you are already an administrator, however, you will simply need to click Continue to allow the software to continue.

A: Yes. Network licensing supports both Local Area Network and Wide Area Network (Internet). Client computers and license server can be physically located in different offices/cities. A client computer can obtain a license token from remote license servers through Internet. VPN connection is recommended for security.

A: In order to check out a license for PCA software from network to a portable computer (i.e. a laptop), the WCommute.exe and lsapiw32.dll files issued by pcaStructurePoint must be used on the portable computer. These two files are vendor specific. These two files issued by other software vendor cannot be used on a client computer to check out PCA software. Please refer to the Commute_Readme.txt on CD (folder License Server) for instructions.

Q: Network License - What is the difference between a commuter license and a remote commuter license?

A: Suppose you want to check out a license from your office network to a laptop computer. If during the checking out process, the laptop can be connected to the network, then the laptop is considered as a normal commuter client, and you need to refer to the Commuter License Guide on CD (in folder License Server | PDF) for instructions.

Suppose you want to check out a license from your office network to a desktop computer at home. Since the desktop computer cannot be connected to the office network during the checking out process, it is considered as a remote commuter client. You need to refer to the Remote Commute License Guide on CD (folder License Server | PDF) for instructions.

A: Yes. Please call us to request this feature. By default redundant licensing is not supported by a network license.

Q: Network License - I want my PCA software on client to do a broadcasting. What should I do?

A: Simply put LAN in the lshost.txt file. PCA software performs a broadcasting over the same subnet and retrieve a license token from the first available license server. Note that broadcasting cannot reach a license server located outside the subnet. If the license server is located in another subnet, IP address of the license server must be entered explicitly in the lshodt.txt on each client computer.

Q: Network License - I have multiple license servers. How can I config my client so that it rolls over to the next server if a server is down?

A: Simply put IP addresses of all your license servers in the lshost.txt file on client, one IP per line. PCA software tries all of them one by one until a license token is retrieved successfully. You can put LAN in the last line in case all the specified servers fail.

Q: Network License - I have the server name in the lshost.txt on client computer, but the client cannot find the server. What should I do?

A: Rainbow SentinelLM server software (located in the Network_License folder on our CD or available to download from our website) can be only installed on Win32 platforms (i.e. Windows NT/2000/XP). It cannot be installed on Novell server.

A: It works fine with Cisco Systems VPN, VPN of Windows Server 2003, and Aventail VPN. Other VPN systems have not been tested.

Q: Network License - Can the Network License Manager be located outside of subnet (WAN or another subnet)?

A: It is recommeded that the Network License Server and clients are in the same subnet. License Manager communicates by sending UDP packets on port 5093. If you want to go across different subnets, then you have to make sure that the routers do not block the packets and they allow two way communications. This is difficult to configure unless you have advanced router knowledge.

A: The SentinelLM network license manager runs on any Win9x, NT, ME, 2000, XP, and 2003 Server. Among Windows, Windows NT or later (2000, XP, 2003 Server) is recommended due to its support for Windows Services.

A: The SentinelLM Network License Manager (or server) is a System Service on Windows NT/2000/XP/2003 Server, and a Background service on Windows 95/98. On start up, the license manager reads and decrypts license keys from an initialization file. The license manager runs at the end user site, and grants or denies permission for a licensed application to run, based on its store of license codes. Each license code specifies a fixed number of keys that may be issued.

A: For Network License Manager, please select a PC that is stable (Windows NT or later) and is always available on the network (Laptops or Notebooks are not recommended).

Q: Network License - I have 5 network licenses now. But I would like to add 3 more. How do I do it?

A: License code is accumulative. After you receive license code for 3 more licenses, append the new license code to the end of the existing license code file (in a new line) and restart the license manager service or reboot the server.

Q: Network License - What happens to my license server if an application crashes?

A: Once invoked, the application will periodically confirm its continued existence to the license manager by sending a heartbeat while the application is still executing. If the application or machine crashes for any reason, the license will be returned to the server or pool in approximately 5 to 10 minutes without requiring end user intervention.

Q: Network License - What happens when I have other products using Sentinel License Manager installed?

A: Sites where a Sentinel License Manager is already installed can append the new license codes to the end of the existing license code file and restart the license manager. SentinelLM 7.2.0.0 or higher is required.

A: Commuter Licensing allows an end user the ability to check out and check in a license authorization from a network server. When a Commuter typically checks out a license from his/her laptop, it decrements the hard limit by one on the network server or pool, and a temporary standalone license is created on the laptop. Please refer to Commuter License Guide document on CD (in the License Server | PDF folder).

Q: Network License - What should I do if I get error#17, while installing license through Client Activator?

A: When adding a standalone license, you can ignore this error. To add a Network license, set the Environment variable LSFORCEHOST to the IP address or the name of the machine on which your SentinelLM server is running.

Q: Network License - I have exited my application, but my license has not been released. Why?

A: There is a �hold-time� for 1 minute for released license. That means for the next 1 minute it is available ONLY to you. After the 1-minute hold, it is available to other users.

Q: Network License - I get �Clock Tampering Detected� message when I try to run evaluation version?

A: If the 15-day evaluation version detects any clock tampering activity, it permanently disables itself. Contact us at support@pcaStructurePoint.com to enable the application.