IBM 16/4 Token-Ring PCI Adapter II for IBM Lan Client Disk 4 (V3.00) THIS FILE IS BEST VIEWED AFTER PRINTING. THE FILE LNCLIENT.HTM CONTAINS EXACTLY THE SAME INFORMATION AS IS IN THIS FILE. LNCLIENT.HTM IS FORMATTED IN HTML AND CAN BE VIEWED IN ANY WEB BROWSER OR HTML ENABLED WORD PROCESSOR. ==================================================================================== WEB BROWSER OR HTML ENABLED WORD PROCESSOR. IBM LAN Client - VERSION 3.0 (With Novell IntranetWare Client for DOS/Windows 3.1x) TO THE READER: This document is for Release 3.0 of IBM LAN Client. If you obtain a later version of the code, you should obtain a later version of the document as part of the new package. You should use this document with Release 3.0 only. It is assumed that you have downloaded and unpacked the IBM LAN Client code to obtain this document, and have therefore read the README.1ST file that was delivered with the IBM LAN Client. To obtain the latest version of IBM Lan Client you can get the package named LANCLNT by: Downloading updated diskette images using anonymous FTP from either: The IBM LAN Support BBS at ftp.raleigh.ibm.com, directory pub/products/lanprods/lantran Using the World Wide Web to access URL http://www.raleigh.ibm.com/nes/neslant.htm Follow the instructions for downloading and creating diskettes given on the Web page. Once the diskettes are created, refer to the README.1ST file on the LANCLNT1 diskette for further assistance. Using the dial-in BBS to download files. Call 1-919-517-0001 and set your modem to 8 data bits, no parity, and 1 stop bit. Provide the requested information, or answer "yes" to all prompts to register with the BBS and reach the main panel. You should then type REFDISK to access the Licensed Software areas. Then, type S LAN CLIENT to find the IBM Lan Client files. TECHNICAL ASSISTANCE: Technical support for this release is available by calling IBM support at the following numbers: In the USA, 1-800-426-7299 Options by IBM Help Center In the USA, 1-800-237-5511 IBM Support Services In the USA, 1-800-772-2227 IBM Help Center In Canada, 1-800-565-3344 Information on Novell IntranetWare Client is available using the World Wide Web address http://www.novell.com/intranetware/products/clients/clientdoswin When you request support for the LAN Client program, please gather the following information: 1.Adapter name 2.LAN Client version number (displayed when the LAN Client is loaded 3.PC type, model, and RAM size 4.Version of DOS 5.Which application software you are using and its version 6.A description of the problem 7.The contents of CONFIG.SYS 8.The contents of AUTOEXEC.BAT and STARTNET.BAT 9. The contents of NET.CFG, NETWORK.INI, and RESOLV.CFG 10. The contents of SYSTEM.INI and WIN.INI if using MS Windows 11. Is there a hardware copy protection device being used? 12. The MODULE.TXT file created by executing the command MODULES>MODULE.TXT from the command prompt after loading LAN Client. 13. The version of EMM386 you are using (displayed by loading EMM386 from the command line) 14. The version of HIMEM.SYS you are using 15. Names of any files sent 16. Contact name, phone number, and e-mail address CONTENTS About IBM LAN Client 2 IBM LAN Client Features 2 DOS Conventional Memory Usage -- Reduction 3 Supported IBM LAN Adapters 3 4Supported Software 4 Supported Operating Systems 4 Related Documentation 4 Restrictions for This Release 4 Installing IBM LAN Client - Overview 4 The Installation Programs: LCINST and LCINSTC 4 Hardware Requirements 5 Memory Requirements 5 Software Requirements 5 Dynamically Loading and Unloading Modules 5 Using the IBM LAN Client GUI Installation Program (LCINST) 6 Using the IBM LAN Client Command line Installation Program (LCINSTC) 6 General Parameters 7 Specifying Protocols and Applications 7 Parameters for Novell Intranetware Client 8 Parameters for TCP/IP 9 Parameters for Class of Service 9 Parameters for Route Switch 10 Parameters for Token-Ring ISA Adapters 10 Parameters for Token-Ring Microchannel Adapters 10 Parameters for Auto LANStreamer Token-Ring PCI Adapters 11 Parameters for Token-Ring PCI Family Adapters 11 Parameters for Token-Ring Credit Card Adapters 12 Application-Specific Installation Information 13 Installing DOS LAN Requester 13 Installing DOS LAN Services GUI or DDE Support 13 Installing with Artisoft's LANtastic 13 Installing with Novell's LAN Workplace 14 Installing with NetManage's Chameleon 14 Using the WINSOCK Apps from IBM TCP/IP Version 2.x for DOS 14 Using the WINSOCK Apps from IBM Internet Connection for Windows Version 5.x 14 Installing IBM LAN Client from a Network Server 14 Installation and Load-Time Messages 15 Installation Program Messages 15 LCINSTC Installation and Load-Time Messages 16 CCB1API Load-Time Messages 17 NNetBIOS Load-Time Messages 18 NCBRMAPI Load-Time Messages 18 NLLC8022 Load-Time Messages 18 Troubleshooting Tips 18 Bridging Considerations 19 Configuring a TCP/IP Hosts File 19 Insufficient Environment Space 19 Information about Configuration Files 19 Information about NET.CFG 19 Information about STARTNET.BAT 19 NetBIOS Parameters 20 Configuration parameter 21 Timer Tick Values 21 Differences between IBM LAN Client and LAN Support Program 22 List of Abbreviations 22 Trademarks 23 About IBM LAN Client IBM LAN Client provides program interfaces to support network application programs using selected IBM Token-Ring. It allows a client workstation to communicate with an IBM LAN Server at Version 3.0, 4.0, and Warp Server, or with a Novell Netware Server at Version 2.15c or higher, or to use TCP/IP applications. (The IBM and Novell client code is included with this package but, with the exception of PING, TCP/IP applications are not.) In addition, support is provided for programs written to the NetBIOS or I EEE 802.2 application programming interfaces. IBM LAN Client Features ƒ As little as 4 KB conventional memory required. (See below for more detail.) ƒ One common environment for concurrent multiple protocols. ƒ One or more of NetBIOS, IPX, TCP/IP, and IEEE 802.2. ƒ Shim modules, such as ODINSUP and LANSUP, are not needed. ƒ Includes client software for attachment to Novell NetWare Servers and IBM LAN Servers. ƒ Supports DOS LAN Services 5.x. ƒ New Novell IntranetWare Client for DOS/Windows. ƒ Provides full access to essential NetWare services such as NetWare Directory Services (NDS). ƒ Provides improved connection reliability, including the ability to auto-reconnect open files. ƒ Provides enhanced Large Internet Packet (LIP) and Packet Burst support. ƒ Includes an installation tool with a Graphical User Interface (GUI) for easy installation of client software. ƒ Includes a command-line version of the installation tool for use by network administrators installing on a large number of workstations. ƒ Allows the same adapter device driver to be used for client workstations and for Novell NetWare servers, reducing support complexity. DOS Conventional Memory Usage -- Reduction IBM LAN Client minimizes the use of DOS conventional memory for network communications. With IBM LAN Client, IBM LAN adapter drivers and protocol stacks no longer require large amounts of DOS memory below 1 MB. The tables in this section show how little m emory is required for IBM LAN Client, compared to existing implementations. There is one table for ISA and Microchannel adapters, and one for the PCI adapter. These tables show how much DOS conventional memory is used by IBM LAN Client for three popular communication protocols, compared with current usage. Table 1. IBM Auto 16/4 ISA and MC Adapter Memory Reduction Table Protocol Before IBM Lan Client With IBM Lan Client Protocol Before IBM Lan Client With IBM Lan Client IPX 32KB 5KB IEEE802.2 9KB 4KB NetBIOS 32KB 4KB Table 2. IBM Auto LANStreamer Adapter Memory Reduction Table Protocol Before IBM Lan Client With IBM Lan Client Protocol Before IBM Lan Client With IBM Lan Client IPX 59KB 5KB IEEE 802.2 95KB 4KB NetBIOS 95KB 4KB Supported IBM LAN Adapters IBM LAN Client provides support for the following adapters: ƒ IBM Auto LANStreamer PCI Adapter ƒ IBM Auto 16/4 Token-Ring ISA Adapter ƒ IBM Token-Ring 16/4 ISA-16 Adapter ƒ IBM Token-Ring Auto 16/4 Credit Card Adapter ƒ IBM Auto 16/4 Token-Ring MC Adapter ƒ IBM Token-Ring 16/4 Adapter/A ƒ IBM Auto Wake Token-Ring ISA Adapter ƒ IBM Token-Ring PCI Family Adapters ƒ IBM Turbo 16/4 Token-Ring ISA Adapter ƒ IBM Turbo 16/4 Token-Ring Credit Card Adapter The adapter device driver needed for the adapter to operate with the IBM LAN Client software is provided on the IBM LAN Client installation diskettes. The following drivers are provided: ƒ TOKEN.LAN -- for ISA, Microchannel, and PCMCIA Token-Ring adapters ƒ IBMMPCO.LAN -- for the Auto LANStreamer PCI Token-Ring adapter ƒ IBMTRPO.LAN -- for the Token-Ring PCI Family Adapters The installation program will copy the driver onto your workstation hard disk when you tell it which adapter you will be using. It will also provide the correct load statements in STARTNET.BAT. Supported Software IBM LAN Client provides support for the following protocols and client applications: ƒ For DOS 5.0 or higher: ƒ IEEE 802.2 ƒ NetBIOS ƒ DOS LAN Services 5.x (with IBM Warp Server) ƒ NetWare IntranetWare Client (IPX/SPX) (with Novell NetWare 2.15c and higher) ƒ PC3270 Version 4.x ƒ DCAF (Version 1.3 + CSDs) ƒ Artisoft LANtastic Version 6.0 ƒ Attachmate 3270 Emulation ƒ LANDP (If you are using Version 2, make sure that the service level of LAN.EXE is MS004 or higher.) ƒ For Windows 3.1, Windows 3.11, and Windows for Workgroups 3.11: ƒ IEEE 802.2 ƒ NetBIOS ƒ DOS LAN Services 5.x (with IBM Warp Server) ƒ Novell IntranetWare Client (IPX/SPX) (with Novell NetWare 4.0) ƒ AS/400 for Windows (Version 4.0, V3R1M0, and V3R1M1 TCP/IP OR 802.2 ƒ TCP/IP using Winsock 1.1 or 1.2 ƒ PC3270/Windows Version 4.x ƒ Artisoft LANtastic Version 6.0 ƒ APPC/Windows Note: IBM LAN Station Manager cannot be run in the same workstation as IBM LAN Client. Supported Operating Systems IBM LAN Client supports the following desktop operating systems: ƒ MS-DOS 5.x and 6.x ƒ PC-DOS 5.x, 6.x, and 7.0 ƒ Windows 3.1 and 3.11, in enhanced mode ƒ Windows for Workgroups 3.11 Related Documentation In addition to this document, you might need to consult the following publications: ƒ The appropriate LAN adapter documentation (provided with the adapter) ƒ IBM LAN Technical Reference IEEE 802.2 and NetBIOS Application Programming Interfaces, SC30-3587 ƒ IBM LAN Server Command and Utilities, S10H-9686 ƒ IBM Guide to LAN Server Books, S10H-9688 ƒ IBM DOS LAN Services and Windows User's Guide, S10H-9684 ƒ Manuals for Novell IntranetWare Client and Novell NetWare Server 4.0 ƒ Manuals for Novell TCP/IP interface Note: IBM documentation can be obtained from your IBM marketing representative, or by calling IBM support at the following numbers: ƒ In the USA, 1-800-426-7299 ƒ In Canada, 1-800-565-3344 Note: Novell documentation can be obtained by contacting Novell, either by calling 1-800-NETWARE or over the World Wide Web at URL http://www.novell.com. Restrictions for This Release The following restrictions apply for this release of IBM LAN Client: ƒ IBM LAN Client will operate with only one adapter. ƒ You cannot use RPL to download IBM LAN Client from either a Novell NetWare server or an IBM LAN Server. Installing IBM LAN Client - Overview Read this section before installing IBM LAN Client. The Installation Programs: LCINST and LCINSTC There are two installation programs provided on the IBM LAN Client diskettes: ƒ LCINST provides a GUI and should meet the needs of most users. ƒ LCINSTC allows parameters to be specified on the command line or in a file, and is intended for use by network administrators who have to install IBM LAN Client on many machines. You will need to run the program INSTALL.EXE, on IBM LAN Client diskette 1, to unpack and install LCINST or LCINSTC. Information on how to do this is included in the sections: "Using the IBM LAN Client GUI Installation Program (LCINST)" page 6 "Using the IBM LAN Client Command line Installation Program (LCINSTC)" page 6 The installation programs will configure and install IBM LAN Client, including the protocol stacks and client applications you request. They will not configure and install your network adapter. If you do not already have an adapter installed, you must ins tall and configure an adapter (using the installation aid that came with the adapter) before installing IBM LAN Client. If you already have a supported adapter installed, the IBM LAN Client installation program will replace your existing adapter device dr iver with a driver from the IBM LAN Client diskettes. In order to run IBM LAN Client, changes need to be made to some of your system files, and you will also need a NET.CFG and a STARTNET.BAT file. The installation program will always create NET.CFG and STARTNET.BAT files for you. There is more information a bout these two files in "Information about Configuration Files." Changes will need to be made to CONFIG.SYS and AUTOEXEC.BAT. You can choose to let the installation program make the changes for you, in which case your existing CONFIG.SYS and AUTOEXEC.BAT files will be renamed to CONFIG.xxx and AUTOEXEC.xxx, where xxx i s a numeric between 000 and 999 that is incremented each time the files are updated. If you do not want the changes made automatically, the installation program will create new files, named CONFIG.LC and AUTOEXEC.LC, and put them in the directory you spec ified as the target directory. In this case, you will need to manually update CONFIG.SYS and AUTOEXEC.BAT before running IBM LAN Client. If you are going to run IBM LAN Client in a Windows environment, changes will need to be made to PROGMAN.INI, SYSTEM.INI, and WIN.INI. The installation will make backup copies of these files, named PROGMAN.xxx, SYSTEM.xxx, and WIN.xxx, where xxx is a nume ric between 000 and 999 that is incremented each time the files are updated. Hardware Requirements In order to run IBM LAN Client, your workstation must have the following hardware: ƒ Intel (or compatible) 80386 or higher processor ƒ Hard-disk drive with at least 3 MB of free storage ƒ At least 4 MB of RAM (6 MB when using Novell IntranetWare Client) ƒ One LAN adapter from the list of Supported IBM LAN Adapters on page 3. ƒ A Connection to the network Memory Requirements You will need at least 4 MB of RAM to run IBM LAN Client (6 MB when using Novell IntranetWare Client). Although IBM LAN Client requires much less conventional memory than earlier solutions, it does require a certain amount of extended memory. If you run a tool such as MEMMAKER that maximizes conventional memory, you must tell it that you need extended memory. The installation program that you will use to install IBM LAN Client might also require extended memory to operate. The command line installation program requires no extended memory, and no more than 300 KB of conventional memory. The GUI installation pro gram requires less than 1.5 MB of extended memory and no more than 300 KB of conventional memory. The amount of extended memory needed depends on the applications and protocols you choose to run. This section lists the approximate requirements for some popular configurations. These figures are based on a Token-Ring ISA or MC adapter, and a cache of 38 4 KB for the Novell IntranetWare Client (the default on 4 MB workstations). Table 3. Extended Memory Requirements Table APPLICATION/PROTOCOL Extended Memory NetBIOS/IEEE 802.2 877KB TCP/IP 1011KB TCPIP NETBIOS/IEEE 802.2 1139KB Novell IntranetWare Client 1.99KB Novell IntranetWare Client/IEEE 802.2 2.12KB Novell IntranetWare Client/TCP/IP IEEE 802.2 2.38KB Software Requirements In order to run IBM LAN Client, you must have the following software installed on your workstation: ƒ An operating system from the following list: ƒ MS-DOS 5.0 or higher ƒ PC-DOS 5.0 or higher ƒ Windows 3.1 or 3.11 in enhanced mode ƒ Windows for Workgroups 3.11 A DOS memory manager, HIMEM.SYS must be installed. In addition, EMM386.EXE V4.49 or later can be installed, as can most third-party memory managers such as Quarterdeck's QEMM-386. Note: If EMM386.EXE is in use, it must be at V4.49 or later. EMM386.EXE is provided with your DOS operating system. To determine what version you are using, simply type EMM386 at your DOS command line. The latest version of EMM386.EXE can be obtained from the IBM BBS at service.boulder.ibm.com using anonymous FTP. It will be in the ps/products/pcdos/fixes/v7.0 directory, named d70emm.zip. There are two environments where IBM LAN Client is not the optimal solution: ƒ If you are running DOS (without Windows) and you need TCP/IP support, you will have to continue using your current solution based on a NDIS 2- or 16-bit ODI MAC driver since IBM LAN Client does not provide TCP/IP support under DOS. ƒ If you are running Windows for Workgroups Version 3.11 and you are using the Windows for Workgroups requestor and do not need the 802.2 protocol stack or any of the additional features provided by Novell IntranetWare Client, you should not load LAN C lient. Dynamically Loading and Unloading Modules The installation programs will create and update files that will load a complete IBM LAN Client package when you power up or restart your workstation. IBM LAN Client also allows you to change which modules are loaded while you are using your workstation. To load a module, you would either: ƒ Make the directory containing the module the current directory ƒ Type (for example): LOAD TOKEN FRAME=TOKEN-RING or: ƒ Type (where the module is in C:\LNCLIENT): LOAD C:\LNCLIENT\TOKEN FRAME=TOKEN-RING To unload a module, follow the same procedure, but substitute UNLOAD for LOAD and omit any parameters. If you unload an adapter device driver or a protocol module while communications are active, you will terminate the communications. Note: When you use the Ctrl + Alt + Del key sequence to restart your workstation, you will see a red box with the following message: Please wait while the Novell IntranetWare Client shuts down ... This is normal behavior, and you will see this message for any combination of client and protocol code you have loaded. Using the IBM LAN Client GUI Installation Program (LCINST) The GUI installation program operates under DOS, or in the full-screen DOS box of Windows. You will need 1.5 MB of free extended memory and not more than 300 KB of conventional memory to run the program. First the installation program will be copied to yo ur hard disk, and then you can use it to install IBM LAN Client. After getting to a DOS prompt, you will need to do the following steps: ƒ Place the IBM LAN Client diskette 1 in drive A and type A:\INSTALL Then, press Enter. ƒ INSTALL.EXE will ask you which drive and which path and directory you want to use for the IBM LAN Client installation program. (If you simply press Enter, it will use the defaults of C: and LNCLIENT.) Next, it will decompress the necessary files and copy them to the directory. Error messages are listed in "Installation Program Messages." ƒ INSTALL.EXE will make the directory you specified in step 2 the current directory and invoke LCINST automatically. If you want to run LCINST at a later time, you will need to make the directory in which LCINST is installed the current directory and a t the command prompt type LCINST Then, press Enter. This will start the GUI installation program. The installation program consists of several panels that allow you to customize your installation. If you are happy with the defaults, you will just need to click OK on each panel. ƒ The first interactive panel will ask you to specify your operating environment -- DOS or Windows or Windows for Workgroups. It will also ask you to provide a name for a file to hold your configuration information. (This file could be used as input to the command line installation program LCINSTC.) ƒ The second panel asks you to identify the network adapter you will be using with IBM LAN Client. ƒ The third panel asks you which client applications and protocols you will want to run. Some selections require others: for example, you cannot run DLS without also running NetBIOS. Also, you cannot chooseTCP/IP unless you also choose Windows as your operating environment. ƒ You will then reach the configuration panel. On this panel, you will be asked to specify a target directory for the files that will be installed, and whether you want to have CONFIG.SYS and AUTOEXEC.BAT updated automatically. From this panel you can access others, listed next. If you have chosen to install TCP/IP or DLS, you must provide information on the corresponding panels. Additional panels are: ƒ Network Options: on this panel, you provide information specific to the adapter you selected. ƒ Route Switch: on this panel, you can enable Route Switching if the adapter software you selected supports this feature. ƒ Class of Srv: on this panel, you can set port ranges and priorities for TCP and UDP if the adapter software you selected supports this feature. ƒ TCP/IP: on this panel, you provide address information needed for TCP/IP to run. ƒ DLS: on this panel, you specify identifying information for your DOS LAN Services client station. You also select the type of DLS redirector you want, whether to start and log on to DLS when you start your workstation, and whether you want peer servi ces. ƒ NWCL32: on this panel, you can specify the parameters affecting your connection to a NetWare server. These are optional parameters. If you need help navigating through the panels, click the HELP area. If you need further information about the available choices, click the choice you are interested in using the right mouse button, or press F1. Note: If your workstation has 4 MB or less memory, you will not be able to run the GUI installation program after you have installed IBM LAN Client and restarted your machine. If you want to remove IBM LAN Client, or review the help text, you will need to run the command-line version of the installation program, described in the next section. If you want to run the GUI installation program again, "rem" out the startnet line in AUTOEXEC.BAT and reboot the machine. Using the IBM LAN Client Command line Installation Program (LCINSTC) The command line installation program operates under DOS, or in the full-panel DOS box of Windows. You will need no more than 170 KB of conventional memory to run the program. You can copy the installation program to your hard disk, and then use it to ins tall IBM LAN Client, or you can run it from your diskette drive. All of the parameters for the IBM LAN Client installation must be specified at the same time -- either on the command line or in a file. If you need fewer than 124 characters to specify the parameters, and you will be installing to only one workstation, you might choose to use the command line option. Otherwise, use an editor of your choice to create a text file containing the parameters. Note: The LCINSTC program allows some combinations of parameters that are not supported by IBM LAN Client. These combinations are not allowed by the GUI installation program. The GUI program was written for users who want to avoid making invalid or unsupp orted selections. In contrast, the command line program is targeted at the advanced technical user or LAN administrator for whom flexibility is more important than locking out all possible unsupported combinations. To guarantee a supported environment, us e the GUI to build a .CFG file that can then used be as input for the command line program. You might choose to run the command-line installation program from your diskette drive. If you want to have the program copied to your hard disk, follow these steps, after getting to a DOS prompt: ƒ Place the IBM LAN Client diskette 1 in drive A and type A:\INSTALL Then, press Enter. ƒ INSTALL.EXE will ask you which drive and which path and directory you want to use for the IBM LAN Client installation program. (If you simply press Enter, it will use the defaults of C: and LNCLIENT.) Next, it will decompress the necessary files and copy them to the directory. Error messages are listed in "Installation Program Messages." ƒ INSTALL.EXE will make the directory you specified in step 2 the current directory, and will start the GUI installation program, LCINST, automatically. You will need to exit from LCINST by clicking EXIT on the first panel. Note: If you want to make INSTALL.EXE run LCINSTC automatically instead of LCINST, you can edit the file RLCINST.BAT on the IBM LAN Client diskette Simply change the @LCINST.COM line to @LCINSTC /parm 1 /parm2 ../parm n (if no parameters specified, LCINSTC help text will be displayed). To install IBM LAN Client using the command line alone, you would  then type the following: LCINSTC /parm 1 /parm 2 .. /parm n Then, press Enter. You cannot run the program from your diskette drive. To install IBM LAN Client with the parameters in a file, you would do the following steps: ƒ Using an editor of your choice, create a text file containing parameters. The contents of the file could look like this: /NOUPDATE /TRPCI /NetBIOS Install LCINSTC as described above, or make the directory in which you previously installed LCINSTC the current directory. ƒ Type: LCINSTC /FILE=drive:\path\filename Then, press Enter. The /FILE parameter identifies the file you created in step 1. You can put some of the parameters in a file and some on the command line. You can code the same parameter in a file and on the command line. The installation program will read the command line from left to right, inserting parameters from a file when it encounters the /FILE parameter. If a parameter is duplicated, the last instance encountered will be the one used. You must determine all the parameters to be used for the install command before entering the entire install statement on your workstation command line. The following sections will describe the available parameters. Note: All parameters start with the / character. The parameter names are not case-sensitive; you can use any combination of upper- and lower-case letters. General Parameters These parameters are applicable for all adapter or protocol choices. Normally you would specify these parameters first. In the case of the /HELP or /REM parameter, it would normally be the only parameter. /?, /H, or /HELP Any of these parameters causes help information to be displayed in extended format. If none of these is selected, and no other correct parameters are specified, help is presented in abbreviated form. /FILE=drive:\path\filename This option allows you to specify the input parameters in a file. /REM Coding this parameter will cause the program to deactivate an existing IBM LAN Client installation. /LCDIR=drive:\dir Optional. This parameter specifies the directory where you want the installation program to put the IBM LAN Client programs. If you omit this parameter, the default will be C:\LNCLIENT. /NOUPDATE Optional. Specifying this option will prevent CONFIG.SYS and AUTOEXEC.BAT from being updated when IBM LAN Client is installed. New files are created instead, named CONFIG.LC and AUTOEXEC.LC, in the directory specified by the /LCDIR parameter. If this option is not specified, CONFIG.SYS and AUTOEXEC.BAT will be backed up to CONFIG.xxx and AUTOEXEC.xxx, where xxx is a decimal number between 000 and 999, and new CONFIG.SYS and AUTOEXEC.BAT files will be created. /WINDIR=drive: Coding this parameter tells the installation program that you want IBM LAN Client to run with Windows. It specifies the directory in which Windows is installed, which is usually C:\WINDOWS. If you request Windows support for DLS, by coding /DLS and /WINDL S, or you request TCP/IP support by coding /TCPIP, the installation program will search for your Windows directory automatically, and you do not need to code this parameter. Specifying Protocols and Applications The following parameters are used to specify the applications and protocols you want to install. Some of them have additional, protocol-specific, parameters that you might specify after you specify the application or protocol. They are defined in the foll owing sections. If you do not specify one of the parameters in this section, the Novell Intranetware Client and IEEE 802.2 will be installed by default. /NWCL32 This optional parameter requests installation of the Novell Intranetware Client. If you will be running IBM LAN Client with Windows, you cannot specify both /NWCL32 and /DLS. /DLS This optional parameter requests installation of DOS LAN Services and the NetBIOS protocol. If you select /DLS, you cannot also select /NetBIOS, which will be installed automatically. You cannot specify both /NWCL32 and /DLS. /NetBIOS This optional parameter requests installation of the NetBIOS protocol. /8022 This optional parameter requests installation of the IEEE 802.2 protocol. There are no other parameters for this protocol. /TCPIP This optional parameter requests installation of TCP/IP support. Do not specify this parameter unless you will be running IBM LAN Client with Windows. /ROUTESWENABLE=CLIENT,PEER,AUTO This option will enable the Route Switching for the adapter. The default is 'AUTO'. Parameters for Novell Intranetware Client If you select /NWCL32 as your client/server application, you can also specify the additional parameters described in this section. /AUTORECONLEVEL=n Optional. After a critical network error, Novell Intranetware Client will attempt to reconnect to network resources. This parameter is used to specify the highest level of resources you want auto-reconnected. The valid values (defined below) are 0-5, and the default is 1 for TokenRing. ƒ No auto-reconnect ƒ Devices only (connections, drives, printers) ƒ The same as for 1, plus read-only files ƒ The same as for 1, plus all files and file locks ƒ The same as for 3, including data recovery for file write data ƒ The same as for 4, plus the client will switch to local disk and re-synchronize with network files at a later time /PREFERREDSERVER=########################## Optional. Code this parameter to specify the server you normally use. This will be the first server the Novell Intranetware Client code will attempt to use when you establish a connection. /FIRSTNETDRIVE=# Optional. Use this parameter to specify the drive letter to be assigned to the first network drive when a connection is established to a NetWare server. Any letter between A and Z is valid. The default is the first available drive letter at the time IBM L AN Client is installed. /NAMECONTEXT=######################## Optional. You need to code this parameter only if you are connecting to a NetWare 4.x server. It specifies your context within the server's directory tree structure. If you do not know what to code for this parameter, contact your network administrator. Parameters for DOS LAN Services If you select /DLS as your client/server application, you can also specify the additional parameters described in this section. /MACHID=############### Required. This parameter specifies the Machine ID to DOS LAN Services. It is the name that identifies which computer is yours. Choose an ID that is unique within your domain. It can be up to 15 characters long and can contain letters, numbers, and the fol lowing characters: ! # $ % & ( ) _ ` ~ /USERNM=#################### Required. This parameter specifies the User Name to DOS LAN Services. It is the name that identifies you within the domain. Choose a name that is unique within your domain. It can be up to 20 characters long and can contain letters, numbers, and the follo wing characters: ! # $ % & ( ) _ ` ~ /DOMAINNM=############### Required. This parameter specifies the Domain Name to DOS LAN Services. It is the name of the domain to which you belong. It can be up to 15 characters long and can contain letters, numbers, and the following characters: ! # $ % & ( ) _ ` ~ /REDIR=B or /REDIR=F or /REDIR=V or /REDIR=P Required. This parameter specifies the type of redirector for DOS LAN Services. There are four redirectors: ƒ Basic (B) ƒ Full (F) ƒ Virtual (V) ƒ Protected mode (P) The basic redirector provides all standard requester functions, such as connecting, disconnecting, and browsing. It uses less memory and disk space than the full redirector and should be used if low memory usage is important and you are not running Window s. The full redirector provides advanced network functions, such as named pipes and support for using aliases to identify resources, as well as increased performance. The virtual redirector should be used if you are requesting Windows support and you want to reduce memory usage. If you selected Windows support, you should code this parameter as V(irtual). The protected mode redirector provides the function of the full redirector while using less DOS memory. /WINDLS Optional. Use this parameter if you want Windows support for DOS LAN Services. If you use this parameter and do not also use the /WINDIR parameter, the installation program will search for your Windows directory. /PEERDLS Optional. Use this parameter if you want DOS LAN Services Peer-to-Peer support to be installed. /DLSSTART=N or /DLSSTART=Y or /DLSSTART=LOGON Optional. This parameter specifies how DOS LAN Services should be started. If /DLSSTART=N is coded, then DLS will not be started when you power up or restart your workstation. If /DLSSTART=Y is coded, DLS will be started but you will not be logged on. If /DLSSTART=LOGON is coded, DLS will be started and you will be logged on. The default is /DLSSTART=Y. Note: The parameters previously used to specify extra SAPs and extra stations for NetBIOS are not needed with this version. Additional SAPs and stations will be allocated as required, as long as sufficient memory is available. Parameters for TCP/IP If you choose to install TCP/IP support by coding /TCPIP, you can also specify the additional parameters described in this section. If you do not know the values to code for these parameters, contact your network administrator. /DHCP Enable this parameter if you want to use the Dynamic Host Configuration Protocol. /TCPIPADDR=nnn.nnn.nnn.nnn This TCP/IP input identifies the local IP address. This field is required when DHCP is not selected (disabled). /TCPIPMASK=nnn.nnn.nnn.nnn Required. Specifies the local subnet mask. This field is required when DHCP is not selected (disabled). /TCPIPGATE=nnn.nnn.nnn.nnn Optional. Specifies the default gateway. This field is required when DHCP is not selected (disabled). /TCPIPDOMAIN=nnn.nnn.nnn.nnn Optional. Specifies the domain name. /NAMESERVER=nnn.nnn.nnn.nnn Optional. Use this parameter to identify the nameserver you will be using. You may specify more than one nameserver by coding this parameter more than once. Parameters for Class of Service /COSTCPRANGE=LLLLL-UUUUU,p This optional Class of Service input identifies a TCP Port Range and a priority value. The range consists of a Lower decimal value (lllll; can be 1 to 5 characters), a Upper decimal value (uuuuu; can be 1 to 5 characters), and a priority value 1 character). The Lower and Upper range values can be from 00000 to 65535. The upper value must be equal to or greater than the Lower value. The priority value can be any integer value from 1 to 6. Each TCP Port range must be identified with this input, for example, /COSTCPRANGE=80-80,4 or /COSTCPRANGE=12345-12345,6. The ranges cannot overlap in any way. A maximum of four Class of Service ranges can be specified (TCP and UDP combined). /COSUDPRANGE=LLLLL-uuuuu,p This optional Class of Service input identifies a UDP Port Range and a priority value. The range consists of a Lower decimal value (lllll; can be 1 to 5 characters), a Upper decimal value (uuuuu; can be 1 to 5 characters), and a priority value 1 character). The Lower and Upper range values can be from 00000 to 65535. The Upper value must be equal to or greater than the Lower value. The priority value can be any integer from 1 to 6. Each UDP Port range must be identified with this input, fora example, /COSUDPRANGE=80,4 or /COSUDPRANGE=12345-12345,6. The ranges cannot overlap in any way. A maximum of four Class of Service ranges can be specified (TCP and UDP combined).

