Transcription
OrCAD Network LicensingNetwork Licensing Guide
Copyright 1998 OrCAD, Inc. All rights reserved.TrademarksOrCAD, OrCAD Layout, OrCAD Express, OrCAD Capture, OrCAD PSpice, andOrCAD PSpice A/D are registered trademarks of OrCAD, Inc. OrCAD Capture CISand OrCAD Express CIS are trademarks of OrCAD, Inc.Microsoft, Visual Basic, Windows, Windows NT, and other names of Microsoftproducts referenced herein are trademarks or registered trademarks of MicrosoftCorporation.Microsoft, MS-DOS, Windows, Windows NT and the Windows logo are eitherregistered trademarks or trademarks of Microsoft Corporation.Adobe, the Adobe logo, Acrobat, the Acrobat logo, Exchange and PostScript aretrademarks of Adobe Systems Incorporated or its subsidiaries and may be registeredin certain jurisdictions.FLEXlm is a registered trademark of Highland Software, Inc. Highland productscontain certain trade secrets and confidential and proprietary information of HighlandSoftware, Inc., and Globetrotter Software. Use of this copyright notice isprecautionary and does not imply publication or disclosure. No part of thispublication may be reproduced, transmitted, transcribed, stored in a retrieval system,or translated into any language in any form by any means without the writtenpermission of Highland Software, Inc., and Globetrotter Software.The HASP system and its documentation are copyrighted by Aladdin KnowledgeSystems Ltd. (C) 1985 to present. All rights reserved.HASP and MemoHASP are registered trademarks of Aladdin Knowledge SystemsLtd.NetHASP , MacHASP , DataHASP , TimeHASP , SerialHASP Hasp36 ,MemoHASP36 , NetHASP36 , OpenHASP , HASPCard , and AladdinCARD are trademarks of Aladdin Knowledge Systems Ltd.EENET is a trademark of Eckert Enterprises.9300 SW Nimbus Ave.Beaverton, OR 97008 USA
A ll other brand and product names mentioned herein are used for identification purposes only,and are trademarks or registered trademarks of their respective holders.60-30-670First edition 30 November 1998Technical Support: (503) 671-9400Technical Support email:techsupport@orcad.comCorporate offices:(503) 671-9500World Wide Web:http://www.orcad.comFax:(503) 671-9501General email:info@orcad.comOrCAD Japan K.K.:81-45-621-1911OrCAD UK Ltd.:44-1256-381-400OrCAD Design Network (ODN): http://www.orcad.com/odn
9300 SW Nimbus Ave.Beaverton, OR 97008 USA
ContentsBefore you beginxiiiProduct configurations . . . .How to use this guide . . . . .Symbols and conventionsRelated documentation . .Chapter 1.xiv. xv. xvxviOverview . . . . . . . . . . . . . . . . . . . . . . . . . .OrCAD network licensing . . . . . . . . . . . . . . . .What is the License Manager? . . . . . . . . . . . .Setting up network licensing for OrCAD programs . .Server guidelines . . . . . . . . . . . . . . . . . . .Selecting a server . . . . . . . . . . . . . . . . .Supported protocols . . . . . . . . . . . . . . .Choosing a license server . . . . . . . . . . . . . . .FLEXlm . . . . . . . . . . . . . . . . . . . . . . .NetHASP . . . . . . . . . . . . . . . . . . . . . .Step one: Configuring the designated license server . .Installing the hardware lock . . . . . . . . . . . . .Supported operating systems . . . . . . . . . . . .Novell Netware file server . . . . . . . . . . . .Windows 95 or NT 4.0 . . . . . . . . . . . . . .Step two: Installing OrCAD programs on a file serverStep three: Configuring remote or local clients . . . . .Windows 95 or NT 4.0 . . . . . . . . . . . . . .Troubleshooting your network licensing setup . . . .License Manager . . . . . . . . . . . . . . . . . . . .Clients . . . . . . . . . . . . . . . . . . . . . . . . .Server or client setup . . . . . . . . . . . . . . . . .Setting up the License Manageron a Novell Netware 386/486 file server . . . .Getting started.113344445556666789910101112. . . . . . . . . . . 13
ContentsSetting up Windows 95 or NT clients for Novell server . . .Setting up the License Manager on Windows 95 or NT . . .Windows 95 server . . . . . . . . . . . . . . . . . . . . . .Windows NT server . . . . . . . . . . . . . . . . . . . . .Automatic activation for NetHasp License ManagerSetting up Windows 95 or NT for NetBIOS . . . . . . . .Setting up Windows 95 or NT for TCP/IP . . . . . . . .Setting up local networks under Novell . . . . . . . . . . . .Specifying local networks with HASPSERV.NLM . . . .Examples . . . . . . . . . . . . . . . . . . . . . . . . .Specifying local networks with other servers . . . . . . .Setting timeout length . . . . . . . . . . . . . . . . . . . .Update or regenerate license information . . . . . . . . . . .Update license information . . . . . . . . . . . . . . . . .Regenerate license information . . . . . . . . . . . . . . .Chapter 2vi.151616161718192020212424252525Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . .Networks and protocols supported by NetHASP . . . . . .IPX support . . . . . . . . . . . . . . . . . . . . . . . . . .TCP/IP support . . . . . . . . . . . . . . . . . . . . . . .NetBIOS support . . . . . . . . . . . . . . . . . . . . . . .The NetHASP License Manager . . . . . . . . . . . . . . . . . .NetHASP on a Windows NT workstation . . . . . . . . . .Automatic activation of NHSRVW32.EXE . . . . . . . .Viewing the HASP NT Loader entry in the SCManagerNetHASP Automatic Search . . . . . . . . . . . . . . . . . . . .Automatic search algorithm . . . . . . . . . . . . . . . .Automatic search under IPX . . . . . . . . . . . . . . . . . .Automatic search under TCP/IP . . . . . . . . . . . . . . . .Automatic search under NetBIOS . . . . . . . . . . . . . . .NetHASP custom search . . . . . . . . . . . . . . . . . . . . . .General custom search information . . . . . . . . . . . . . .Custom search under IPX . . . . . . . . . . . . . . . . . . . .General notes for IPX . . . . . . . . . . . . . . . . . . . .Custom search under TCP/IP . . . . . . . . . . . . . . . . .UDP broadcast . . . . . . . . . . . . . . . . . . . . . . . .UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .General note for NetBIOS . . . . . . . . . . . . . . . . . etHASP.27
ContentsAdapting NetHASP to the network . . . . . . . . . . . . . . . . . . . .Defining the range of workstations under IPX . . . . . . . . . . . .Defining the range of workstations under TCP/IP . . . . . . . . .Defining the range of workstations under NetBIOS . . . . . . . . .Adapting the timeout length . . . . . . . . . . . . . . . . . . . . . .Defining the number of served protected programs . . . . . . . .NetHASP License Manager for Windows 95 and Windows NTNetHASP in Novell local networks and internetworks . . . . . . .Adapting the NetHASP License Manager . . . . . . . . . . . .Adapting the NetHASP client . . . . . . . . . . . . . . . . . . .Setting the default protocol on a network workstation . . . . . . .Windows 95 workstation . . . . . . . . . . . . . . . . . . . . . .Windows NT workstation . . . . . . . . . . . . . . . . . . . . .NetHASP License Manager switches . . . . . . . . . . . . . . . . . . .NetHASP configuration file template . . . . . . . . . . . . . . . . . . .NetHASP status codes . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 070717172737374747575767676777879808067Overview . . . . . . . . . . . . . . . . . . . . . . . . . .Overview of FLEXlm . . . . . . . . . . . . . . . . . . .FLEXlm components . . . . . . . . . . . . . . . . .The License Manager daemon (lmgrd) . . . . .The vendor daemon . . . . . . . . . . . . . . .The license file . . . . . . . . . . . . . . . . . . .The program . . . . . . . . . . . . . . . . . . . .The license request process . . . . . . . . . . . . . .Configuring FLEXlm . . . . . . . . . . . . . . . . .Getting started checklist . . . . . . . . . . . . . . . . .Installing licensed software . . . . . . . . . . . . .License servers and hostids . . . . . . . . . . .lmgrd and license files . . . . . . . . . . . . . .Administration tools . . . . . . . . . . . . . . .Options files . . . . . . . . . . . . . . . . . . . .Notes for end users . . . . . . . . . . . . . . . . . .How to specify a license file . . . . . . . . . . .Getting information about licenses . . . . . . .The license file . . . . . . . . . . . . . . . . . . . . . . .Specifying location of the license file . . . . . . . .Setting the path to the license file at start-up .Setting the path with an environment variableLicense file format . . . . . . . . . . . . . . . . . . .vii
ContentsSERVER lines . . . . . . . . . . . . . . . . . . . . . . .DAEMON lines . . . . . . . . . . . . . . . . . . . . .FEATURE or INCREMENT lines . . . . . . . . . . .FEATURESET lines . . . . . . . . . . . . . . . . . . .PACKAGE lines . . . . . . . . . . . . . . . . . . . . .UPGRADE lines . . . . . . . . . . . . . . . . . . . . .The anatomy of a license file . . . . . . . . . . . . . . . .Parameters of license file fields . . . . . . . . . . . .Types of license files . . . . . . . . . . . . . . . . . . . . .Floating (concurrent) licenses . . . . . . . . . . . . .Node-locked licenses . . . . . . . . . . . . . . . . . .Mixed node-locked and floating licenses . . . . . . .The license finder . . . . . . . . . . . . . . . . . . . . . . . . .Starting the license finder . . . . . . . . . . . . . . . . . .Finder file format . . . . . . . . . . . . . . . . . . . . . .Combining license files . . . . . . . . . . . . . . . . . . . . .Overview of combining license files . . . . . . . . . . . .Using the same server node . . . . . . . . . . . . . . . . .Why license files may not be compatible . . . . . . .Combining license files from multiple vendors . . .Using separate license files on the same server nodeUsing a different server node . . . . . . . . . . . . . . . .Selecting server nodes . . . . . . . . . . . . . . . . . . . . . .Resources used by the server . . . . . . . . . . . . . . . .Processes . . . . . . . . . . . . . . . . . . . . . . . . .Sockets . . . . . . . . . . . . . . . . . . . . . . . . . .CPU time . . . . . . . . . . . . . . . . . . . . . . . . .Disk space . . . . . . . . . . . . . . . . . . . . . . . .Memory . . . . . . . . . . . . . . . . . . . . . . . . . .Network bandwidth . . . . . . . . . . . . . . . . . . .Diskless nodes and remote mounted disks . . . . . . . .Redundant servers . . . . . . . . . . . . . . . . . . . . . .Setting up redundant servers . . . . . . . . . . . . . .Quorums and redundant servers . . . . . . . . . . .Counted vs. uncounted licenses . . . . . . . . . . . . . .The options file . . . . . . . . . . . . . . . . . . . . . . . . . .Creating an options file . . . . . . . . . . . . . . . . . . .Customizing the options file . . . . . . . . . . . . . . . .EXCLUDE . . . . . . . . . . . . . . . . . . . . . . . .EXCLUDEALL . . . . . . . . . . . . . . . . . . . . . .GROUP . . . . . . . . . . . . . . . . . . . . . . . . . .HOST GROUP . . . . . . . . . . . . . . . . . . . . . 10111111112
ContentsINCLUDE . . . . . . . . . . . . . . . .INCLUDEALL . . . . . . . . . . . . . .LINGER . . . . . . . . . . . . . . . . .NOLOG . . . . . . . . . . . . . . . . .REPORTLOG . . . . . . . . . . . . . .RESERVE . . . . . . . . . . . . . . . . .TIMEOUT . . . . . . . . . . . . . . . .Understanding the options file . . . . . . .How lmgrd uses the options file . . .Rules of precedence in the options fileLimiting access for multiple users . . .License administration tools . . . . . . . . . .lmcksum . . . . . . . . . . . . . . . . . . .lmdiag . . . . . . . . . . . . . . . . . . . .lmdown . . . . . . . . . . . . . . . . . . . .lmgrd . . . . . . . . . . . . . . . . . . . . .lmhostid . . . . . . . . . . . . . . . . . . .lmremove . . . . . . . . . . . . . . . . . . .lmreread . . . . . . . . . . . . . . . . . . .lmstat . . . . . . . . . . . . . . . . . . . . .lmswitchr . . . . . . . . . . . . . . . . . . .lmver . . . . . . . . . . . . . . . . . . . . .The debug log file . . . . . . . . . . . . . . . .Informational messages . . . . . . . . . . . . .Configuration problem messages . . . . . . .Daemon software error messages . . . . . . .FLEXlm troubleshooting guide . . . . . . . . .General debugging tips . . . . . . . . . . .Troubleshooting list . . . . . . . . . . . . .Problem-description-solution format .Hostid problems . . . . . . . . . . . .Connection problems . . . . . . . . . .Other client problems . . . . . . . . . .Hostids for FLEXlm-supported machines . . 143145149151ix
Contentsx
TablesTable 1Table 2Table 3Table 4Table 5Table 6Table 7Table 8Table 9Table 10Table 11Table 12Table 13Table 14Table 15NetHASP License Manager switches . . . . . .NetHASP License Manager switch descriptions[NH COMMON] keywords . . . . . . . . . . .[NH IPX] keywords . . . . . . . . . . . . . . .[NH NETBIOS] keywords . . . . . . . . . . . .[NH TCPIP] keywords . . . . . . . . . . . . . .NetHASP server status codes . . . . . . . . . .Default location of the FLEXlm license file . . .Where to install FLEXlm administration tools .Starting the License Manager daemon . . . . .License file parameter length limits . . . . . . .FLEXlm options file syntax . . . . . . . . . . . .FLEXlm informational messages . . . . . . . . .FLEXlm configuration problem messages . . .Daemon software error messages . . . . . . . . 52. 53. 57. 58. 60. 61. 63. 70. 75. 77. 90109132135138
Tablesxii
Before you beginOrCAD offers a total solution for your core design tasks:schematic- and VHDL-based design entry; FPGA andCPLD design synthesis; digital, analog, and mixed-signalsimulation; and printed circuit board layout. What’smore, OrCAD’s products are a suite of applications builtaround an engineer’s design flow—not just a collection ofindependently developed point tools. OrCAD networklicensing is just one element in OrCAD’s total solutiondesign flow.OrCAD network licensing allows users in a networkconfiguration to use OrCAD programs, such as PSpice,Layout, Express, Capture, or Capture CIS, on any Novell,Windows 95, or Windows NT computer (or client) on thenetwork without being locked to a specific computer.The number of users who can run OrCAD programs at thesame time is limited to the number of program licensespurchased.OrCAD network licensing is handled by the LicenseManager, which administers licenses to clients.
Before you beginProduct configurationsWhen you install OrCAD network licensing, you canchoose between two types of license managers: NetHASP,or FLEXlm.NetHASP works with TPC/IP, IPX, and NetBIOS, sosystem administrators can use a wide variety ofconfigurations for client computers.FLEXlm gives administrators more control and flexibilitythan NetHASP in administering OrCAD licenses, butrequires that the license server and all of the clientmachines be configured with TCP/IP.xiv
How to use this guideHow to use this guideThis guide is designed so you can quickly find theinformation you need to use network licensing. To helpyou learn and use network licensing efficiently, thismanual is organized by tasks, beginning with installationand configuration basics (chapter one), and moving on tomore advanced concepts for the NetHASP and FLEXlmlicense managers (chapters two and three).Symbols and conventionsOrCAD printed documentation uses a few specialsymbols and conventions.NotationExamplesDescriptionC rPress C rMeans to hold down the C keywhile pressing r.A, f, oFrom the File menu, choose Open (A, f, o) Means that you have two options.You can use the mouse to choosethe Open command from the Filemenu, or you can press each of thekeys in parentheses in order: firstA, then f, then o.Monospace fontIn the Part Name text box, type PARAM.Text that you type is shown inmonospace font. In the example,you type the characters P, A, R,A, and M.MODEL MLOAD NMOSExamples of syntax, netlist output,and source code are displayed inmonospace font. The exampleshows an example of the syntax forthe PSpice .MODEL statement. (LEVEL 1 VTO 0.7 CJ 0.02pF)UPPERCASEIn Capture, open CLIPPERA.DSN.Path and filenames are shown inuppercase. In the example, youopen the design file namedCLIPPERA.DSN.ItalicsIn Capture, save design name.DSN.Information that you are to provideis shown in italics. In the example,you save the design with a name ofyour choice, but it must have anextension of .DSN.xv
Before you beginRelated documentationIn addition to this guide, you can find technicalinformation in online help files, online books, OrCAD’stechnical web site, as well as other books. The table belowdescribes the types of technical documentation providedwith the Network Licensing Guide.This documentation component . . .Provides this . . .This guide—OrCAD Network Licensing GuideBasic and advanced information on installing andconfiguring network licensing for OrCAD products.NetHASP settings online help (NETTEST.HLP)Testing information for the NetHASP License Manager.HASP device driver installation online help(HINSTALL.HLP)Installation, troubleshooting, and command lineinformation for the HASP device driver.NetHASP License Manager online help(NHSRVW32.HLP)Information about using the NetHASP License Manager.NetHASP Monitor online help (MONITOR.HLP) Data on the loaded NetHASP License Manager, includingset and installed protocols, the number of NetHASPLicense Managers on the network, and the number of usersthat have logged in to the License Manager.Online OrCAD Network Licensing GuideAn online, searchable version of this guide.ODN—OrCAD Design Networkwww.orcad.com/odnAn internet-based technical support solution. ODNprovides a variety of options for receiving and accessingdesign and technical information. ODN provides: A Knowledge Base with thousands of answers toquestions on topics ranging from schematic designentry and VHDL-based programmable logic design toprinted circuit board layout methodologies. A Knowledge Exchange forum for you to exchangeinformation, ideas, and dialog with OrCAD users andtechnical experts from around the world. A list of newpostings appears each time you visit the KnowledgeExchange, for a quick update of what’s new since yourlast visit. Tech Tips that deliver up-to-the-minute productinformation in your email box. Stay informed about thelatest advances, tips, and announcements on yourOrCAD product. Online technical support via the Tech SupportConnection. Use this service to submit technical supportincidents online. Create submissions, upload files, trackyour incidents and add comments directly intoOrCAD’s support database.xvi
Getting started1OverviewThe following sections provide information for setting upyour network for network licensing: OrCAD network licensing on page 1-3 describes thenetwork licensing and the License Manager. Setting up network licensing for OrCAD programs onpage 1-4 gives guidelines for selecting and setting up aserver. Troubleshooting your network licensing setup on page 1-10provides information on troubleshooting the LicenseManager, client crashes, or your network setup. Setting up the License Manager on a Novell Netware386/486 file server on page 1-13 describes setting up theLicense Manager on a Novell server. Setting up Windows 95 or NT clients for Novell server onpage 1-15 describes setting up a network withWindows clients and a Novell server.
Chapter 1 Getting started2 Setting up the License Manager on Windows 95 or NT onpage 1-16 describes setting up a network of Windowscomputers using the IPX protocol. Setting up local networks under Novell on page 1-20describes setting up a network of Novell computers. Update or regenerate license information on page 1-25explains how to update or regenerate your licenseinformation.
OrCAD network licensingOrCAD network licensingNetwork licensing allows users running in a networkconfiguration to use OrCAD programs, such as PSpice,Layout, Express, or Capture, on any Novell, Windows 95,or Windows NT computer (or client) on the networkwithout being locked into a specific computer.The number of users who can run OrCAD programs at thesame time is limited to the number of program licensespurchased.What is the License Manager?The License Manager is the OrCAD program thatadministers licenses to clients. It runs on the server andaccesses the hardware lock for licensing information.Depending on your configuration, the License Manager iscalled NHSRVW32.EXE, HASPSERV.NLM, orLMGRD.EXE.See Chapter 2, NetHASP, for moreinformation about NetHASP licensing.See Chapter 3, FLEXlm, for moreinformation about FLEXlm licensing.Once the hardware lock and License Manager areinstalled on the server, each license is checked in andchecked out by the License Manager. The LicenseManager administers the licenses throughout thenetwork. This process is completely transparent.3
Chapter 1 Getting startedSetting up network licensing forOrCAD programsThere are three major steps in setting up networklicensing for OrCAD programs. They must be performed inthe following order:1Configure the designated license server by installingthe License Manager program.You must install the License Manager prior to installing OrCADprograms.Note2Install OrCAD programs on a file server (or onindividual clients).3If the OrCAD programs are installed on a file server(not a client), configure network clients to access theOrCAD programs installed on the file server.Server guidelinesAdditional requirementsSelecting a serverThe computer must have a parallel port andmust be stable, which means it should notbe subject to frequent restarting.The computer you choose to be the server will depend onyour network configuration. The server can be anyNovell, Windows 95, or Windows NT computer on thenetwork. However, you must designate one computer asthe server. This computer then becomes the license serverthat will handle the requests for individual licenses fromclients by monitoring the number of users or licenses.Supported protocolsproducts support IPX, NETBIOS, and TCP/IPprotocols on Novell, Windows NT and Windows 95.OrCAD4
Setting up network licensing for OrCAD programsChoosing a license serverIf you are running the TCP/IP protocol, OrCADrecommends configuring your server with FLEXlm;however, you have the option to use NetHASP.FLEXlmProsConsFLEXlm gives administratorsmore control and flexibilitythan NetHASP in administeringOrCAD licenses.FLEXlm requires thelicense server and all ofthe client machines to beconfigured with TCP/IP.See Chapter 3, FLEXlm, for moreinformation about the features andbenefits of FLEXlm.With FLEXlm you can: Selectively allow access tolicenses for a defined groupof people. Check in licenses that are notbeing used. Get information about whatlicenses are being used andby whom.NetHASPProsConsNetHASP works withTCP/IP, IPX and NetBIOS,so system administrators canuse a wider variety ofconfigurations for clientcomputers.NetHASP provides onlyminimal administrativetools.See Chapter 2, NetHASP, for moreinformation about the features andbenefits of NetHASP.NetHASP Monitor providesremote monitoring of theLicense Manager.5
Chapter 1 Getting startedStep one: Configuring thedesignated license serverThe license server and the file server can have differentoperating systems. For example, if you are using Novellon your file server, you can designate a Windows 95workstation as the license server.Installing the hardware lockThe license server requires a hardware lock. The rednetwork hardware lock attaches to the parallel port (theplug does not affect the operation of printers or otherdevices).NoteThe machine that hosts the hardware lock is designated as thelicense server.Supported operating systemsThe computer you choose for the license server dependson your network configuration. The server can be anyNovell, Windows 95, or Windows NT computer on thenetwork.During the Novell Netware file serverinstallation, the installation programrequests that you attach the hardware lockto the client. After the installation, removethe hardware lock and attach it to theserver.6Novell Netware file serverTo install the License Manager on a Novell Netware fileserver you must start the installation process on a client soyou can remotely access the appropriate files through theNovell console.1Select a client (Windows 95 or NT) that has permissionto copy files to an area that can be accessed from theNovell console.
Step one: Configuring the designated license server2Insert the OrCAD CD into the CD-ROM drive on theclient.3From the Start menu of the Windows task bar, chooseRun.4Enter: drive:\SETUP.EXE (where drive is theCD-ROM drive).5When the Installation Setup screen appears, selectNetwork Server Installation. Follow the instructionson how to install the License Manager program.Windows 95 or NT 4.01Insert the OrCAD CD into the CD-ROM drive.2From the Start menu of the Windows task bar, chooseRun.3Enter: drive:\SETUP.EXE (where drive is theCD-ROM drive).4When the Installation Setup screen appears, selectNetwork Server Installation. Follow the instructionson how to install the License Manager program.NotePress F1 to access help during the License Manager installationprocess.7
Chapter 1 Getting startedStep two: Installing OrCADprograms on a file serverOnce the License Manager has been installed and testedon the server, you are now ready to install OrCADprograms. These programs can be installed on a fileserver, or on individual clients.Note8Press F1 to access help during the OrCAD program installationprocess.
Step three: Configuring remote or local clientsStep three: Configuring remoteor local clientsNoteConfiguring remote clients is only possible if you have installedOrCAD programs on a designated file server.Windows 95 or NT 4.01Insert the OrCAD CD into the CD-ROM drive on theclient.2From the Start menu of the Windows task bar, chooseRun.3Enter: drive:\SETUP.EXE (where drive is theCD-ROM drive).4Select Configure Client on the Installation Setupscreen.5Select Remote on the following screen to create a localprogram group on the client, with references toprogram files that are installed on a remote server.Alternatively, select Local to install the program fileson the local client.NotePress F1 to access help during the configure client process.9
Chapter 1 Getting startedTroubleshooting your networklicensing setupIf the license manager becomesunavailable for any reason while an OrCADprogram is running, you may be promptedto remedy the situation before you will beallowed to resume operation. The programmakes every attempt to provideuninterrupted service.Note If you need to restart the LicenseManager or the license server, the clientswill lose their licenses, and theirapplications will need to be restarted.10License ManagerRun the built-in diagnostic program to verify the LicenseManager is working properly. To run the built-indiagnostic program, do the following:1Insert the OrCAD CD into the CD-ROM drive.2From the Windows Start menu, choose Run.3Enter: drive:\SETUP.EXE (where drive is theCD-ROM drive).4On the Installation Setup dialog, select NetworkServer Installation and choose Next.5Select Test License Manager and choose Next.6Enter the path to the Server ID file, then choose Next.7Enter the directory path to where the License Manageris installed, or accept the default path provided, thenchoose Next.8In the Activate the License Manager dialog, selecteither Activate License Manager or Do not activate, itis already running, depending on the activation statusof the License Manager. Choose Next to run thediagnostic program.
Troubleshooting your network licensing setupIf the test fails on this Verify this Novell server1License Manager version 6.0 is loaded and running onNovell file server.2Current workstation has IPX installed and configured.3Current workstation can communicate with the Novellserver. (This can be done by doing something as simpl
NetHASP settings online help (NETTEST.HLP) Testing information for the NetHASP License Manager. HASP device driver installation online help (HINSTALL.HLP) Installation, troubleshooting, and command line information for the HASP device driver. NetHASP License Manager online help (NHSRVW32.HLP) Information about using the NetHASP License Manager .