PARAMETERS FOR ROUTE SWITCHING If you choose to install Route Switching by coding /ROUTESWENABLE, you can also specify the additional parameters described in this section. If you do not know the values to code for these parameters, contact your network administrator. /ROUTESWTABLESIZE=<####> Optional, Use this parameter to specify the Route Switching Table size. The value for this keyword must be an integer value between 16 and 1024. The default is 16. Parameters for Token-Ring ISA Adapters If you will be running IBM LAN Client using a Token-Ring ISA adapter, you will need to specify: /TRSHAREDRAM You can also specify the additional parameters described in this section. If you do not specify either /FTOKEN or /FTOKENSNAP, support will be installed for /FTOKEN unless you also code /TCPIP, in which case support for both frame types will be installed. If you code the /TRSHAREDRAM parameter, the TOKEN.LAN adapter device driver will be installed. /FTOKEN Optional. This parameter requests support for the normal Token-Ring frame format using the IEEE 802.2 LLC header. /FTOKENSNAP Optional. This parameter requests support for the Token-Ring frame format that uses an 8-byte SNAP header in place of the IEEE 802.2 header. This frame type is required only if you plan to use TCP/IP. /NODEADDR=############X Optional. Code this parameter if you want to specify a locally administered address to override the encoded address of your adapter. This field requires 12 hexadecimal digits, which can optionally be followed by either L or M. Coding L indicates that the address is in canonical format; coding M specifies that it is in Most Significant Bit (MSB) first format. Token-Ring addresses are traditionally expressed in MSB format, although universally administered addresses are assigned by the IEEE in canonical for mat. The valid range is 40000000000M-7FFFFFFFFFFFM. /MAXFRAMESIZE=#### Optional. Use this parameter to specify the maximum buffer size used by the Link Support Layer for your adapter. The valid range is 20-18000 bytes, the default is 4500 bytes. Parameters for Token-Ring Microchannel Adapters If you will be running IBM LAN Client using a Token-Ring Microchannel adapter, you will need to specify: /TRSHAREDRAMMC You can also specify the additional parameters described in this section. If you do not specify either /FTOKEN or /FTOKENSNAP, support will be installed for /FTOKEN only unless you also code /TCPIP, in which case support for both frame types will be insta lled. If you code the /TRSHAREDRAMMC parameter, the TOKEN.LAN adapter device driver will be installed. /FTOKEN Optional. This parameter requests support for the normal Token-Ring frame format using the IEEE 802.2 LLC header. /FTOKENSNAP Optional. This parameter requests support for the Token-Ring frame format that uses an 8-byte SNAP header in place of the IEEE 802.2 header. This frame type is required only if you plan to use TCP/IP. /NODEADDR=############X Optional. Code this parameter if you want to specify a locally administered address to override the encoded address of your adapter. This field requires 12 hexadecimal digits, which can optionally be followed by either L or M. Coding L indicates that the address is in canonical format; coding M specifies that it is in Most Significant Bit (MSB) first format. Token-Ring addresses are traditionally expressed in MSB format, although universally administered addresses are assigned by the IEEE in canonical for mat. The valid range is 400000000000M-7FFFFFFFFFFFM. /MAXFRAMESIZE=#### Optional. Use this parameter to specify the maximum buffer size used by the Link Support Layer for your adapter. The valid range is 20-18000 bytes. the default is 4500 bytes. Parameters for Auto LANStreamer Token-Ring PCI Adapters If you will be running IBM LAN Client using an Auto LANStreamer Token-Ring PCI adapter, you will need to specify: /TRPCI You can also specify the additional parameters described in this section. If you do not specify either /FTOKEN or /FTOKENSNAP, support will be installed for /FTOKEN only unless you also code /TCPIP, in which case support for both frame types will be insta lled. If you code the /TRPCI parameter, the IBMMPCO.LAN adapter device driver will be installed. Note: The IBMMPCO.LAN device driver is used for only the Auto LANStreamer PCI Adapter in this environment, it will not load correctly unless both TOKENTSM and ETHERTSM are already loaded. The installation program will include load statements for both TSMs when creating a STARTNET.BAT file that loads IBMMPCO.LAN. /FTOKEN Optional. This parameter requests support for the normal Token-Ring frame format using the IEEE 802.2 LLC header. /FTOKENSNAP Optional. This parameter requests support for the Token-Ring frame format that uses an 8-byte SNAP header in place of the IEEE 802.2 header. This frame type is required only if you plan to use TCP/IP. /NODEADDR=############X Optional. Code this parameter if you want to specify a locally administered address to override the encoded address of your adapter. This field requires 12 hexadecimal digits, which can optionally be followed by either L or M. Coding L indicates that the address is in canonical format; coding M specifies that it is in Most Significant Bit (MSB) first format. Token-Ring addresses are traditionally expressed in MSB format, although universally administered addresses are assigned by the IEEE in canonical for mat. The valid range is 400000000000M-7FFFFFFFFFFFM. /RXBUF=## Optional. Use this parameter to define the number of receive buffers used by the IBMMPCO.LAN driver. Valid values are: 4, 8, 16, 32, or 64; the default is 4. /TXBUF=## Optional. Use this parameter to define the number of transmit buffers used by the IBMMPCO.LAN driver. Valid values are: 1, 2, 4, 8, or 16; the default is 1. NOTE: For Auto LANStreamer this value is always forced to 1 and cannot be changed using this keyword. /DATARATE=## Optional. Use this parameter to specify the speed of the Token Ring you will be using, or to request that the adapter determine the speed itself. If the adapter makes the determination, it will configure itself accordingly. Coding /DATARATE=A will request that the adapter make the determination (auto-sense). Coding 16 specifies that you will be attached to a 16-Mbps ring, and coding 4 specifies that you will be attached to a 4-Mbps ring. The default for this parameter is A for auto-sense. /MAXFRAMESIZE=#### Optional. Use this parameter to specify the maximum buffer size; used by the Link Support Layer for your adapter. The valid range is 20-18000 bytes, the default is 4500 bytes. Parameters for Token-Ring PCI Family Adapters If you will be running IBM LAN Client using a Token-Ring PCI Family Adapter, you will need to specify: /TRPCI2 You can also specify the additional parameters described in this section. If you do not specify either /FTOKEN or /FTOKENSNAP, support will be installed for /FTOKEN only unless you also code /TCPIP, in which case support for both frame types will be insta lled. If you code the /TRPCI2 parameter, the IBMTRPO.LAN adapter device driver will be installed. /FTOKEN Optional. This parameter requests support for the normal Token-Ring frame format using the IEEE 802.2 LLC header. /FTOKENSNAP Optional. This parameter requests support for the Token-Ring frame format that uses an 8-byte SNAP header in place of the IEEE 802.2 header. This frame type is required only if you plan to use TCP/IP. /NODEADDR=############X Optional. Code this parameter if you want to specify a locally administered address to override the encoded address of your adapter. This field requires 12 hexadecimal digits, which can optionally be followed by either L or M. Coding L indicates that the address is in canonical format; coding M specifies that it is in Most Significant Bit (MSB) first format. Token-Ring addresses are traditionally expressed in MSB format, although universally administered addresses are assigned by the IEEE in canonical for mat. The valid range is 400000000000M-7FFFFFFFFFFFM. /RXBUF=## Optional. Use this parameter to define the number of receive buffers used by the IBMTRPO.LAN driver. Valid values are: 4, 8, 16, 32, or 64; the default is 4. /TXBUF=## Optional. Use this parameter to define the number of transmit buffers used by the IBMTRPO.LAN driver. Valid values are: 1, 2, 4, 8, or 16; the default is 2. /DATARATE=## Optional. Use this parameter to specify the speed of the Token Ring you will be using, or to request that the adapter determine the speed itself. If the adapter makes the determination, it will configure itself accordingly. Coding /DATARATE=A will request that the adapter make the determination (auto-sense). Coding 16 specifies that you will be attached to a 16-Mbps ring, and coding 4 specifies that you will be attached to a 4-Mbps ring. The default for this parameter is A for auto-sense. /MAXFRAMESIZE=#### Optional. Use this parameter to specify the maximum buffer size used by the Link Support Layer for your adapter. The valid range is 20-18000 bytes; the default is 4500 bytes. /ROUTESWENABLE=CLIENT,PEER,AUTO This option will enable Route Switching . The default is 'AUTO'. /ROUTESWTABLESIZE=<####> This optional input will specify the Route Switching Table Cache size. The value for this keyword must be and integer value between 16 and 1024. The default is 1024. Parameters for Token-Ring Credit Card Adapters If you will be running IBM LAN Client using a Token-Ring Credit Card adapter, you will need to specify: /TRCC or /TRCC2 You can also specify the additional parameters described in this section. If you do not specify either /FTOKEN or /FTOKENSNAP, support will be installed for /FTOKEN unless you also code /TCPIP, in which case support for both frame types will be installed. If you code the /TRCC parameter, the TOKEN.LAN adapter device driver will be installed. The /TRCC2 keyword is used to identify the adapter to be installed as a Turbo 16/4 Token-Ring Credit Card Adapter. Optional inputs include: /FTOKEN Optional. This parameter requests support for the normal Token-Ring frame format using the IEEE 802.2 LLC header. /FTOKENSNAP Optional. This parameter requests support for the Token-Ring frame format that uses an 8-byte SNAP header in place of the IEEE 802.2 header. This frame type is required only if you plan to use TCP/IP. /NODEADDR=############X Optional. Code this parameter if you want to specify a locally administered address to override the encoded address of your adapter. This field requires 12 hexadecimal digits, which can optionally be followed by either L or M. Coding L indicates that the address is in canonical format, coding M specifies that it is in Most Significant Bit first format. Token-Ring addresses are traditionally expressed in MSB format, although universally administered addresses are assigned by the IEEE in canonical format. T he valid range is 40000000000M-7FFFFFFFFFFFM. /DATARATE=## Optional. Use this parameter to specify the speed of the Token Ring you will be using, or to request that IBM LAN Client determine the speed itself. If IBM LAN Client makes the determination, it will configure the adapter accordingly. Coding /DATARATE=A w ill request that IBM LAN Client make the determination (auto-sense). Coding 16 specifies that you will be attached to a 16-Mbps ring, and coding 4 specifies that you will be attached to a 4-Mbps ring. The default for this parameter is A for auto-sense. /MAXFRAMESIZE=##### Optional. Use this parameter to specify the maximum buffer size used by the Link Support Layer for your adapter. The valid range is 20-18000 bytes, the default is 4500 bytes. /ENABLER=## Optional. Use this parameter to select the software interface method to be used to access the credit card adapter. Card services is usually easier to configure and more flexible but requires more DOS memory. The Point Enabler requires less memory, but you must understand how your machine is configured so that you do not specify resource values that conflict with other hardware in your machine. Valid inputs are CS for the Card Services Enabler and PT for the Point Enabler; the default is PT. /SOCKET=# Optional. If you are using the Point Enabler, use this parameter to specify the PCMCIA socket used for the adapter. Valid values are A, B, C, or D; the default is A. /MMIOADDR=#### Optional. Use this parameter to specify the Memory Mapped IO Address for the adapter. Valid values are from C000 to DE00 on 8 KB boundaries; the default is D600. /SRAMSIZE=## This input identifies the Shared RAM memory size. Valid values are 8, 16, 32, 64 KB; the default is 16 KB. NOTE: Valid only for the Auto 16/4 Token-Ring Credit Card adapter. /SRAMADDR=#### This input identifies the Shared Ram Address. Valid values are from C000 to DC00; the default is D800. If the /SRAMSIZE is 8 or 16 KB the Address must be on a 16 KB boundaries. The boundary is 32 and 64 KB for the 32 and 64 KB memory sizes, respectively. NOTE: Valid only for the Auto 16/4 Token-Ring Credit Card adapter. /IO=### This input is optional for single LAN adapter installation. This option will specify the Hex IO address of your adapter. Valid values are A20 and A24 for the Auto 16/4 Token-Ring Credit Card adapter, and 300 to FEC for the Turbo 16/4 Token-Ring Credit Car d adapter. The default for both adapters is A20. /IRQ=## Optional. Use this parameter to specify the interrupt level to be used by the PCMCIA controller for your adapter. Valid values are 3 to F (hexadecimal); the default is 9. Application-Specific Installation Information Installing DOS LAN Requester The IBM LAN Client installation program does not support installation of DLR 3.0. If you want to run DLR 3.0 with IBM LAN Client, follow the instructions listed here: ƒ Install LCINST as described in the preceding section, or make the directory in which you previously installed LCINST the current directory, and type LCINST Then, press Enter. ƒ Proceed through the LCINST panels. Make sure that the DOS-only box is checked even if you are running Windows. Also, make sure to select NetBIOS on the protocol panel. ƒ Restart your workstation. ƒ Install DLR, using the installation instructions that came with it. The DLR installation program will copy the necessary programs and update CONFIG.SYS and AUTOEXEC.BAT. ƒ Restart your workstation. Installing DOS LAN Services GUI or DDE Support The IBM LAN Client installation diskettes do not include the GUI or DDE support of DLS 5.x. The version on the installation diskettes is fully functional, except that it does not provide the GUI interface or DDE support. If you do not need the GUI interfa ce or DDE support, you do not need to follow the instructions in this section. If you want to run the GUI version or add DDE support, follow the instructions listed here: ƒ Install DLS, using the installation instructions that came with it, before using the LCINST program. (You can install the LCINST program itself, but do not use it to install IBM LAN Client before installing DLS.) Use whatever DLS options you need, ex cept that you must specify "default" for the protocol, and "no network card". ƒ Do not reboot your machine after installing DLS. ƒ Edit your CONFIG.SYS file and remove (or remark out) the following two lines: ƒ DEVICE=C:\NET\PROTMAND.DOS ƒ DEVICE=C:\NET\IBMTOK.DOS ƒ Install LCINST as described in the preceding section, or make the directory in which you installed LCINST the current directory, and type LCINST Then, press Enter. ƒ Proceed through the LCINST panels, making sure to select NetBIOS on the protocol panel. ƒ Restart your workstation. Installing with Artisoft's LANtastic The installation program for IBM LAN Client creates a file named STARTNET.BAT that is called from AUTOEXEC.BAT at load time. The installation program for Artisoft's LANtastic also creates a STARTNET.BAT file. Whichever installation program is run second w ill remark out the line in AUTOEXEC.BAT that invokes the first program. In addition, there is a statement in the LANtastic file that is incompatible with IBM LAN Client and IBM LAN Client installation. IBM LAN Client installation removes some lines in SYS TEM.INI that LANtastic requires. You therefore need to do the following things when installing both IBM LAN Client and LANtastic: ƒ Install IBM LAN Client first. ƒ Install LANtastic in a different directory. ƒ After installing LANtastic, edit AUTOEXEC.BAT and insert IBM LAN Client's STARTNET.BAT line that was removed by the LANtastic installation program. Make sure that the line that references STARTNET.BAT for IBM LAN Client is before the line that refere nces STARTNET.BAT for LANtastic. ƒ Change the following line in the LANtastic STARTNET.BAT: AILANBIO @STARTNET.BAT to read: rem AILANBIO @STARTNET.BAT Note: A client running Lantastic's NetBIOS cannot communicate with a client running Lan Client's NetBIOS. Installing with Novell's LAN Workplace The TCP/IP support shipped with IBM LAN Client provides backwards compatibility for Novell's LAN Workplace applications. This requires some additional installation steps. ƒ You must use the WLIBSOCK.DLL and winsock.dll files from the IBM LAN Client installation, not those from the Novell LAN Workplace installation. ƒ If your version of Novell's LAN Workplace required a "device=vtcpip.386" line in the Window's SYSTEM.INI file, you need to delete or remark out that line. ƒ If you install Novell's LAN Workplace after you install IBM LAN Client, you must remove the line referencing STARTNET.BAT that was added to your AUTOEXEC.BAT file by the LAN Workplace installation. ƒ The IP address information will be provided by the IBM LAN Client installation program. If you installed LAN Workplace to a directory other than NET, you will need to replace NET in the PATH statements with the correct directory. A sample NET.CFG sec tion could look as follows: PROTOCOL TCPIP PATH SCRIPT C:\NET\SCRIPT PATH PROFILE C:\NET\PROFILE PATH LWP_CFG C:\NET\HSTACC PATH TCP_CFG C:\NET\TCP IP_ROUTER 130.57.4.254 IP_NETMASK 255.255.252.0 IP_ADDRESS 130.57.6.129 Note: The version of winsock.dll that is provided on your IBM LAN Client installation diskettes is for use only with IBM LAN Client TCP/IP. It complies with the Winsock 1.1 and 1.2 specifications and supports both 16-bit and 32-bit applications and DLLs u nder Windows 3.1x. Installing with NetManage's Chameleon If you are installing both IBM LAN Client and NetManage's Chameleon at the same time, install IBM LAN Client first. Be sure to install IBM LAN Client TCPIP support. Then, install Chameleon, making sure that you do not set up an interface, and do the follo wing things: ƒ Edit the CONFIG.SYS file and remove or remark out any references to PROTMAN.DOS, and any references to an NDIS adapter device driver (files with an extension of .DOS). ƒ Edit the AUTOEXEC.BAT file and remove or remark out any references to NETBIND.EXE. ƒ Edit the SYSTEM.INI file in the WINDOWS directory and remove the line: DEVICE=drive:\path\NMTCPIP.386 ƒ Rename the NetManage winsock.dll to winsock.net. You will find winsock.dll in the directory in which you installed Chameleon. If you already have Chameleon installed, when you install IBM LAN Client, follow steps 3 and 4 above. Note: The version of PING shipped with NetManage's Chameleon will not work in this environment. Use the PING shipped with IBM LAN Client. The TCPIP.NLM shipped with IBM LAN Client will provide the TCP protocol support. Using the WINSOCK Apps from IBM TCP/IP Version 2.x for DOS If you are installing IBM LAN Client and want to use some of the IBM TCP/IP Version 2.x Windows TCP apps at the same time, install IBM LAN Client first. Then, install TCP/IP for DOS and do the following things: ƒ Edit the CONFIG.SYS file and remove or remark out any references to PROTMAN.DOS and any references to an NDIS adapter device driver (files with an extension of .DOS). ƒ Edit the CONFIG.SYS file and remove or remark out any references to C:\TCPDOS\BIN\DOSTCP.SYS. ƒ Edit the AUTOEXEC.BAT file and remove or remark out any references to C:\TCPDOS\BIN\INET.EXE. ƒ Edit the AUTOEXEC.BAT file and remove or remark out any references to NETBIND.EXE. ƒ Use CUSTOM to configure for Windows. ƒ Rename winsock.dll supplied with TCP/IP for DOS to winsock.net. The winsock.dll should be in the TCPDOS\BIN subdirectory. Copy the winsock.dll that comes with LAN Client into the TCPDOS\BIN subdirectory. The IBM LAN Client winsock.dll should be in th e C:\LNCLIENT subdirectory. ƒ Copy the HOSTS and SERVICES file from the TCPDOS\ETC directory into the LNCLIENT subdirectory. Note: The version of PING shipped with IBM TCP/IP for DOS will not work in this environment. Use the PING shipped with IBM LAN Client. Only IBM TCP/IP FTP Client and Telnet client have been tested to work with IBM Lan Client. Using the WINSOCK Apps from IBM Internet Connection for Windows Version 5.x If you are installing IBM LAN Client and want to use some of the IBM Internet Connection for Windows Version 5.x Windows TCP apps at the same time, install IBM LAN Client first. Then, install Internet Connection for Windows and do the following thing: ƒ Install Internet Connection for Windows using the Custom Install path and deselect the Internet Connection TCP/IP Network Component. ƒ Copy the winsock.dll that comes with LAN Client into the ICW\BIN subdirectory. The IBM LAN Client winsock.dll should be in the C:\LNCLIENT subdirectory. ƒ Copy the HOSTS and SERVICES file from the ICW\ETC directory into the LNCLIENT subdirectory. Note: If you already installed Internet Connection for Windows with the Internet Connection TCP/IP Network Component, you need to completely remove Internet Connection for Windows (including the references in your Windows SYSTEM.INI file), and then reinst all your Internet Connection for Windows. Installing IBM LAN Client from a Network Server If you are installing IBM LAN Client on a number of machines that already have working network connections, you might want to put the contents of the IBM LAN Client diskettes on your LAN server and install to the client machines from the server. In order to put the installation programs and the IBM LAN Client code on your server, follow these steps: ƒ Copy all of the files on all four diskettes into a directory of your choice, using the command: XCOPY A:\*.* /S ƒ Switch to the directory to which you copied the files and edit the file FILELIST.DAT. You need to delete the following files from the list: LCINSTC.EXE, LCINSTC.MSG, GETPARMS.MSG, DDPRINS.MSG, INSTALL.LST, and RLCINST.BAT. ƒ Run INSTALL.EXE, specifying the directory to which you copied the files from the diskettes. For example, if you copied the files to F:\NETINST, you would type: INSTALL F:\NETINST You can now install IBM LAN Client on your client machines by specifying the correct server drive and directory when executing LCINST or LCINSTC. Note: This document is included with the Internet/bulletin board version of IBM LAN Client and also with adapter-specific versions of IBM LAN Client that use LANAID instead of LCINST for their installation program. These network instructions apply only to the Internet/bulletin board version of IBM LAN Client. Because LANAID interacts with the network adapter (LCINST does not), network installations using LANAID will not work with some adapters. Installation and Load-Time Messages For information about messages from application programs, please refer to the application's documentation. For information about messages from adapter device drivers, please refer to the adapter's documentation. This section includes messages written by t he installation programs, LCINST and LCINSTC, and messages written at load time by IBM LAN Client components. Both installation programs begin by writing messages indicating which version of IBM LAN Client will be installed: Installation for IBM LAN Client Version 3.0 (With Novell's IntranetWare Client for DOS/Windows 3.1x) (C) Copyright IBM Corporation 1995. US Government users restricted rights - use, duplication, or disclosure restricted by GSA ADP schedule contract with IBM Corporation. The installation program will create a STARTNET.BAT file with message logging disabled. Some modules write load-time messages to a log file, and some modules write run-time messages to a log file. If you are experiencing problems, you might want to activa te message logging. To activate message logging, you need to add /L to the load line for NIOS.EXE in STARTNET.BAT. The messages will be logged to a file named NIOS.LOG in the directory in which the IBM LAN Client modules are located. This file is not auto matically erased, so once you activate logging, it will continue to grow in size. Installation Program Messages The messages in this section may be written by either the GUI or command-line installation programs. The installation program will create a log file containing the messages that were written to the screen during installation. The log file is named LCINST.LOG, and will be in the directory in which IBM LAN Client will be installed. The following messages w ill be written to only the log file: The following files have been created in the drive:\path directory, and they need to replace the files listed below. drive:\path\filename.ext For the installed protocols to function correctly, remove or rename the following files: drive:\path\filename.ext Do not leave blank lines in FILELIST.DAT since they will cause the Install program to fail. Note: These messages are written only if you select /NOUPDATE, to prevent the installation from updating your configuration files. If these messages are written to the log file, a message will be written to screen to tell you that you need to check the lo g file. The following messages are for your information only, and do not indicate that an error has occurred. Installing IBM LAN Client ... Installing Windows support for IBM LAN Client... No update needed. n files installed. Installation complete. Logging installation to drive:\path\filename.ext Installation logged to drive:\path\filename.ext Insert disk N into the disk drive, then select Insert disk N and press any key, press ESC to cancel. (LCINSTC only.) Searching drive DRIVE: for Windows. Windows directory found. Checking to see if IBM LAN Client exists on your computer. IBM LAN Client does exist on your computer and is being removed. IBM LAN Client has been deactivated in the CONFIG.SYS and AUTOEXEC.BAT files. IBM LAN Client has been deactivated in the Windows files. Searching your computer for existing networking software that may conflict with IBM LAN Client. IBM LAN Client will deactivate networking software that was found on your computer. The changes will be included in the AUTOEXEC.BAT and CONFIG.SYS files that are created for this installation. IBM LAN Client will deactivate networking software that was found on your computer. The changes will be included in the SYSTEM.INI file created for this installation. Checking for the existence of files that may require renaming or removal in order to facilitate the installation of DOS LAN Services. The following file has been renamed from drive:\path\filename.ext to drive:\path\filename.ext. No files requiring renaming or removal were found. You requested that the IBM LAN Client installation not update your computer configuration. For instructions on how to update your machine configuration, please see drive:\path\filename.ext. An error occurred during the backup phase of updating your computer configuration files, installation switched to the /NOUPDATE mode. For instructions on how to update your machine configuration, please see drive:\path\filename.ext. Backing up drive:\path\filename.ext to drive:\path\filename.ext. New configuration file has been written to drive:\path\filename.ext. Loading computer configuration files that may require updates. Installation list file, drive:\path\filename.ext is being copied temporarily to hard drive. Installation list file, drive:\path\filename.ext is being removed from hard drive. Restoring modified files drive:\path\filename.ext The following messages indicate that the installation program has encountered an error and cannot install or remove IBM LAN Client. They will be preceded by the word ERROR:. Please correct the problem and rerun the program. Out of memory. Installation failed. Cannot restore configuration files. Insufficient disk space to install IBM LAN Client. NN bytes of disk space required. Insufficient disk space to install Windows support for IBM LAN Client. NN bytes of disk space required. Another network operating system may be loaded on this machine already. Log file could not be opened. Installation list file, drive:\path\filename.ext cannot be found to be copied. TCPIP installation requires Windows, it will not be installed. WARNING: No extended memory manager was detected in the CONFIG.SYS file. An extended memory manager such as HIMEM.SYS is required for the IBM LAN Client software. Required diskette was not inserted. Installation cannot complete. File required to generate a Windows group file could not be found. IBM LAN Client removal cannot continue. Unable to open AUTOEXEC.BAT. Unable to open STARTNET.BAT. Windows directory not found. The Windows directory specified is a Windows 95 directory. Windows 95 is not supported at this time. The Windows directory specified is a Windows NT directory. Windows NT is not supported at this time. Unable to update file drive:\path\filename.ext. IBM LAN Client deactivation did not complete. DOS configuration files could not be backed up. Windows configuration files could not be backed up. IBM LAN Client could not be found and therefore cannot be deactivated. Existing networking software that conflicts with IBM LAN Client may exist on your computer. It could not be removed because temporary DOS configuration files could not be created. Existing networking software that conflicts with IBM LAN Client may exist on your computer. It could not be removed because temporary Windows configuration files could not be created. Warning, an attempt to backup the configuration file, drive:\path\filename.ext has failed. It will not be overlaid by the new configuration file. The installation will continue in the /NOUPDATE mode. Cannot open input file: drive:\path\filename.ext. Cannot open output file: drive:\path\filename.ext. Error reading input file: drive:\path\filename.ext. Error writing output file: drive: \path\filename.ext. Not enough memory to read input file: drive:\filename.ext. File already exists: drive: \path\filename.ext. Restoring from backup, drive:\path\filename.ext to drive: \path\filename.ext has failed. The file does not exist, installation will continue. You cannot run this program from a DOS box under OS/2. You will need to boot DOS and rerun this program. The Point Enabler was selected for this installation, but Card Services was found on your machine. Please rerun the installation and select the Card Services Enabler. The Card Services Enabler was selected for this installation but, Card Services was not found on your machine. Please rerun the installation and select the Point Enabler. LCINSTC Installation and Load-Time Messages The messages in this section are written by the command line installation program. You will not see any of these messages if you use only the GUI installation program. Most of these messages are self-explanatory. If you have coded an invalid value for a p arameter, refer to the relevant section of this document for information on how to code it correctly. The following messages are for information only, and do not indicate that an error has occurred. ---- Press any key to continue, to exit --- No Help Available IBM LAN Client has been deactivated on your computer. Installation of IBM LAN Client has completed successfully. Reboot your machine for the changes to take effect. LCINSTC does not check the credit card parameters specified on the Hardware folder against those currently specified by card services or the point enabler. Make sure to enter the same values you are currently using unless you intend to make changes. The following messages indicate that an error has occurred. They will be preceded by the word ERROR:. Correct the problem, and run the installation program again. Parameter /FILE= cannot be used in a file. Invalid NetWare directory. Invalid Windows directory. Invalid Node Address, parameter ignored Invalid value for parameter /RXBUF (number of receive buffers): value Invalid value for parameter /TXBUF (number of transmit buffers): value Invalid value for parameter /DATARATE: value Invalid value for parameter /TCPIPADDR: value Invalid value for parameter /TCPIPASK: value Invalid value for parameter /TCPIPGATE: value Invalid value for parameter /MACHID: value Invalid value for parameter /USERNM: value Invalid value for parameter /DOMAINNM: value Invalid value for parameter /TCPIPDOMAIN: value Invalid value for parameter /NAMESERVER: value Invalid value for parameter /PREFERREDSERVER: value Invalid value for parameter /AUTORECONLEVEL: value Invalid value for parameter /FIRSTNERDRIVE: value Invalid value for parameter /MAXFRAMESIZE: value Invalid value for parameter /ENABLER: value Invalid value for parameter /SOCKET: value Invalid value for parameter /MMIOADDR: value Invalid value for parameter /SRAMSIZE: value Invalid value for parameter /SRAMADDR: value Invalid value for parameter /IRQ: value Unknown parameter: parameter IBM LAN Client will not be installed. Required adapter parameter information not provided. Required protocol parameter information not provided. Required parameter, parameter not specified. Parameter, parameter is not allowed. All required parameters for TCP/IP were not specified. All required parameters for DLS were not specified. Novell IntranetWare Client option specified without corresponding protocol parameter. NetBIOS or DLS option specified without corresponding protocol parameter. DLS option specified without corresponding protocol parameter. TCP/IP option specified without corresponding protocol parameter. Windows directory must be specified for TCP/IP support. Windows directory must be specified for Windows DLS support. Required parameter, parameter not specified for protocol. Required parameter, parameter is not allowed for protocol. Could not open file: drive: \path\filename.ext. /WINDIR was not specified, and Windows directory could not be found. Deactivation of already installed IBM LAN CLIENT did not include Windows configuration files. /WINDIR was specified but invalid, and a Windows directory could not be found. Deactivation of already installed IBM LAN CLIENT did not include Windows configuration files. Windows support cannot be installed for both IBM LAN Client and DOS LAN Services. Error occurred while gathering parameter information, installation terminated. Currently, LCINSTC supports single-adapter installations only. More than one adapter was specified. IBM LAN Client installation encountered a problem during execution. Please refer to earlier messages to identify the problem. Invalid value for parameter /ENABLER: value. Valid values are CS (Card Services) and PT (Point Enabler). The shared RAM address is not on the correct boundary for the specified shared RAM size, /SRAMADDR: value, /SRAMSIZE: value. No adapter type was specified. ƒ Installation cannot continue. ƒ Installation cancelled by user. Insufficient disk space exists to complete installation. At least one of the following files is write protected drive:\path\filename.ext These files must be unprotected for the installation to proceed. CCB1API Load-Time Messages The CCB1API module provides backwards compatibility for programs using the 16-bit CCB1 interface. It will display the following copyright messages when loaded into memory: IBM IEEE 802.2 CCB1 API Mapper v x.xx (C) Copyright IBM Corporation 1995. All rights reserved. If CCB1API loads correctly, it will not write any messages other than the copyright message. If CCB1API encounters a problem while loading, it will write one of the following error messages. The messages should be self-explanatory. CCB1API: 5C interrupt vector could not be hooked CCB1API: Memory for nested execution could not be allocated CCB1API: No conventional memory available CCB1API: Unable to process parameters parm parm for keyword keyword CCB1API: Could not find board using parameters parm parm for keyword keyword CCB1API: Board n specified for keyword keyword does not support 802.2 frame type NNetBIOS Load-Time Messages There are only two NNetBIOS load time messages: NIOS NetBIOS NLM Copyright IBM, 1996. All rights reserved. Unable to allocate NIOS memory for ACB. NCBRMAPI Load-Time Messages There are three NCBRMAPI load-time messages. No conventional memory available. 5C interrupt could not be hooked. IBM Translation NLM Version 1.0. Copyright IBM, 1996. All rights reserved. NLLC8022 Load-Time Messages The NLLC8022 module implements the IEEE 802.2 protocol support. It will display the following copyright messages when loaded into memory: NIOS LLC 802.2 v x.xx Copyright 1992 Novell, Inc. IBM, 1995. All rights reserved. NLLC8022 will write the following informational message if it loads correctly: NLLC8022: BOUND to board n. NLLC8022 might also write the following error messages at load time. The messages should be self-explanatory. NLLC8022: Unable to allocate memory while binding to board n. NLLC8022: Unable to process bind parameters parm parm. NLLC8022: Could not find board to bind to using parameters parm parm. NLLC8022: Board n does not support 802.2 frame type. NLLC8022: Already bound to board n. NLLC8022: n is an invalid board number. Troubleshooting Tips The combination of IBM LAN Client and some application programs can occasionally result in error messages whose cause is not immediately obvious. This section documents known situations that might cause problems. NetWare Client shutdown message when Ctrl-Alt-Del You get the message Please wait while the NetWare Client shuts down but you are not running the NetWare Client, only 802.2, NetBIOS, or DOS LAN Services. The IBM LAN Client code is built using the Novell NIOS operating system support, which issues this me ssage any time the NIOS environment is shut down, even if Novell IntranetWare Client is not loaded. Windows load error: "vvland.386 could not find NetBIOS Interface" This error message can be encountered if PC3270 for Windows is installed, but NetBIOS support is not needed. If you see this message, update your SYSTEM.INI file to remark out the load line for vvland.386. To remark out the load line use a semi-colon as t he first character of the line loading vvland.386. SYSTEM.INI should be in your WINDOWS directory, normally C:\WINDOWS. DLS error message: "No PROTMAN loaded" This message is written by DOS LAN Services if it cannot find NetBIOS. You might see this message if one of the IBM LAN Client files failed to load out of STARTNET.BAT. Occasional hangs with PC3270/DOS If you are running Version 4.x, install CSD2. If you are running Version 3.0 or 3.1, install CSD4. Task Switching errors DOS Task Switching Applications (such as Wordperfect for DOS and Groupwise for DOS) are not supported with IBM LAN Client. You will need to disable the task-switching function when using such applications. (Starting WordPerfect with the /dl option, or Gro upwise with the /da option, for example). Also, note that if enhanced-mode Windows is started with insufficient free extended memory, it will attempt to start in standard mode with task switching. Ctrl-Alt-Del (soft reboot) hangs with EMM386 In certain situations when EMM386 and IBM LAN Client are loaded together, a soft reboot produces a hang. The following situations are known to cause problems: ƒ The EMMM386 version shipped with MSDOS 5.0 has problems handling a soft reboot when code is executing in protect mode. Version 4.44 of EMM386 does not have this problem, and users of IBM LAN Client should be running version 4.49 or higher. ƒ Compaq machines with a pre-1990 BIOS running EMM386 and IBM LAN Client will hang when a soft reboot is issued. If you have this problem, you will either need to upgrade the BIOS or use a DOS memory manager other than EMM386. ƒ On some machines (particularly Compaq laptops) a RAM or NOEMS parameter must be coded on the EMM386 load line in CONFIG.SYS to prevent the soft reboot hang. EMM386 ERROR #12 If error 12 is occurring, this indicates that a stack is being used incorrectly. Try adding the following command to your CONFIG.SYS file: STACKS=18,512 MEM POOL SIZE error message on exiting Windows You will need to increase the memory available to Windows by adding the following line to your NET.CFG file in the NIOS section. MEM POOL SIZE xxx Where "xxx" is the number of kilobytes to allocate. If there is no NIOS section already in the file, you would code: NIOS MEM POOL SIZE xxx Machine hangs when running Attachmate in the foreground with another application in the background You need to change the Attachmate configuration. By default, Attachmate is set up to run concurrently with other applications; you need to change this option to non-concurrent. To do this you need to run the Attachmate Configuration program. You are using WordPerfect and the dots that return you to the directory are not shown. Add the parameter SHOW DOTS=ON to NET.CFG under the NETWARE DOS REQUESTER section. You are using NetWare Server. You must install a patch to ensure that your drive mappings will remain intact. Copy PATCHMAN.NLM and SHORTAFX.NLM from the LAN Client directory to the SYS:SYSTEM directory of the 3.11 Server. Type LOAD PATCHMAN and LOAD SHORTAFX to execute the patch. Add the load commands to AUTOEXEC.NCF to allow for server reboots. Bridging Considerations IBM LAN Client includes a module named SROUTE.NLM, which provides support for source-route bridging. If you are using a Token-Ring adapter, the load statement for SROUTE.NLM will be included in your STARTNET.BAT file. If your Token-Ring network is using o nly source-route bridging, you will have no problems. If your Token-Ring network is using only transparent bridging, you will need to remove the load line for SROUTE.NLM from your STARTNET.BAT file. If you have a network that uses both transparent and source-route bridging, you will need to add parameters to the load line for SROUTE.NLM. SROUTE.NLM will normally look for unknown stations using frames with a routing information field. These frames wil l allow a station to be found if there a path through a Source Route bridge. If the path is through a transparent bridge, SROUTE.NLM needs to discover that path using a frame with no routing information field. If you have a mixed network, change the LOAD SROUTE line in your STARTNET.BAT file as follows: LOAD SROUTE BOARD=0 TRA=n TRO=n If you have more than one board you will need multiple statements. The parameter TRA (This Ring Alternate) specifies how many discovery frames with a routing information field should be sent before switching to frames with no routing information. The parameter TRO (This Ring Only) specifies how many discovery frames with out routing information should be sent before switching to frames with routing information. The suggested value for n is 2. Configuring a TCP/IP Hosts File If you are not using Novell's LAN Workplace, you may need set up a HOSTS file to define the host name you are using. You will need to create a file named HOSTS containing the address, hostname, and alias. This file should be in the subdirectory identified in the TCP_CFG path entry in the PROTOCOL TCPIP section of NET.CFG. Insufficient Environment Space Some users may encounter messages stating that the environment space needs to be increased. To increase the environment space, edit your CONFIG.SYS. The /E on the following line sets the environment space: shell=c:\dos\command.com /e:1024 /p 1024 is usual ly sufficient for LAN Client. Information about Configuration Files Information about NET.CFG NET.CFG is used to hold configuration information and parameters for the client applications and protocols you choose to run. The installation program will create the file based on your input, and you should not need to change it. If you want more informa tion on the parameters, and you are running Windows, you can look at the file NWCFGDW.HLP. This file should be in the subdirectory \NLS\ENGLISH under the directory in which you installed Windows: for example, C:\WINDOWS\NLS\ENGLISH. One reason for changing the parameters in NET.CFG is to change the duration of the IEEE 802.2 timers. There is detailed information on how to do this in "Timer Tick Values" on page 21. You might also need to change this file to set the maximum frame size that will be used for your adapter. To do this, add the following lines to the NET.CFG file: LINK SUPPORT MAX BUFFER SIZE xxxxx Where xxxxx is the value in bytes. Although you might request a maximum frame size using this method, the frame size actually used for any given connection might be different. The frame size can be affected by negotiations between the two end stations, or by the capabilities of any bridges in the path between them. Information about STARTNET.BAT STARTNET.BAT contains the statements that need to be executed when you bring up your workstation to load IBM LAN Client. The load statements for the adapter device driver and for the NetBIOS protocol code allow parameters to be specified; other parameters are stored in NET.CFG. Below is a sample STARTNET.BAT file for a Token-Ring ISA adapter using the Novell Intranetware Client and IEEE 802.2 protocols. SET NWLANGUAGE=ENGLISH CD \ CD C:\LNCLIENT NIOS.EXE LOAD LSL LOAD CMSM LOAD TOKENTSM LOAD TOKEN FRAME=TOKEN-RING LOAD SROUTE LOAD IPX LOAD CLIENT32 LOAD NLLC8022 LOAD CCB1API C: CD \ Here is an example for the Token-Ring PCI adapter using NetBIOS and IEEE 802.2. SET NWLANGUAGE=ENGLISH CD \ CD C:\LNCLIENT NIOS.EXE LOAD LSL LOAD CMSM LOAD TOKENTSM LOAD ETHERTSM LOAD IBMMPCO FRAME=TOKEN-RING LOAD SROUTE LOAD NLLC8022 LOAD CCB1API LOAD NNETBIOS LOAD NCBRMAPI C: CD \ Note that each load line in the STARTNET.BAT file will actually be followed by a line that reads: IF ERRORLEVEL 1 PAUSE This will cause the execution of the STARTNET.BAT file to pause if an error is encountered, thus ensuring that you are aware that the error has occurred. You can resume execution by pressing ENTER. NetBIOS Parameters There are a number of NetBIOS parameters that are not included in the installation process because they are not often changed. To change the default values for these parameters, you must edit the NET.CFG file and put them in a section for NNetBIOS. If you code more than one parameter, use a blank as the separator. Configuration parameter NetBIOS parameters are specified in the NET.CFG section for NetBIOS configuration. Most parameter values are per adapter. Parameters that apply to all adapters are noted as global. There are no required parameters. Note: In the text below, "processed" means read from NET.CFG and saved in some variable, initiating any relevant processing. The NetBIOS parameters are as follows: ReceiveBuffers This global parameter determines the number of receive buffers (SAP buffers) in the buffer pool, per adapter. It is a global parameter because the value is used before the ACB exists. Must be a decimal value from 2 to 24. If omitted or 0, the default is 6. UseAddrMsb This parameter specifies whether the address used for the NCB.STATUS network address and NAME_NUMBER_1 is Most Significant Bit (MSB) order or Canonical. If set to YES, the network address used in the NCB.STATUS command and in NAME_NUMBER_1 will be MSB (if the address is 010203040506, it will be saved as 060504030201). The default is YES. UseMaxDatagram This parameter specifies whether to request the full transmit buffer size for datagrams. If this parameter is set to NO, which is the default, the length of a datagram has a maximum of 512 bytes. Set this parameter to YES if you require the full transmit buffer size for datagrams. TI Sets the inactivity timer. This value is correlated to a time interval specified in the NLLC8022 configuration parameters. The TI inactivity timer determines how long to wait before generating a DLC status if there is no link-station traffic. Must be a de cimal number from 0 to 10. If omitted or 0, the default is 10. T1 Sets the response timer. This value is correlated to a time interval specified in the NLLC8022 configuration parameters. The T1 response timer determines the delay before retransmitting a link-level frame if no acknowledgment is received. Must be a decima l value from 0 to 10. If omitted or 0, the default is 5. T2 Sets the receiver acknowledgment timer. This value is correlated to a time interval specified in the NLLC8022 configuration parameters. The T2 acknowledgment timer determines the delay before acknowledging a received frame when the receive window has not been reached. Must be a decimal value from 0 to 11. If omitted or 0, the default is 2. If the value is 11, the T2 timer function is not implemented. MaxIn This parameter specifies the number of NetBIOS message packets to receive before sending an acknowledgment. The MaxOut parameter value should be less than or equal to the MaxIn parameter value. The range is 1-127. If omitted or 0, the default is 1. MaxOut This parameter specifies the number of NetBIOS message packets to send before expecting an acknowledgment. The MaxOut parameter value should be greater than the MaxIn parameter value. The range is 1-127. If omitted or 0, the default is 1. NetBIOSTimeout Sets the transmit timeout in 1/2-second periods. This is the time between transmission of queries (for instance, CALL). Must be a decimal number from 0 to 20. If omitted or 0, the default is 1 (1/2 second). Refer to the NetBIOSRetries parameter for more i nformation. NetBIOSRetries This parameter specifies the number of times the NetBIOS protocol attempts transmissions at the NetBIOS level before assuming that the receiver is not present. The transmission activities include name claims, session setups, and other similar actions. Mus t be a decimal number from 0 to 10. If omitted or 0, the default is 2. Refer to the NetBIOSTimeout parameter for more information. MaxDataRcv This parameter specifies the maximum size of user data in any frame that this node can receive on a session. The partner node makes sure that the size of the user data in frames transmitted over the session is no larger than the maximum receive size or th e size available in its transmit buffer, whichever is smaller. NetBIOS takes into account the maximum size that bridges in the path will forward, and never sends a frame too large for the bridge. The range of this parameter is 512-65535, and the default i s 17735. The 17735 is 17749 (maximum I-Field for 16-MB Token Ring) minus the 14 bytes for the NCB frame header (MIF header). Note: This value will never override the maximum value supported by the adapter. DlcRetries This parameter specifies the number of additional transmission attempts that the netBIOS protocol makes before assuming that the DLC layer of the receiving workstation is not responding. The value of this parameter can be low on a reliable network that do es not drop many packets. Increase this parameter value on a network that drops a large number of packets. Must be a decimal number from 0 to 255. If omitted or 0, the default is 8. XmitPriority This parameter specifies the maximum transmission priority for all transmissions. The higher the number, the higher the priority. Must be a decimal number from 0 to 6. If omitted or 0, the default is 0. This parameter is used to set the priority part of the DLC.OPEN.SAP OPTIONS_PRIORITY parameter table field. RND May be coded as a number from 0 to 255. If a nonzero value is coded, the Remote Name Directory (RND) function is implemented with the value indicating the number of remote names that can be saved by the local node. Note that 4 is the minimum number of nam e entries; if 1, 2, or 3 is entered, the value of 4 is used. If omitted or 0, the RND function is not implemented. When RND is implemented (after the local station has located a remote name), the remote node address is saved and subsequent CALLS, STATUS Q UERIES, and SEND DATAGRAMS to that name will be to a specific node rather than a broadcast to all nodes. The default is 0. RDC This function works only when Remote Name Directory (RND) is implemented. Enter this keyword with a value of YES to have SEND DATAGRAMS use RND to send to remote nodes. If a bridge in the transmission path drops out, datagrams give no indication that the path is no longer valid. If you find that the remote node is not receiving datagrams, you can update the RND by having the application program issues an NCB.FIND.NAME command with a receive buffer length of zero. The default value is NO. If this parameter value is omitted or coded as NO, SEND DATAGRAMS does not use the RND function. Sample NET.CFG file entry: PROTOCOL NNETBIOS T1=4 // retransmission timer RND=YES // remote name directory Timer Tick Values IEEE 802.2 timer tick parameters are found in the NET.CFG file. Information on how to change the values is provided for users who want to customize their IEEE 802.2 timing parameters. Most users will not want to make any changes to this timing information . The IEEE 802.2 protocol implementation uses three timers: T1Response timer TIInactivity timer T2Receiver Acknowledgment timer The rate at which each of these timers is stepped and the value at which they time out are selectable by parameters. The rate of stepping is referred to as the TICK and can be specified in the NET.CFG file as shown at the end of this section. Each timer requires a short timer tick (TICK_ONE) and a long timer tick (TICK_TWO). The period between timer ticks is some number of 55-millisecond intervals. The timer value, or count at which it expires, can be selected with parameters in the NNETBIOS section of NET.CFG. A timer value is selected by using a number between 1 and 10. Each timer is divided into two groups of possible values: ƒ If the number selected is between 1 and 5, the short timer tick (TICK_ONE) is used and is referred to as group 1. The timer value is equal to the number selected multiplied by the short timer tick value (number_selected x short_tick_value). ƒ If the number selected is between 6 and 10, the long timer tick (TICK_TWO) is used and is referred to as group 2. The timer value is equal to the number selected minus 5 multiplied by the long timer tick value ((number_selected- 5) x long_tick_value) Therefore, there are three timers, with two rates selectable for each, which provide a total of six parameters to be selected. The time of expiration is not exact but falls into a range starting with the calculated time. For example, if the following tick values are chosen for a given timer: Group-1 tick: 200 ms Group-2 tick: 1 second then the following timer values would be available: Group 1 Value (in MS) Group 2 Value (in seconds) actual actual range range 1 100 200-400 6 1 1-2 2 400 400-600 7 2 2-3 3 600 600-800 8 3 3-4 4 800 800-1000 9 4 4-5 5 1000 1000-1200 10 5 5-6 Following are some basic guidelines to consider when selecting timer values. In most cases, the default values provide efficient operation. Response Timer (T1) The Response timer (T1) is maintained by the sending station whenever an I-format LPDU or a command LPDU with the poll bit set to 1 is sent. If this timer expires before a response is received, the sending station solicits remote link station status by se nding a supervisory command LPDU with the poll bit set to 1. The T1 timer value should, therefore, be greater than the total delay time that the frame might encounter within the sending node, the network, and the receiving node. Normal settings for the T1 parameter should be in the range of 1 to 2 seconds. For instance, a setting above 2 seconds can result in noticeable delays to those responses that must be retransmitted (typically less than 3 percent of the total frames). Inactivity Timer (TI) The Inactivity timer (TI) runs whenever the Response timer (T1) is not running. If this timer expires, the link might have been lost. The Inactivity timer (TI) value should be 5 to 10 times greater than the T1 value, and it is recommended that the minimum be 25 seconds. The default is 25 seconds. Receiver Acknowledgment Timer (T2) A link station starts T2 when an I-format LPDU is received into workstation memory. T2 is stopped when an acknowledgment is sent either with an outgoing frame or when the number of I-format LPDUs received before the sending acknowledgment value is reached . If T2 expires, the link station must send an acknowledgment as soon as possible. The value of T2 must be less than that of T1 to ensure that the remote link station receives the delayed acknowledgment before T1 expires. Typical values for T2 are 80 to 2 56 ms. This is a sample NET.CFG file entry: PROTOCOL NLLC8022 NET BIND TOKEN-RING TOKEN 1 T1_TICK1 4 // Response timer - short tick (group one) T1_TICK2 20 // Response timer - long tick (group two) T1_VALUE 5 // Response timer - value T2_TICK1 1 // Receiver acknowledgment - short tick (group one) T2_TICK2 7 // Response acknowledgment - long tick (group two) T2_VALUE 2 // Receiver acknowledgment - value TI_TICK1 20 // Inactivity timer - short tick (group one) TI_TICK2 90 // Inactivity timer - long tick (group two) TI_VALUE 10 // Inactivity timer - value The values in this sample file are the defaults used by the code, and result in timer values of 1.1 seconds for T1, 110 milliseconds for T2, and 25 seconds for Ti. Differences between IBM LAN Client and LAN Support Program IBM LAN Client is intended to replace LAN Support Program with minimum disruption to existing installations. However, the two environments are not identical, and it is possible that in some situations the differences may be noticeable, or may require you to do something a little differently. Differences you might need to know about are listed in this section. Extra SAPs and extra stations These are parameters that were often needed for LAN Support Program that are no longer needed for IBM LAN Client. IBM LAN Client will continue to allocate memory for additional SAPs and stations as needed, until your machine runs out of memory, instead of allocating a fixed block of memory when it first starts executing. Specifying a locally administered address If you want to specify a locally administered address (LAA), you may still do so. However, you no longer provide the address as an IEEE 802.2 parameter. You now code the LAA on the adapter device driver load line in STARTNET.BAT (if you did not request th e LAA at installation time). The load line in STARTNET.BAT would be in the following format: LOAD TOKEN FRAME=TOKEN-RING NODE=400012345678 Route discovery across bridges and routers When you use source-route bridging in a Token-Ring environment the client workstation will send discovery frames to locate the server. There are two kinds of discovery frames: All Routes Explorer (ARE), and Spanning Tree Explorer (STE). Both frame types a re forwarded by bridges, but ARE frames are forwarded by all bridges to all rings, and STE frames are forwarded only by bridge ports that have been configured to be part of the Spanning Tree. The Spanning Tree is set up such that there is one and only one path between all stations on the network. LAN Support Program uses ARE frames for discovery, and IBM LAN Client uses STE frames. If your bridges or routers are not configured for Spanning Tree support, it is possible to replace LAN Support Program with I BM LAN Client and have the discovery process fail. This would mean that the client is unable to locate the server. You need to turn on Spanning Tree support for the affected ports on your bridges or routers. Running IBM LAN Manager IBM LAN Station Manager needs to be able to read and write IEEE 802.5 MAC frames. This capability is not provided by IBM LAN Client, and therefore IBM LAN Station Manager cannot be run with IBM LAN Client. List of Abbreviations API application program interface AREAll Routes Explorer BBSBulletin Board System DLCdata link control DOSdisk operating system DLSDOS LAN Services DLRDOS LAN Requester GUIgraphical user interface IEEEInstitute of Electrical and Electronics Engineers IPXInternetwork Packet Exchange ISAIndustry Standard Architecture LAAlocally administered address LANlocal area network LLClogical link control MACmedia access control MCMicrochannel NetBIOSNetwork Basic I/O System NLMNetWare Loadable Module NIOSNetWare I/O Subsystem ODIopen data-link interface PCIPeripheral Component Interconnect SNAPSubnetwork Access Protocol SPXsequenced packet Exchange STESpanning Tree Explorer TCP/IPTransmission Control Protocol/Internet Protocol Trademarks The following terms are trademarks of IBM Corporation in the United States or other countries or both. IBM AS/400 LANStreamerAnyNet Microchannel OS/2 Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation Other company, product, and service names, which may be denoted by a double asterisk (), may be trademarks or service marks of others.