Installation Guide for Clients Microsoft Network Client ® Version 2.
Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. ©1992-1993 Microsoft Corporation. All rights reserved.
iii Contents Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Contents Part 2 Installing LAN Manager Workstation Software Chapter 3 Installing LAN Manager on MS-DOS Workstations . . . . . . . . . 37 Installing LAN Manager Software on an MS-DOS Workstation . . . . . . 38 After Installing an MS-DOS Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Setting Up the Path on an MS-DOS Workstation. . . . . . . . . . . . . . . . . 40 Installing a Mouse Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents v Detaching, Attaching, or Removing LAN Manager. . . . . . . . . . . . . . . . . . Detaching LAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attaching LAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing LAN Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 96 97 98 Part 4 Network Device Drivers Chapter 8 About Network Device Drivers . . . . . . . . . . . . . . . . . .
vi Contents 3Com EtherLink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Com EtherLink II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Com EtherLink III Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Com EtherLink 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Com EtherLink Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Intel TokenExpress Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Madge Networks Smart 16/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . National Semiconductor EtherNODE . . . . . . . . . . . . . . . . . . . . . . . . . . National Semiconductor Sonic EISA (DP83932EB). . . . . . . . . . . . . NCR StarCard (8 bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NCR Token-Ring 4 MBPS ISA . . . . . . . . . . . . . .
viii Contents Ungermann-Bass UBNEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ungermann-Bass UBNEPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Western Digital EtherCard Plus and EtherCard Plus/A. . . . . . . . . . . Western Digital TokenCard, TokenCard WS, and TokenCard PLUS16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Zenith Data Systems Z.Note 325L Notebook PC . . . . . . . . . . . . . . . .
Contents ix LANMAN OS/2 Workstation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . The LANMAN\DRIVERS Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . The LANMAN\LOGS Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The LANMAN\NETLIB Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . The LANMAN\NETPROG Directory . . . . . . . . . . . . . . . . . . . . . . . . . . The LANMAN\SERVICES Directory. . . . . . . . . . . . . . . . . . . . . . .
x Contents Appendix C TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before Installing TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Computers on the Network . . . . . . . . . . . . . . . . . . . . . . . . . Matching LAN Manager Server Names to IP Addresses . . . . . . . . . Advanced Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tuning Microsoft TCP/IP . . . .
1 Before You Begin The Installation Guide for Clients is written for administrators of Microsoft® Windows NT™ networks that will include LAN Manager workstations. It covers the installation of MS-DOS® Basic and Enhanced workstations, including Enhanced workstations running the Microsoft Windows™ operating system. It also covers the installation of OS/2® workstations. This manual helps you plan the installation of your LAN Manager workstations, and shows you how to install and configure the software.
2 Installation Guide for Clients How to Use This Manual Turn to the part of this manual that contains the information you need: Part 1, “Overview, Preparation, and Planning” This part describes the preparations you must make to install and configure LAN Manager on MS-DOS and OS/2 computers. Part 2, “Installing LAN Manager Workstation Software ” This part tells you how to install LAN Manager workstation software on MS-DOS and OS/2 computers.
Before You Begin 3 Documentation Conventions This manual uses several type styles and special characters: Convention Use bold Represents commands, command options, and file entries. Type bold words exactly as they appear (for example, net use). Introduces new terms and represents variables. For example, the variable computername indicates that you type the name of a workstation or a server. Represents examples, screen displays, and error messages. Represents filenames and paths.
4 Installation Guide for Clients Finding Further Information This manual is written for network administrators. In addition to reading this manual, be sure to read the README.TXT or README.DOC files included with LAN Manager. These files are located in the LAN Manager root directory. These online files contain additional important information about LAN Manager, and they include information that was not available when the manuals were printed.
P A R T 1 Overview, Preparation, and Planning Chapters 1 Introduction ......................................................................................7 2 Planning for Installation and Configuration......................................
7 C H A P T E R 1 Introduction The LAN Manager Setup program is used to install and configure LAN Manager on OS/2 and MS-DOS computers. • When you install LAN Manager, the Setup program leads you, step- by-step, through installation using a series of dialog boxes. Your responses to the dialog box questions determine the type of workstation and the exact LAN Manager configuration that will be installed.
8 Installation Guide for Clients Using the Keyboard Use the following keys in both the Setup program dialog boxes and in the Setup screen: Key Function ALT Selects the menu bar in the Setup screen. Then press TAB, SHIFT+TAB, LEFT ARROW, or RIGHT ARROW to move to the menu you want. Denoted by an underlined or highlighted letter in a menu, command, or command button. Pressing ALT and the Access key chooses that menu or command button. When a menu’s commands are displayed, ALT is not required.
Chapter 1 Introduction 9 Online Help The LAN Manager Setup program offers you two types of online help: help for dialog boxes and menu-based help. • Help for dialog boxes is available from most of the LAN Manager Setup dialog boxes that appear when you install or configure LAN Manager software. When you choose a dialog box’s Help button or press the F1 key, a help dialog box appears, providing information specific to that LAN Manager Setup dialog box.
10 Installation Guide for Clients System Requirements Before installing LAN Manager, check that your system meets the following requirements. The following tables list the processor type, memory, and operating system needss for LAN Manager workstations. The following table shows the processors required for different LAN Manager configurations. Processor Requirements LAN Manager configuration 8086/88 286 386 486 MS OS/2 1.x workstation IBM OS/2 2.
Chapter 1 Introduction 11 Before Installing Before you can install LAN Manager, the computer’s operating system must be installed. Before you begin to install LAN Manager, have these items at hand: • Manuals for the computer. • Manuals for the operating system. • If needed, a supplemental drivers disk that contains a network adapter driver or a protocol. Also, before you begin to install LAN Manager, determine the following: • The amount of random access memory (RAM) installed in the • • • • computer.
12 Installation Guide for Clients
13 C H A P T E R 2 Planning for Installation and Configuration This chapter helps you make the decisions necessary to install and configure LAN Manager workstations. (Workstations are also referred to as clients.
14 Installation Guide for Clients Figure 2.1 Planning for Enhanced MS-DOS Workstations Computer: Parameter 1. Computer Configuration Processor Memory Free hard disk space MS-DOS version Network adapter Network adapter settings Windows 3.0 (or later) installed? Windows directory Range Default Entry 8088, 8086 or greater 640K plus extended or expanded memory 4 MB minimum 3.
Chapter 2 Planning for Installation and Configuration 4. Workstation Settings Computername Username Domain name Other domains to monitor (up to 4 domains) Any unique computername Any valid username Any valid domain name Valid domain name or blank Messaging service? yes or no 5. Running with the Windows Operating System Run LAN Manager with the Windows Operating System? Location of WIN.INI file Display messages * Entry required Blank *______________ Blank DOMAIN 1. Blank 2. Blank 3. Blank 4.
16 Installation Guide for Clients Figure 2.2 Planning for Basic MS-DOS Workstations Computer: Parameter Range Default 1. Computer Configuration Processor Memory Free hard disk space MS-DOS version Network adapter Network adapter settings 8088, 8086, or greater — 640K minimum — 1 MB minimum — 3.3 or newer — — — — — Entry ______________ ______________ ______________ ______________ ______________ ______________ 2.
Chapter 2 Planning for Installation and Configuration 4. Workstation Settings Computername 5.
18 Installation Guide for Clients Figure 2.3 Planning for OS/2 Workstations Parameter Range Default Entry 1. Computer Configuration Processor Memory Free hard disk space Network adapter Network adapter settings OS/2 version 286 or greater 4.5 MB recommended 5 MB minimum — — 1.21, 1.3, or 2.
Chapter 2 Planning for Installation and Configuration 4. Workstation Settings Computername Other domains to monitor (up to 4 domains) Any unique computername Any valid username Any valid domain name Valid domain name or blank Autostart Messenger service? Autostart Netpopup service? yes or no yes or no Username Domain name 5. Service Parameters Messenger service: Message log filename Message buffer size * Entry required 19 Blank Blank DOMAIN *______________ *______________ *______________ 1.
20 Installation Guide for Clients Planning for LAN Manager Installations on MS-DOS Computers This section explains the information that was introduced earlier in this chapter, in “Configuration Planning Forms.” It provides information and concepts you should understand before you begin to install or configure LAN Manager workstation software on MS-DOS computers. It is a good idea to photocopy the configuration planning forms and fill them in while reading this section.
Chapter 2 Planning for Installation and Configuration 21 Network adapter To communicate over the network, a computer must have at least one network adapter installed. You must know the type of each adapter installed so that you can determine the appropriate network adapter driver and protocol, and you must know the settings used for each network adapter. (For more information about network adapters, settings, and network adapter drivers, see Part 4, “Network Device Drivers.
22 Installation Guide for Clients Network Adapter Drivers and Protocols When installing, you’ll need to provide information about the computer’s network adapter and network adapter drivers. LAN Manager uses network device drivers (software that coordinates between the computer’s software and hardware) to operate the network adapter(s) in the computer. Network adapter drivers control the physical function of the network adapters, and protocol drivers bind to the network adapter driver.
Chapter 2 Planning for Installation and Configuration 23 Some network adapter drivers are monolithic. A monolithic driver acts as both a network adapter driver and a protocol, and it does not require that another protocol be selected and bound to it. Only one monolithic driver, the loopback driver, is provided with LAN Manager. This driver lets a computer with no network adapter run LAN Manager for testing purposes. (For more information about the loopback driver, see Part 4, “Network Device Drivers.
24 Installation Guide for Clients Number of NetBIOS sessions The number of NetBIOS sessions. For MS-DOS workstations, the range is 1 through 22; the default is 6. An entry is required. The TCP/IP protocol can be bound to only one network adapter driver for each workstation. If the TCP/IP protocol is bound to more than one network adapter driver on a workstation, only the first binding is effective; all subsequent bindings of TCP/IP to network adapter drivers are ignored.
Chapter 2 Planning for Installation and Configuration 25 Domain name The name of the domain or workgroup to which a workstation belongs. It can have as many as 15 characters, and it can contain letters, numerals, and these characters: !#$%&()^_' {}~ An entry is required. The default is DOMAIN. An entry is required.
26 Installation Guide for Clients Using Stacker with LAN Manager If you are using Stacker®with LAN Manager, the lines in CONFIG.SYS that specify Stacker should come before the line that begins device= and contains \protman.dos. This allows for the possibility that the network drivers may be on either the stacked or unstacked portion of the hard drive. Drivers that are loaded before Stacker must exist on the unstacked portion of the hard drive.
Chapter 2 Planning for Installation and Configuration 27 Using LAN Manager with HIMEM.SYS requires: • MS-DOS version 3.3 or later • LAN Manager Enhanced or Basic workstation software • 64K or more of extended memory If this computer is currently running HIMEM.SYS, LAN Manager does not replace the existing HIMEM.SYS file. EMM386.EXE For emulating expanded memory, a section of extended memory configured for the Lotus/Intel/Microsoft (LIM) 4.0 expanded memory specification (EMS) on 386 and higher computers.
28 Installation Guide for Clients Using Third Party Memory Managers for Workstations Before running the optimization or configuration program of a third party memory manager, edit AUTOEXEC.BAT to comment out (add a REM statement at the beginning of) the net start workstation line and any lines loading protocols. Then edit CONFIG.SYS to comment out the line that specifies the path to PROTMAN.DOS. It will look something like this: device = c:\lanman.dos\drivers\protman\protman.
Chapter 2 Planning for Installation and Configuration 29 Planning for LAN Manager Installations on OS/2 Computers This section explains the information that was introduced earlier in this chapter, in “Configuration Planning Forms.” It provides information and concepts you should understand before you begin to install or configure LAN Manager workstation software on OS/2 computers. It is a good idea to photocopy the configuration planning forms and fill them in while reading this section.
30 Installation Guide for Clients Network adapter To communicate over the network, a computer must have at least one network adapter installed. You must know each adapter that is installed so that you can determine the appropriate network adapter driver and protocol, and you must know the settings that have been used for each network adapter. (For more information about network adapters, settings, and network adapter drivers, see Part 4, “Network Device Drivers.
Chapter 2 Planning for Installation and Configuration 31 Network adapter driver You must choose one or more network adapter drivers. The driver(s) must support the network adapter installed in the computer, and the settings used for that adapter. During installation, you can select No Driver as the network adapter driver. This allows you to complete an installation without specifying a network adapter driver or a protocol.
32 Installation Guide for Clients Subnet mask A series of bits used to identify the subnet number portion of an IP address. The Subnet mask has four fields separated by periods, in the form: w.x.y.z The range for each of the first three fields (w, x, and y) is 0 through 255. The range for the last field (z) is 1 through 254. The Subnet mask setting is required. Default gateway (router) The IP address of the default router used.
Chapter 2 Planning for Installation and Configuration 33 Username The name by which the network identifies the user of a computer and the name to which you assign permissions to use resources. The username can have as many as 20 characters, and it can contain letters, numerals, and these characters: !#$%&()^_' {}~ The username can be identical to the computername. An entry is required. Domain name The name of the domain or workgroup to which a workstation belongs.
34 Installation Guide for Clients Services Parameters When installing, you cannot change the services parameters of a workstation. After installation, you can change the services parameters using the Configuration menu’s Services command. (The procedure is described in Part 3, “Managing Your LAN Manager Software Configuration.”) For an OS/2 workstation, you can set only the Messenger service parameters. Messenger service parameters Lets the computer send and receive messages on the network.
P A R T 2 Installing LAN Manager Workstation Software Chapters 3 Installing LAN Manager on MS-DOS Workstations........................37 4 Installing LAN Manager on OS/2 Workstations...............................45 5 Setup Screen Basics ........................................................................
37 C H A P T E R 3 Installing LAN Manager on MS-DOS Workstations This chapter shows you how to install LAN Manager workstation software on MS-DOS computers. For planning assistance and for explanations of configuration choices you can make, see Chapter 2, “Planning for Installation and Configuration.” It is recommended that you complete the planning forms provided in Chapter 2 and keep them available while installing.
38 Installation Guide for Clients Installing LAN Manager Software on an MS-DOS Workstation You can install LAN Manager 2.2 from disk on an MS-DOS computer. The computer may use the Microsoft Windows operating system. Note If you are using Microsoft Windows, do not run LAN Manager Setup in the Windows “MS-DOS Prompt” window. Exit the Microsoft Windows operating system before running LAN Manager Setup. Û To install LAN Manager 2.2 from disk 1.
Chapter 3 Installing LAN Manager on MS-DOS Workstations 39 After Installing an MS-DOS Workstation After installing an MS-DOS workstation, you can do the following: • Review the hardware settings for the network adapter in the • • • • PROTOCOL.INI file. If these settings are incorrect or incomplete, the system will not operate correctly. You may need to adjust the CONFIG.SYS, LANMAN.INI, and PROTOCOL.INI files. For more information, see Part 4, “Network Device Drivers.” Review the AUTOEXEC.
40 Installation Guide for Clients Setting Up the Path on an MS-DOS Workstation When the Setup program installs a LAN Manager Enhanced or Basic workstation, it adds the directory you specified for the LAN Manager software to the computer’s search path. By default, the following directory is added to the path: For Enhanced workstations: c:\lanman.dos\netprog For Basic workstations c:\lanman.
Chapter 3 Installing LAN Manager on MS-DOS Workstations 41 Note that the mouse driver must have a .COM filename extension. Some mouse drivers (those with a .SYS filename extension) are installed by the CONFIG.SYS file, which is loaded before AUTOEXEC.BAT. If your computer installs the mouse driver with CONFIG.SYS, and if you have a mouse driver with a .COM filename extension available, edit the AUTOEXEC.BAT file as shown in the previous example, and then delete the command in the CONFIG.
42 Installation Guide for Clients For LAN Manager Enhanced, prtsc is stored in the LANMAN.DOS\NETPROG directory. You can type prtsc at the command line, or you can start it automatically with the Workstation service by including it in the wrkservices entry in the [workkstation] section and in the [services] section of the LANMAN.INI file.
Chapter 3 Installing LAN Manager on MS-DOS Workstations 43 Modifying the Microsoft Windows SETUP.INF File When installing an MS-DOS workstation, the Setup program checks to see if Microsoft Windows version 3.x is installed on the computer. If the Microsoft Windows operating system is installed, Setup looks for and modifies various files, including the Windows SETUP.INF file. If Microsoft Windows is installed locally (on the computer’s hard disk), the installation proceeds normally.
44 Installation Guide for Clients
45 C H A P T E R 4 Installing LAN Manager on OS/2 Workstations This chapter shows you how to install LAN Manager workstation software on OS/2 computers. For planning assistance and for explanations of configuration choices you can make, see Chapter 2, “Planning for Installation and Configuration.” It is recommended that you complete the planning forms provided in Chapter 2 and keep them available while installing an OS/2 workstation.
46 Installation Guide for Clients Installing an OS/2 Workstation Using the LAN Manager installation disk set, install LAN Manager onto a computer that already has OS/2 operating system software installed. For workstation operating system and hardware requirements, see Chapter 1, “Introduction.” Û To install LAN Manager workstation software on a computer that already has OS/2 installed 1. Start the computer and open an OS/2 window or full screen session. 2.
Chapter 4 Installing LAN Manager on OS/2 Workstations 47 After Installing an OS/2 Workstation After installing an OS/2 workstation, you can do the following: • Review the hardware settings for the network adapter. If these settings are incorrect or incomplete, the system will not operate correctly. If you use default settings, the system should operate correctly. If you have modified the hardware settings, or if you have software that does so, check and adjust the CONFIG.SYS, LANMAN.INI, and PROTOCOL.
48 Installation Guide for Clients
49 C H A P T E R 5 Setup Screen Basics Whenever you need to review or change the configuration of an existing LAN Manager workstation, you use the LAN Manager Setup program’s menu interface, called the LAN Manager Setup screen. This chapter describes how to use the LAN Manager Setup screen. Starting the Setup Screen If this is an MS-DOS computer, start from the MS-DOS command line.
50 Installation Guide for Clients 2. From the LAN Manager directory, start the Setup screen. Type setup and press ENTER. If the computer has a monochrome or plasma screen, type setup /mono and press ENTER. The LAN Manager Setup screen is displayed. Using Setup Screen Menus Follow these steps when using Setup screen commands. Û To issue commands from the Setup screen 1. Select a menu in one of these ways: • Click a menu name. Note The mouse cannot be used with IBM OS/2 2.0.
Chapter 5 Setup Screen Basics 51 • Press the key that corresponds to the letter highlighted or underlined in the command name. • If a function key (F key) is shown next to the command name, press that function key. • Press the UP or DOWN ARROW keys to select a command, and then press ENTER. A LAN Manager dialog box appears. The following illustration shows the LAN Manager Setup screen menus and commands for MS-DOS computers.
52 Installation Guide for Clients Saving Configuration Changes After you complete a particular configuration task, choose the OK button to exit the final configuration dialog box and return to the Setup screen. If you changed the configuration, Setup displays the Configuration Complete dialog box, as shown in the following illustration.
Chapter 5 Setup Screen Basics 53 Exiting the Setup Screen The LAN Manager menu’s Exit Setup command returns you to the MS-DOS or OS/2 command line. Û To exit the LAN Manager Setup screen 1. Complete and close any open dialog boxes. 2. From the LAN Manager menu choose Exit Setup, or press F3. If you have changed the LAN Manager configuration during this session in the Setup screen, the LAN Manager Configuration Complete dialog box appears, instructing you to reboot the computer after exiting Setup. 3.
54 Installation Guide for Clients
P A R T 3 Managing Your LAN Manager Configuration Chapters 6 Managing an MS-DOS Workstation................................................57 7 Managing an OS/2 Workstation.......................................................
57 C H A P T E R 6 Managing an MS-DOS Workstation This chapter describes the LAN Manager Setup screen for MS-DOS computers. Using the Setup screen, you can review and change the configuration for LAN Manager Enhanced and LAN Manager Basic workstations. The LAN Manager Setup screen for MS-DOS computers has four menus: LAN Manager, Configuration, Connectivity, and Help, as shown in the following illustration.
58 Installation Guide for Clients Managing the Configuration Settings Use the Setup screen’s Configuration menu to manage LAN Manager’s network device driver configurations and workstation settings. Managing Network Device Drivers Using the Configuration menu’s Network Drivers command, you can: • Review the workstation’s network device driver configurations. • Change the protocol(s) bound to a network adapter driver in a network device driver configuration. • Add a network device driver configuration.
Chapter 6 Managing an MS-DOS Workstation 59 2. Review the network device driver configurations. If necessary, you can scroll through the list of configurations by clicking the scroll bar or by pressing the PAGE DOWN and PAGE UP keys. A configuration consists of a network adapter driver and one or more protocols bound to it. If the driver is monolithic, a configuration consists of only the network adapter driver.
60 Installation Guide for Clients Review or edit the TCP/IP Settings dialog box as necessary, and then choose the OK button. If you made no changes, the Setup screen returns and you are finished. If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 6. If you made no changes in any of the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears.
Chapter 6 Managing an MS-DOS Workstation Û 61 To change the protocol(s) bound to a network adapter driver 1. From the Configuration menu, choose the Network Drivers button. The Workstation Configuration dialog box appears, showing you this computer’s network device driver configurations: 2. Select the network device driver configuration you want to change. A configuration consists of a network adapter driver and one or more protocols bound to it.
62 Installation Guide for Clients 3. Choose the Add/Remove Protocols button. The Network Protocols dialog box appears: The Network Protocols dialog box lists the protocols available on this computer. If necessary, you can scroll through the list by clicking the scroll bar or by pressing the PAGE DOWN and PAGE UP keys. • If the list contains all needed protocols, continue on to step 4.
Chapter 6 Managing an MS-DOS Workstation 63 5. When you finish adding or removing protocols, choose the OK button. The selected protocols are bound to the network adapter driver in this network device driver configuration. The Workstation Configuration dialog box returns, showing the modified network device driver configuration. 6. Optionally, from the Workstation Configuration dialog box you can: • Change the protocol(s) bound to a network adapter driver in another network device driver configuration.
64 Installation Guide for Clients 9. If you made no changes, the Setup screen returns and you are finished. If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 10. If you made no changes in any of the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears. • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns.
Chapter 6 Managing an MS-DOS Workstation 65 2. Choose the Add New Config button. The Network Adapter Drivers dialog box appears, displaying a scrollable list of the available network adapter drivers. If necessary, you can scroll through the list by clicking the scroll bar or by pressing the PAGE DOWN and PAGE UP keys. 3. Select a network adapter driver.
66 Installation Guide for Clients 4. The Network Protocols dialog box shows you the protocols available on this computer. If necessary, you can scroll through the list of protocols by clicking the scroll bar or by pressing the PAGE DOWN and PAGE UP keys. • If the list contains all needed protocols, proceed to step 5.
Chapter 6 Managing an MS-DOS Workstation 67 8. When you have completed your review (and your optional changes), exit the Workstation Configuration dialog box. • To exit this dialog box and discard any changes you made, choose the Cancel button. The Setup screen returns. You are finished, and steps 9 and 10 do not apply. • To save any changes you made, choose the OK button.
68 Installation Guide for Clients 10. If you made no changes in the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears. • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns. • To return to the Workstation Configuration dialog box, choose the Review button. There you can review, change, accept, or cancel the changes you have made (beginning again at step 2).
Chapter 6 Managing an MS-DOS Workstation 69 3. Choose the Remove Config button. The network device driver configuration is removed. 4. Optionally, from the Workstation Configuration dialog box you can: • Change the protocol(s) bound to a network adapter driver in a network device driver configuration (as described earlier in this section) • Add a network device driver configuration (as described earlier in this section) • Return to step 2 and remove another network device driver configuration 5.
70 Installation Guide for Clients Review or edit the TCP/IP Settings dialog box as necessary, and then choose the OK button. If you made no changes, the Setup screen returns and you are finished. If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 7. If you made no changes in the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears. • To save the changes you made, choose the Save button.
Chapter 6 Managing an MS-DOS Workstation 71 Managing Workstation Settings Using the Configuration menu’s Workstation Settings command, you can change the computername, username, domain name, domains to monitor, and services to autostart for a LAN Manager Enhanced workstation. For a LAN Manager Basic workstation, you can change only the computername.
72 Installation Guide for Clients 3. When you have completed your review or your changes, exit the Workstation Settings dialog box. • To exit this dialog box and discard any changes you made, choose the Cancel button. The Setup screen returns. You have finished this process. (None of the following steps apply.) • To save your changes, choose the OK button. The dialog box that appears next depends on the hardware and software configuration of your computer. Proceed to step 4 for instruction. 4.
Chapter 6 Managing an MS-DOS Workstation 73 • The Support for the Windows Environment dialog box appears if the Microsoft Windows operating system is installed on this computer, and if LAN Manager Enhanced (but not LAN Manager Basic) is installed. This dialog box asks you to decide whether LAN Manager will run with the Windows operating system.
74 Installation Guide for Clients • The Messaging Popups dialog box appears if the Microsoft Windows operating system is installed on this computer, and Yes was selected in the Workstation Settings dialog box for running the Messaging service and in the Support for the Windows Environment dialog box, indicating you want to run LAN Manager with the Windows operating system.
Chapter 6 Managing an MS-DOS Workstation 75 5. If you made any changes to any of the dialog boxes, the Configuration Complete dialog box appears last, asking you to save or review the changes you made. • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns. • To return to the Workstation Settings dialog box, choose the Review button. There you can review, change, accept, or cancel the changes you made (beginning at step 2).
76 Installation Guide for Clients Û To manage the NetWare service 1. From the Connectivity menu, choose NetWare Service. The NetWare service Setup screen appears. 2. Review and change the settings as necessary. For instructions, see the NetWare Connectivity Guide or use online help. When you complete your review and exit the NetWare service Setup screen, the LAN Manager Setup screen reappears. Removing LAN Manager You use the LAN Manager menu’s Remove command to remove LAN Manager from the computer.
Chapter 6 Managing an MS-DOS Workstation Û 77 To remove LAN Manager from an MS-DOS workstation 1. If you are running the Microsoft Windows operating system, exit Windows. 2. For LAN Manager Enhanced only, stop the Workstation service from the MS-DOS command line by typing net stop workstation and pressing ENTER. 3. Start the Setup screen from the LAN Manager directory by typing setup and pressing ENTER. 4. From the LAN Manager menu, choose Remove.
78 Installation Guide for Clients
79 C H A P T E R 7 Managing an OS/2 Workstation This chapter describes the LAN Manager Setup screen for OS/2 computers. Using the Setup screen, you can review and change the LAN Manager configuration for OS/2 workstations. The LAN Manager Setup screen for OS/2 computers has four menus: LAN Manager, Configuration, Connectivity, and Help, as shown in the following illustration.
80 Installation Guide for Clients Managing the Configuration Settings Use the Setup screen’s Configuration menu to manage LAN Manager’s network device driver configurations, workstation settings, and services parameters. Managing Network Device Drivers Using the Configuration menu’s Network Drivers command, you can: • Review the network device driver configurations. • Change the protocol(s) bound to a network adapter driver in a network device driver configuration.
Chapter 7 Managing an OS/2 Workstation 81 3. Optionally you can: • Change the protocol(s) bound to a network adapter driver in a network device driver configuration. • Add a network device driver configuration. • Remove a network device driver configuration. Instructions for these optional tasks are provided following this procedure. 4. When you have completed your review (and any changes you made in step 3), exit the Workstation Configuration dialog box.
82 Installation Guide for Clients If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 6. If you made no changes in any of the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears. • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns. • To return to the Workstation Configuration dialog box, choose the Review button.
Chapter 7 Managing an OS/2 Workstation 83 2.Select the network device driver configuration you want to change. A configuration consists of a network adapter driver and one or more protocols bound to it. Select a configuration by clicking the configuration, or by pressing the UP and DOWN ARROW keys. If necessary, you can scroll through the list of configurations by clicking the scroll bar or by pressing the PAGE DOWN and PAGE UP keys. The selection is highlighted.
84 Installation Guide for Clients 4. In the Network Protocols dialog box, add or remove protocols from this network device driver configuration. A protocol is included in this network device driver configuration when the check box at the left of the protocol is selected. A protocol is selected ([X]) or cleared ([ ]) by clicking the check box, or by pressing the UP or DOWN ARROW key until the protocol is highlighted, and then pressing the SPACEBAR. 5.
Chapter 7 Managing an OS/2 Workstation 85 8. If the TCP/IP protocol is included in one of the configurations, and if you chose the OK button in the Workstation Configuration dialog box, the TCP/IP Settings dialog box appears: Review or edit the TCP/IP Settings dialog box as necessary, and then choose the OK button. If you made no changes, the Setup screen returns and you are finished. If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 9.
86 Installation Guide for Clients Û To add a network device driver configuration 1. From the Configuration menu, choose Network Drivers. The Workstation Configuration dialog box appears, showing you this computer’s network device driver configurations. 2. Choose the Add New Config button. The Network Adapter Drivers dialog box appears, displaying a scrollable list of the available network adapter drivers.
Chapter 7 Managing an OS/2 Workstation 87 3. Select a network adapter driver. • If the list contains the needed network adapter driver, select the driver by clicking it or by pressing the UP or DOWN ARROW key until the driver is highlighted. After the driver is selected, choose the OK button.
88 Installation Guide for Clients • If the list contains all needed protocols, proceed to step 5. • If the list does not contain a needed protocol, and if you have a 5. 6. 7. 8. supplemental drivers disk containing that protocol, you can copy the protocol to the computer by choosing the Other Protocol button and following the instructions that appear on your screen.
Chapter 7 Managing an OS/2 Workstation 89 9. If the TCP/IP protocol is included in one of the configurations, and if you chose the OK button in the Workstation Configuration dialog box, the TCP/IP Settings dialog box appears: Review or edit the TCP/IP Settings dialog box as necessary, and then choose the OK button. If you made no changes, the Setup screen returns and you are finished. If you changed the TCP/IP settings, the Configuration Complete dialog box appears: 10.
90 Installation Guide for Clients Û To remove a network device driver configuration 1. From the Configuration menu, choose Network Drivers. The Workstation Configuration dialog box appears, showing you this computer’s network device driver configurations: 2. Select the network device driver configuration you want to remove. A configuration consists of a network adapter driver and one or more protocols bound to it. Select a configuration by clicking it, or by pressing the UP and DOWN ARROW keys.
Chapter 7 Managing an OS/2 Workstation 91 5. When you have completed your review (and your optional changes), exit the Workstation Configuration dialog box. • To exit this dialog box and discard any changes you made, choose the Cancel button. The Setup screen returns. You are finished, and steps 6 and 7 do not apply. • To save any changes you made, choose the OK button.
92 Installation Guide for Clients 7. If you made no changes in the preceding steps, the Setup screen returns and you are finished. If you made any changes, the Configuration Complete dialog box appears. • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns. • To return to the Workstation Configuration dialog box, choose the Review button. There you can review, change, accept, or cancel the changes you made (beginning again at step 2).
Chapter 7 Managing an OS/2 Workstation 93 2. Review or edit the Workstation Settings dialog box. For detailed information about the settings in this dialog box, press F1 or choose the Help button. 3. When you have completed your review and changes, exit the Workstation Settings dialog box. • To exit this dialog box and discard any changes you made, choose the Cancel button. The Setup screen returns. You are finished, and step 4 does not apply. • To save any changes you made, choose the OK button.
94 Installation Guide for Clients Managing Services Parameters Services parameters are set to their default values during installation. They can be modified only after installation, using the Configuration menu’s Services command. For an OS/2 workstation, you can change only the Messenger service parameters. Û To review or change the services parameters 1. From the Configuration menu, choose Services. The Services Parameters dialog box appears: 2.
Chapter 7 Managing an OS/2 Workstation 95 6. When you have finished changing the services parameters, choose the OK button from the Services Parameters dialog box. If you made any changes, the Configuration Complete dialog box appears. If you did not make changes, the Setup screen returns, you are finished, and step 7 does not apply. 7. If the Configuration Complete dialog box appears: • To save the changes you made, choose the Save button. The changes are saved and the Setup screen returns.
96 Installation Guide for Clients 2. As instructed by the dialog box, insert the connectivity service Setup disk in the disk drive or type a path to the connectivity service’s Setup software, and then choose the OK button. 3. Follow the instructions that appear on your screen. For more information, see the connectivity service’s manual(s) or use the connectivity service’s online help.
Chapter 7 Managing an OS/2 Workstation Û 97 To detach LAN Manager from an OS/2 workstation 1. From the OS/2 window or full screen session, stop the Workstation service by typing net stop workstation and pressing ENTER. Follow the instructions that appear on your screen. 2. Change to the LAN Manager drive and directory and start the LAN Manager Setup screen. Usually you would type: c: cd \lanman setup 3. From the LAN Manager menu, choose Detach. 4.
98 Installation Guide for Clients Û To attach LAN Manager to an OS/2 workstation 1. From the LAN Manager menu, choose Attach. A dialog box appears, asking you to confirm the attach request. 2. Choose the Yes button. The Setup program attaches LAN Manager. 3. Wait for the attach process to proceed. When instructed by the Attach Ready to Complete dialog box, shut down MS OS/2 from Presentation Manager, and then reboot the computer. 4. Wait for the attach process to continue.
Chapter 7 Managing an OS/2 Workstation 99 LAN Manager can be in the attached or detached condition at the time you issue the Remove command. If LAN Manager is detached, the Remove command deletes the LAN Manager files from the hard disk. If LAN Manager is attached, the Remove command does the following: • Removes and saves LAN Manager information from the CONFIG.SYS and STARTUP.CMD files. • Removes and saves the extended DISK01.SYS or DISK02.SYS file (if installed) and restores the original file.
100 Installation Guide for Clients
P A R T 4 Network Device Drivers Chapters 8 About Network Device Drivers ...................................................103 9 Network Device Driver Options ..................................................131 10 Creating Supplemental Driver Disks ............................................
103 C H A P T E R 8 About Network Device Drivers This chapter contains information about installing and using network device drivers, the software that enables LAN Manager to work with network adapters on LAN Manager workstations. It also explains how to change the configuration of the options that control network device drivers.
104 Installation Guide for Clients Using Network Device Drivers When you install LAN Manager using the Setup program or when you add a new network adapter to your computer, you must specify which network device drivers your system will use.
Chapter 8 About Network Device Drivers 105 LAN Manager creates network access using three types of network device drivers. These three types are as follows: • Protocol (or transport) drivers transfer LAN Manager events between computers on the local-area network, working as intermediaries between LAN Manager and the media-access control driver(s). Protocol drivers are hardware independent; they communicate with LAN Manager through a NetBIOS interface.
106 Installation Guide for Clients Each network device driver has a unique driver name that identifies the driver in the LANMAN.INI and PROTOCOL.INI files. The driver name typically combines the base portion of the filename and a dollar sign (drivername$). For example, the driver name for the IBMTOK.OS2 driver is IBMTOK$.
Chapter 8 About Network Device Drivers 107 Protocol Manager LAN Manager supports the use of multiple protocols. The most practical limit to the number of protocols a computer can support is its memory capacity. Your computer could be connected to as many as 12 networks, of which LAN Manager can manage one, some, or all. LAN Manager’s Protocol Manager module coordinates communication among drivers and adapters. The Protocol Manager driver (PROTMAN.OS2 or PROTMAN.
108 Installation Guide for Clients NetBIOS 3.0 and the CONFIG.SYS File The NETBIOS.OS2 driver must be loaded after the LAN Manager redirector driver (NETWKSTA.SYS) is loaded. Make sure the following line is entered after the LANMAN 2.2 === DO NOT MODIFY BETWEEN THESE LINES section: device = lanroot\netprog\netbios.os2 NetBIOS 3.0 and the LANMAN.INI File In the [networks] section of LANMAN.INI, there is a netn line that accepts parameters for installing NetBIOS.
Chapter 8 About Network Device Drivers 109 To support NetBIOS 3.0, edit your LANMAN.INI file accordingly. Find the netn line that corresponds to the network you want NetBIOS 3.0 support for, and add these parameters to that line. For more information about the LANMAN.INI and PROTOCOL.INI files, see Appendix B, “The LANMAN.INI File,” and Chapter 9, “Network Device Driver Options.” Note The values that the protocol driver uses are not listed in PROTOCOL.INI.
110 Installation Guide for Clients The CONFIG.SYS File The CONFIG.SYS file contains device lines that list the network device drivers MS-DOS or OS/2 loads when you start your computer. All LAN Manager device drivers must be listed in the CONFIG.SYS file. Note This file may have a different name on your computer—for example, CONFIG.OS2 for dual-boot systems. When you use the Setup program to install LAN Manager, you are asked to identify the network adapter(s) in your computer.
Chapter 8 About Network Device Drivers 111 2. All network device drivers installed on your computer. With an MSDOS computer using more than one network adapter, list network device drivers in the order of their Local Area Network Adapter (LANA) numbers. On OS/2 workstations, LANA numbers are assigned according to the order of entries in the [networks] section of the LANMAN.INI file.
112 Installation Guide for Clients The PROTOCOL.INI File The PROTOCOL.INI file describes all protocol and media-access control drivers and defines how to bind them together. PROTOCOL.INI also contains media-access control information such as the input/output (I/O) address, direct memory access (DMA), and interrupts. You can edit PROTOCOL.INI to specify the drivers that work together, and you can fine-tune the parameters they use when exchanging data. The PROTOCOL.
Chapter 8 About Network Device Drivers 113 The name = value entries vary according to the individual driver. (Spaces around the equal sign are optional.) See Chapter 9, “Network Device Driver Options,” for the entries possible for each driver. Two entries are of particular note here: drivername Every section must contain the drivername entry, which specifies the name of the driver defined in the section.
114 Installation Guide for Clients LAN Manager for OS/2 Under OS/2, the [networks] section of LANMAN.INI specifies the protocol or monolithic network device drivers LAN Manager can use, and the order of these lines determines the LANA number of the protocol/adapter pair specifed in the netx line. It does not refer to media-access control drivers. Each [networks] entry has the following form: netn = drivername,m,[options] where n Is a unique number used to identify the driver in later LANMAN.INI entries.
Chapter 8 About Network Device Drivers 115 The Driver-Information Files The Setup program uses driver-information files associated with each driver to install and coordinate multiple network device drivers. The three kinds of driver-information files are discussed briefly in the following list and then in more detail in the sections that follow. NIF Network-information (.NIF) files, text files that provide information about network adapter drivers.
116 Installation Guide for Clients path The path for the directory in which the driver and its associated PROTOCOL.INI file are located. The Setup program appends path to the end of lanroot\DRIVERS, where lanroot is the LAN Manager root directory (usually C:\LANMAN.DOS for MS-DOS workstations, or C:\LANMAN for OS/2 workstations). When the Setup program installs the driver on a hard drive, this directory is created if it does not exist already.
Chapter 8 About Network Device Drivers 117 ancillary An optional entry listing the filename of any additional file required by the driver. If more than one file is required, list each file on a separate line beginning with the word ancillary. xports An optional entry that applies only to NDIS drivers. This entry specifies the protocol for which the driver has been tested and certified. The default is netbeui.
118 Installation Guide for Clients type The type of protocol driver, as defined in the following list: ndis_xport For NDIS-conformant protocol drivers that act as transports (such as TCP/IP). ndis_tsr For terminate-and-stay-resident (TSR) programs that function as protocol drivers. ndis_tcpip For the TCP/IP protocol. ndis_nonb Allows the Basic redirector to have two or more protocols attached to it, the secondary ones being non-NetBIOS protocols (such as IPX or XNSTP).
Chapter 8 About Network Device Drivers 119 The PROTOCOL.INI File Each protocol driver and each network adapter driver must have a PROTOCOL.INI file containing the entries for that card. These entries become part of the master PROTOCOL.INI file that is stored in the LAN Manager root directory. The following example illustrates the general format in all PROTOCOL.INI files for network adapter drivers.
120 Installation Guide for Clients Configuration Examples In the examples in this section, the path of the LAN Manager root directory is C:\LANMAN.DOS for MS-DOS and C:\LANMAN for OS/2. It may be different on your machine. The file entries are not exhaustive. See Chapter 9, “Network Device Driver Options,” for PROTOCOL.INI options. See Appendix B, “The LANMAN.INI File,” for LANMAN.INI options.
Chapter 8 About Network Device Drivers 121 [NETBEUI_XIF] Drivername = netbeui$ SESSIONS = 6 NCBS = 12 BINDINGS = "ELNKMC_NIF" LANABASE = 0 [ELNKMC_NIF] ; ; 3C523 3Com EtherLink /MC adapter ; DRIVERNAME = ELNKMC$ ; 2nd driver name = ELNKMC2$ ; MAXTRANSMITS = 40 ; number of transmit queue elements (optional, default = 12) ; Min = 8, Max = 50 ; Use the default for DOS and normal OS/2 clients ; Set MAXTRANSMITS = 40 for OS/2 servers ; NETADDRESS = "02608C123456" ; network address (optional, default = network
122 Installation Guide for Clients Example 2 Computer: IBM PS/2 (Enhanced workstation, on one network) Operating system: MS-DOS Protocol driver: NetBEUI 2.1, Ungerman Bass XNS™ Media-access control driver: 3Com EtherLink/MC CONFIG.SYS entries: DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\ELNKMC\ELNKMC.DOS DEVICE=C:\LANMAN.DOS\drivers\protocol\xns\UBXPS.DOS AUTOEXEC.BAT entries: @REM === LANMAN 2.2 == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.
Chapter 8 About Network Device Drivers 123 [XNS_XIF] ;************************************************************* ; Ungermann-Bass XNS protocol ;************************************************************* ; Please read C:\LANMAN.DOS\drivers\protocol\xns\protocol.sam for ; optional settings for the XNS protocol. There are several ; parameters that configure the driver's memory usage.
124 Installation Guide for Clients Example 3 Computer: IBM AT or compatible (Enhanced workstation, on two networks) Operating system: MS-DOS Protocol driver: NetBEUI 2.1, Microsoft TCP/IP Media-access control driver: 3Com Etherlink II, NCR®WaveLAN CONFIG.SYS entries: DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\ELNKII\ELNKII.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\WAVELAN\NCR.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\tcpip\tcpdrv.
Chapter 8 About Network Device Drivers [TCPIP_XIF] DRIVERNAME = TCPIP$ IPADDRESS0 = 11 1 20 9 SUBNETMASK0 = 255 255 0 0 DEFAULTGATEWAY0 = 11 1 20 1 NBSESSIONS = 6 LOAD = tcptsr[c],tinyrfc[c],emsbfr[cr] UNLOAD = "unloadt /notsr[dc]" BINDINGS = "ELNKII_NIF" LANABASE = 1 [ELNKII_NIF] ; protocol.ini section for the 3Com Etherlink II Adapter IOADDRESS = 0x310 INTERRUPT = 4 MAXTRANSMITS = 40 DRIVERNAME = ELNKII$ [WAVELAN_NIF] ; Protocol.ini entry for NCR WaveLAN Communications Adapter.
126 Installation Guide for Clients Example 4 Computer: COMPAQ EISA (OS/2 workstation on two networks) Operating system: MS OS/2 1.3 Protocol driver: Netbeui 2.1, Microsoft TCP/IP Media-access control driver: Novell NE 3200 CONFIG.SYS entries: REM === LANMAN 2.2 == DO NOT MODIFY BETWEEN THESE LINES == LANMAN 2.2 === DEVICE=C:\LANMAN\DRIVERS\PROTMAN\PROTMAN.OS2 /i:C:\LANMAN DEVICE=C:\LANMAN\DRIVERS\ETHERNET\NE3200\NE3200.OS2 RUN=C:\LANMAN\DRIVERS\PROTOCOL\tcpip\starttcp.
Chapter 8 About Network Device Drivers [TCPIP_XIF] DRIVERNAME = TCPIP$ IPADDRESS0 = 11 1 18 130 SUBNETMASK0 = 255 255 255 0 DEFAULTGATEWAY0 = 11 1 18 1 NBSESSIONS = 40 NUMNCBS = 85 BINDINGS = "NE3200_NIF" [NE3200_NIF] ;********************* ;** Novell NE3200 ** ;********************* ; ; ; ; ; ; DRIVERNAME = NE3200$ NETADDRESS = NOT REQUIRED MAXREQUESTS = 6 MAXTRANSMITS = 6 MAXFRAMESIZE = 1514 MAXMULTICAST = 50 The following parameters are set with the EISA Configuration utility.
128 Installation Guide for Clients Example 5 Computer: IBM AT or compatible (Basic workstation, on one network) Operating system: MS-DOS Protocol driver: Netbeui 2.1 Media-access control driver: 3Com EtherLink CONFIG.SYS entries: files= 30 DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\HIMEM.SYS rem DEVICE=C:\LM22\DRIVERS\DOSUTILS\EMM386.EXE NoEMS LASTDRIVE=Z DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\ELNK\ELNK.DOS device=C:\WIN30\smartdrv.
Chapter 8 About Network Device Drivers [ELNK_NIF] ; protocol.ini section for the 3Com Etherlink Adapter IOADDRESS = 0x300 INTERRUPT = 5 DMACHANNEL = NONE DMAMODE = BURST MAXTRANSMITS = 12 DRIVERNAME = ELNK$ LANMAN.
130 Installation Guide for Clients
131 C H A P T E R 9 Network Device Driver Options The LAN Manager Setup program sets the configuration options for the network device drivers you install, and usually you don’t need to change them. However, if the default settings conflict with other devices in your computer or if an application program requires a different device-driver option, you can change the configuration of a driver. In addition, some options can be fine-tuned for optimal performance.
132 Installation Guide for Clients There are several utilities that will assist you in using protocol drivers. These are: Load The load utility is used on MS-DOS workstations to load another protocol. The load utility can also be used to view a list of protocols currently loaded into memory. Unload The unload utility is used to first break the connection with the network and then unload the specified protocol.
Chapter 9 Network Device Driver Options 133 The following table summarizes the possible entries and values in the [netbeui] section of the LAN Manager PROTOCOL.
134 Installation Guide for Clients The entries for NetBEUI that you are most likely to adjust are sessions, ncbs, maxtransmits, mintransmits, packets, windowerrors, and selectors. You can change the entry values on an OS/2 workstation to the default MS-DOS values. Changing to the default MS-DOS values conserves memory and other system resources. Entries in the [netbeui] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 135 dlcretries Specifies the number of transmission retries that NetBEUI makes before assuming that the receiver’s DLC layer is not responding. You can lower the value of this entry on a highly reliable network, where few packets are dropped. Raise the value if the network is prone to dropping packets.
136 Installation Guide for Clients maxout Specifies the number of NetBIOS message packets to send before expecting an acknowledgment. This number is often called the “send window.” When the adaptrate entry is present and has a value of zero, the maxout value is not dynamically adjusted. Otherwise, the NetBEUI driver adjusts the maxout value as described in the adaptrate entry in this section. Set the maxout value to be near but not less than the value of maxin.
Chapter 9 Network Device Driver Options 137 netbiosretries Specifies the number of times the NetBEUI driver retries transmissions at the NetBIOS level before assuming that the receiver is not present. This entry is specific to name claims, session setups, and similar activities. For another limit on transmission attempts, see the dlcretries entry in this section. netbiostimeout Specifies the time in milliseconds that the NetBEUI driver waits between retrying transmissions.
138 Installation Guide for Clients selectors (OS/2 only) Specifies the number of internal data descriptors to allocate for global descriptor table (GDT) selectors from OS/2. GDT selectors are a precious resource in OS/2; if you allocate too many, you decrease the performance of other programs and drivers. The NetBEUI driver uses GDT selectors to copy data into user buffers on RECEIVE, RECEIVE-ANY, and RECEIVE-ANY-ANY NCB operations.
Chapter 9 Network Device Driver Options 139 If you set t2 too high, there may be long delays between transmissions while the sender is waiting for acknowledgment. If you set t2 too low, you can generate acknowledgments before the receive window fills up, thus wasting time and lowering performance. In general, increase t2 when using a heavily loaded network, and decrease it when using a lightly loaded network. For an explanation of the relationship among the three timer entries, see the t1 entry.
140 Installation Guide for Clients Media-Access Control Drivers The following table lists the media-access control drivers shipped with LAN Manager version 2.2. In addition to the drivers listed, some manufacturers ship network adapters with other device drivers that work with LAN Manager. The filename extension, when indicated as .ext in the table, is .OS2 for OS/2 and .DOS for MS-DOS. Filename Network adapter(s) supported ELNK.ext ELNKII.ext ELNKII.ext ELNKIII.ext ELNK16.ext ELNKMC.ext ELMC32.
Chapter 9 Network Device Driver Options Filename Network adapter(s) supported DEPCA.ext PC04.OS2 PCNDIS.DOS PC04.OS2 PCNDIS.DOS ED586.ext MACEVX.ext HPLANB.ext HPLANB.ext HPLANB.ext HPLANE.
142 Installation Guide for Clients Filename Network adapter(s) supported NE2000.ext NSEISA.ext SLAN.ext NCR.ext NCRTRN.ext EISA_LM.ext AT_LM.ext AT_LM.ext NE2000.ext NE2000.ext NE1000.ext NE2000.ext NE3200.ext OLITOK.ext PRO4.ext PRO4.ext PRO4.ext PRO4.ext NDIS139.ext NDIS139.ext PRO4.ext CPQTOK.ext MSARC.ext MSARC.ext PDIETH.ext PDIETH.ext PDIETH.ext OLITOK.ext OLITOK.ext OLITOK.ext WAVELAN.ext WAVELAN.ext ES3210.ext NI5210.ext NI6510.
Chapter 9 Network Device Driver Options Filename Network adapter(s) supported NI9210.ext RTR16LM.ext RTR16LM.ext RTR16LM.ext RCE.ext RCE.ext RMMCETH.ext RMATETH.ext SPIDER.ext SMC3016.ext SMC_ARC.ext SMC_ARC.ext SMC_ARC.ext SMC_ARC.ext SMC_ARC.ext SMC_ARC.ext SMCMAC.ext SMCMAC.ext SMCMAC.ext SMCMAC.ext SMCMAC.ext TCCARC.ext TCCTOK.ext TCCARC.ext TCCARC.ext TNDIS.ext TSBETHER.ext NCC16.ext UBNEA.ext UBNEA.ext UBNEA.ext UBNEI.ext UBNEI.ext UBNEPS.ext UBNEI.
144 Installation Guide for Clients Filename Network adapter(s) supported UBNEI.ext TOKWD.ext TOKWD.ext I82593.ext * Ungermann-Bass NICps/EOTP (PC4035) Western Digital 8-bit Token Ring (WD 8005TR) Western Digital 16-bit Token Ring (WD 8015TR) Zenith Data Systems Z.Note 325L Notebook PC * The .OS2 device driver for this network adapter is not certified to work with IBM OS/2 2.0; however, it is certified to work with MS OS/2 1.x.
Chapter 9 Network Device Driver Options 145 3Com EtherLink Required entry: • drivername = elnk$ or elnkn$ The following table summarizes the possible entries and values in the [elnk] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel integer none, 1, or 3 dmamode drivername interrupt ioaddress maxrequests maxtransmits netaddress — — integer hex. integer integer hex. byte, burst — 2–7 200–3F0 8–32 8–50 12 hex.
146 Installation Guide for Clients interrupt Indicates the interrupt level of the network adapter. Note On an 80286 or 80386 computer, specifying interrupt level 2 redirects to interrupt level 9 because the cascaded programmable interrupt control (PIC) is already using interrupt level 2. ioaddress Indicates the current I/O address jumper configuration of the network adapter. The value you select on the adapter must equal this entry’s value.
Chapter 9 Network Device Driver Options 147 3Com EtherLink II Required entry: • drivername = elnkii$ or elnkiin$ This driver is for the following network adapters: • 3Com EtherLink II (3C503) • 3Com EtherLink II/16 TP When an EtherLink II adapter runs in shared-memory mode, the datatransfer and dmachannel entries are ignored. The data-transfer mode is memory-to-memory string moves.
148 Installation Guide for Clients Entries in the [elnkii] section of the LAN Manager PROTOCOL.INI file have the following meanings: datatransfer Sets the data-transfer mode for the network adapter according to the following values: Value Compatible Computers block_dma demand_dma single_dma pio_word pio_byte 8086 and 8088 (fast) 8086 and 8088 (intermediate) 8086 and 8088 (slow) 80286 and 80386 (fast) 80286 and 80386 (slow) This entry is ignored when the adapter runs in shared-memory mode.
Chapter 9 Network Device Driver Options 149 netaddress Overrides the network address of the network adapter. Use this entry only when there are duplicate addresses on the network. The value of this entry is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001". transceiver Identifies the transceiver on the network adapter. The value is either onboard (for a BNC connection) or external (for an AUI or a DIX connection).
150 Installation Guide for Clients 3Com EtherLink III Family Required entry: • drivername = elnk3$ or elnk3n$ This driver is for the following network adapters: • 3Com EtherLink III Family The following table summarizes the possible entries and values in the [elnk3] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername ioaddress maxtransmits netaddress slot — hex. integer hex integer — 0x200–0x3E0 2–50 12 hex.
Chapter 9 Network Device Driver Options 151 3Com EtherLink 16 Required entry: • drivername = elnk16$ or elnk16n$ The following table summarizes the possible entries and values in the [elnk16] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — iobase netaddress hex. hex. 200–3F0 12 hex. digits elnk16$ or elnk16n$ 300 — Entries in the [elnk16] section of the LAN Manager PROTOCOL.
152 Installation Guide for Clients 3Com EtherLink Plus Required entry: • drivername = elnkpl$ or elnkpln$ The following table summarizes the possible entries and values in the [elnkpl] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default datatransfer dmachannel drivername — integer — — 1, 3, or 5–7 — interrupt ioaddress maxtransmits netaddress integer hex. integer hex. 3–15 300–3F0 8–50 12 hex.
Chapter 9 Network Device Driver Options 153 netaddress Overrides the network address of the network adapter. This entry should only be used if, for some reason, there are duplicate addresses on the network. The value of this entry is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001".
154 Installation Guide for Clients 3Com EtherLink/MC Required entry: • drivername = elnkmc$ or elnkmcn$ Note Use the reference disk to set the transceiver type. The following table summarizes the possible entries and values in the [elnkmc] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — maxtransmits netaddress slotnumber integer hex. integer 8–50 12 hex.
Chapter 9 Network Device Driver Options 155 3Com EtherLink/MC32 Required entry: • drivername = elmc32$ or elmc32n$ The following table summarizes the possible entries and values in the [elmc32] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default bridge drivername — — off, on — maxtransmits netaddress recvbufs slotnumber integer hex. integer integer 8–36 12 hex.
156 Installation Guide for Clients 3Com TokenLink Required entry: • drivername = tlnk$ or tlnkn$ The following table summarizes the possible entries and values in the [tlnk] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel (80286 and 80386 computers only) drivername interrupt ioaddress maxtransmits netaddress product_id speed integer 0, 1, 3, 5, 6, or 7 1 — integer hex. integer hex. hex. — — 2–15 300–350 8–40 12 hex. digits 36 hex.
Chapter 9 Network Device Driver Options 157 These are the possible interrupt values: Value Compatible Computers 2, 3, 4, 5 3, 4, 5, 9 3, 4, 5, 9, 10, 11, 12, 14, 15 8086 and 8088 computer 80286 and 80386 computer, 8-bit slot. 80286 and 80386 computer, 16-bit slot (Levels 10–14 are available only if the adapter is ASSY 3410-03 revision A or later.) ioaddress Indicates the current I/O address jumper configuration of the network adapter. This entry must match the adapter’s switch settings.
158 Installation Guide for Clients Accton Technology EtherCoax - 16N This driver is for OS/2 only. Required entry: • drivername = ethne$ or ethenen$ The following table summarizes the possible entries and values in the [ethne] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — irq iobase receivebufsize integer hex. bytes 2–5 200H–3E0H — ethne$ or ethenen$ 3 300H 1024 Entries in the [ethne] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 159 AMD AM2100 Required entry: • drivername = am2100$ or am2100n$ The following table summarizes the possible entries and values in the [am2100] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel drivername integer — 3, 5, 6, 7 — interrupt ioaddress integer hex. 3, 4, 5, 9 200–3E0 5 am2100$ or am2100n$ 9 300 Entries in the [am2100] section of the LAN Manager PROTOCOL.
160 Installation Guide for Clients Amplicard AC 210/AT Required entry: • drivername = ms2000$ or ms2000n$ This driver is for the following network adapters: • Amplicard AC 210/AT • National Semiconductor EtherNODE *16AT • National Semiconductor AT/LANTIC EtherNODE 16-AT3 • Networth EtherneXt 16-bit UTP adapter • Novell NE2000 • Novell NE/2 The following table summarizes the possible entries and values in the [ne2000] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 161 Amplicard AC 210/XT Required entry: • drivername = ms1000$ or ms1000n$ This driver is for the following network adapters: • Amplicard AC 210/XT • Novell NE1000 The following table summarizes the possible entries and values in the [ne1000] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — interrupt iobase integer hex.
162 Installation Guide for Clients Cabletron E2010-X Required entry: • drivername = e20ndis$ or e20ndisn$ The following table summarizes the possible entries and values in the [e20ndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — interrupt integer ioaddress hex. 3, 4, 5, 6, 7, 9, 10, 11, 12, 14, 15 220, 280, 300, 380 e20ndis$ or e20ndisn$ 3 380 Entries in the [e20ndis] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 163 Cabletron E2112 Required entry: • drivername = e21ndis$ or e21ndisn$ The following table summarizes the possible entries and values in the [e21ndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — interrupt integer ioaddress hex. media sharedram — hex.
164 Installation Guide for Clients Cabletron E3010-X Required entry: • drivername = e30ndis$ or e30ndisn$ The following table summarizes the possible entries and values in the [e30ndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — e30ndis$ or e30ndisn$ Entries in the [e30ndis] section of the LAN Manager PROTOCOL.INI file have the following meanings: drivername Identifies the driver name of the network device driver.
Chapter 9 Network Device Driver Options 165 Cabletron E3112-X Required entry: u drivername = e31ndis$ or e31ndisn$ The following table summarizes the possible entries and values in the [e31ndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — e31ndis$ or e31ndisn$ Entries in the [e31ndis] section of the LAN Manager PROTOCOL.INI file have the following meanings: drivername Identifies the driver name of the network device driver.
166 Installation Guide for Clients Cabletron T2015 Required entry: • drivername = t20ndis$ or t20ndisn$ The following table summarizes the possible entries and values in the [t20ndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default bandwidth dmachannel drivername integer integer — 0 or 1 5, 6, or 7 — interrupt integer ioaddress hex.
Chapter 9 Network Device Driver Options 167 interrupt Indicates the interrupt level of the network adapter. ioaddress Indicates the current I/O address jumper configuration of the network adapter. This entry must match the adapter’s switch settings. maxmulticast Specifies the maximum number of multicast addresses that the driver allows. maxrequests Specifies the maximum number of general requests that can be pending at one time. maxtransmits Specifies the number of transmit queue entries in this driver.
168 Installation Guide for Clients Cabletron T3015 Required entry: • drivername = t30ndis$ or t30ndisn$ The following table summarizes the possible entries and values in the [t30ndis] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 169 media Identifies driver assignments when more than one token ring network adapter is installed. The pri entry denotes the first (primary) adapter; sec denotes the second adapter. receivebuffers Specifies the number of receive buffers to use. Any memory left on the adapter is configured as extra receive buffers. receivebufsize Specifies the size of the receive buffers, in bytes. receivechains Specifies the number of receive chain-header queue entries.
170 Installation Guide for Clients Compaq 32-Bit DualSpeed Token Ring Required entry: • drivername = cpqtok$ or cpqtokn$ This driver is for the following network adapters: • Compaq 32-bit DualSpeed Token Ring • Proteon P1990 The following table summarizes the possible entries and values in the [cpqtok] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 171 maxreceives Specifies the maximum number of receive buffers that can be queued at one time. maxrequests Specifies the maximum number of general requests that can be pending at one time. maxtransmits Specifies the maximum number of buffers that can be queued for transmission at one time. netaddress Overrides the network address of the adapter. This entry should only be used if there are duplicate addresses on the network.
172 Installation Guide for Clients Compaq NE3200 Required entry: • drivername = ne3200$ or ne3200n$ This driver is for the following network adapters: • Compaq NE3200 • Intel EtherExpress 32 • Novell NE3200 The following table summarizes the possible entries and values in the [ne3200] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — maxframesize maxmulticast maxreceives maxrequests maxtransmits netaddress integer integer integer integer integer hex.
Chapter 9 Network Device Driver Options 173 maxrequests Sets the maximum number of general requests that can be pending at one time. maxtransmits Sets the number of transmit-queue entries in the driver. netaddress Overrides the network address. Use this entry only when there are duplicate addresses on the network. The value is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001".
174 Installation Guide for Clients Compex ENET16/U Required entry: • drivername = enet$ or enetn$ The following table summarizes the possible entries and values in the [enet] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt — integer enet$ or enetn$ 3 iobase maxtransmits ramaddress hex. integer hex. — 2, 3, 4, 5, 7, 10, 11, 15 200–340 1–50 B000–EC00 280 10 D000 Entries in the [enet] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 175 DCA 10 megabit Required entry: • drivername = mac586$ This driver is for the following network adapters: • DCA 10-megabit twisted pair • DCA 10-megabit fiber-optic adapter • DCA 10-megabit 16-bit ISA adapter The following table summarizes the possible entries and values in the [mac586] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt ioaddress ram slot — integer hex. hex.
176 Installation Guide for Clients ram Indicates the base-segment address of the dual-port memory for the adapter. Valid entries are: A000, A400, A800, AC00, C000, C400, C800, CC00, D000, D400, D800, DC00. If the machine has 512K of base RAM, the following values are also available: 8000, 8400, 8800, 8C00, 9000, 9400, 9800, 9C00. The ram parameter is ignored on a Micro Channel Architecture computer. slot Indicates the Micro Channel slot where the adapter is located. This value is not valid for ISA.
Chapter 9 Network Device Driver Options 177 DCA IRMATrac Token-Ring/Convertible 16/4 Required entry: • drivername = irmatr$ The following table summarizes the possible entries and values in the [irmatr] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default datarate datatransfer integer — 16 pio dmachannel drivername earlyrelease interrupt integer — — integer ioaddress maxtransmits netaddress ram recvbufcount recvbufsize hex. integer hex. hex.
178 Installation Guide for Clients drivername Identifies the driver name of the network device driver. earlyrelease Indicates that the network adapter should use the early token release option, which increases the efficiency. interrupt Indicates the interrupt level of the network adapter. The interrupt level can be 2, 3, 5, or 7 under MS-DOS; under OS/2, the interrupt level can be 3, 5, or 7. The interrupt is ignored on MicroChannel computers.
Chapter 9 Network Device Driver Options 179 DEC DEPCA Required entry: • drivername = depca$ This driver is for the following network adapters: • DEC DEPCA • DEC EtherWORKS LC • DEC EtherWORKS Turbo • DEC EtherWORKS MC The following table summarizes the possible entries and values in the [depca] section of the LAN Manager PROTOCOL.
180 Installation Guide for Clients Dowty Required entry for OS/2: • drivername = pc04$ Required entry for MS-DOS: • drivername = pcndis$ These drivers are for the following network adapters: • Dowty PC0114 • Dowty PS0114 The following table summarizes the possible entries and values in the [dowty] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 181 loopback Indicates whether to turn off loopback. Use on when the protocol is ScaNet/NetBIOS for OS/2; use off when using any other protocol. maxqcb Specifies the maximum number of queue control blocks for data transmission. memaddress Specifies the start address of the shared RAM on the adapter. This value must match the configuration of the ScaNet board. notxownpkt Specifies whether the driver should suppress its own send.
182 Installation Guide for Clients Eden Sistemas ED586/32 Required entry: • drivername = ed586$ • end_io = 0x2CE, 0x2EE, 0x3CE, or 0x3EE • end_memoria = 0xC000, 0xC800, 0xD000, or 0xD800 • interrupcao = 2, 3, 4, 5, 6, or 7 The following table summarizes the possible entries and values in the [ed586] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername end_io — hex. ed586$ 3EE end_memoria hex.
Chapter 9 Network Device Driver Options interrupcao Indicates the interrupt level of the network adapter. This parameter must be present or the driver will fail to initialize.
184 Installation Guide for Clients Everex SpeedLink/PC16 Required entry: • drivername = macevx$ The following table summarizes the possible entries and values in the [macevx] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt ioaddress — integer hex. — 2–15 320–3A0 macevx$ 2 360 Entries in the [macevx] section of the LAN Manager PROTOCOL.INI file have the following meanings: drivername Identifies the driver name of the network device driver.
Chapter 9 Network Device Driver Options 185 HP Ethertwist Required entry: • drivername = hplan$ or hplann$ This driver is for the following network adapters: • HP Ethertwist PC Link (8-bit ISA) • HP Ethertwist PC Link16 (16-bit ISA) • HP Ethertwist MCA Adapter (HP27246) Note After using the Setup program to specify the device driver for the HP Ethertwist network adapter, edit the PROTOCOL.INI file so that the section heading is [hplan], not [hplan_nif].
186 Installation Guide for Clients interrupt Indicates the interrupt level of the network adapter. The interrupt level can range from 2 to 7 inclusive. The interrupt parameter should match the adapter’s interrupt jumper settings. (Does not apply to HP Ethertwist MC.) The default setting is 3. ioaddress Indicates the base I/O address for the network adapter. If this entry does not match the adapter’s I/O address jumper settings, the driver reports an error.
Chapter 9 Network Device Driver Options 187 HP Ethertwist Required entry: • drivername = hplanb$ or hplanbn$ This driver is for the following network adapters: • HP Ethertwist 8 TL (PC27250A) • HP Ethertwist 8 TP (HP27245) • HP Ethertwist 16 TP (HP27247B) Note Do not use the HP Ethertwist 8 TP (HP27245) network adapters with 386/25 or faster computers. The following table summarizes the possible entries and values in the [hplanb] section of the LAN Manager PROTOCOL.
188 Installation Guide for Clients maxhwtrans Indicates the number of full-sized transmit packets that can be simultaneously stored in the adapter-transmit queue. Each transmit packet consumes 1536 bytes; remaining adapter memory is used for the receive-ring buffer. This parameter partitions the adapter memory into a transmit queue and a receive-ring buffer. maxmulticast Indicates the maximum number of multicast addresses that can be simultaneously stored by the driver.
Chapter 9 Network Device Driver Options 189 HP Ethertwist EISA LAN Adapter/32 Required entry: • drivername = hplane$ or hplanen$ The following table summarizes the possible entries and values in the [hplane] section of the LAN Manager PROTOCOL.
190 Installation Guide for Clients maxmulticast Indicates the maximum number of multicast addresses that can be simultaneously stored by the driver. Each address consumes 16 bytes of computer memory. maxswtrans Indicates the number of packets that can simultaneously be stored in the software queue. The driver may put a transmit packet into the software queue before sending it to the adapter-transmit queue. Each packet consumes 144 bytes of computer memory.
Chapter 9 Network Device Driver Options 191 HP PC LAN Adapter/16+ Required entry: • drivername = hplanp$ or hplanpn$ This driver is for the following network adapters: • HP PC LAN Adapter/16+ TL (HP27252A) • HP PC LAN Adapter/16+ TP (HP27247B) The following table summarizes the possible entries and values in the [hplanp] section of the LAN Manager PROTOCOL.
192 Installation Guide for Clients ioaddress Indicates the base I/O address for the network adapter. If this entry does not match the adapter’s I/O address jumper settings, the driver reports an error. maxhwtrans Indicates the number of full-sized transmit packets that can be simultaneously stored in the adapter-transmit queue. Each transmit packet consumes 1536 bytes; remaining adapter memory is used for the receive-ring buffer.
Chapter 9 Network Device Driver Options 193 Hughes Lan Systems 6130 Required entry: • drivername = hls6130$ or hls6130n$ The following table summarizes the possible entries and values in the [hls6130] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt iobase — integer hex. — 2–3 360, 368 hls6130$ or hls6130n$ 3 368 Entries in the [hls6130] section of the LAN Manager PROTOCOL.
194 Installation Guide for Clients IBM Token-Ring Adapters Required entry: • drivername = ibmtok$ or ibmtokn$ This driver is for the following network adapters: • IBM Token-Ring Adapter • IBM Token-Ring Adapter II • IBM Token-Ring Adapter/A • IBM Token-Ring 16/4 Adapter • IBM Token-Ring 16/4 Adapter/A Note If you are using older models of the IBM Token-Ring 16/4 network adapters and protocols fail to bind, add a few more bytes to the upper bound of the EMM386.
Chapter 9 Network Device Driver Options 195 Entries in the [ibmtok] section of the LAN Manager PROTOCOL.INI file have the following meanings: drivername Identifies the driver name of the network device driver. The base portion of the filename, plus a digit when more than one Token-Ring driver is installed, is the drivername. The drivername is ibmtok$ for the first Token-Ring driver, ibmtok2$ for the second, and so on.
196 Installation Guide for Clients ram (Token-Ring Adapter and Token-Ring Adapter II only) Specifies the physical RAM location on the adapter if the default location is not adequate. The value of ram is a hexadecimal number between 0xA000 and 0xF000, located on an 8K boundary for the Token-Ring adapter or a 16K boundary for the Token-Ring II adapter. The RAM location defaults to a location immediately following the read-only memory (ROM) on the next appropriate boundary.
Chapter 9 Network Device Driver Options 197 xmitbufsize Specifies the size of the transmit buffers in bytes. The value must be a multiple of 8. The maximum size of a transmit buffer depends on the adapter you are using. The original Token-Ring Adapter, Token-Ring Adapter II, and Token-Ring Adapter/A adapters allow only 2040 bytes. The newer Token-Ring 16/4 Adapter and Token-Ring 16/4 Adapter/A adapters allow 4096 bytes at the 4-MBPS adapter setting and 17,952 bytes at the 16-MBPS setting.
198 Installation Guide for Clients IBM PC Network II and Baseband Required entry: • drivername = ibmneta$ or ibmnetan$ This driver is for the following network adapters: • IBM PC Network II • IBM Baseband The following table summarizes the possible entries and values in the [ibmnet] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 199 IBM PC Network II/A and Baseband/A Required entry: • drivername = ibmneta$ or ibmnetan$ This driver is for the following network adapters: • IBM PC Network II/A • IBM Baseband/A The following table summarizes the possible entries and values in the [ibmneta] section of the LAN Manager PROTOCOL.
200 Installation Guide for Clients maxtransmits Sets the maximum number of outstanding transmit-chain commands. This entry configures the size of the transmit chain-request queue. receivebuffers Configures the number of receive buffers in the receive-buffer pool. receivebufsize Configures the size in bytes of receive buffers in the receive-buffer pool.
Chapter 9 Network Device Driver Options 201 ICL Etherteam 16 Required entry: • drivername = ethiie$ The following table summarizes the possible entries and values in the [ethiie] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername irqnumber ioaddress maxtransmits netaddress transceiver — integer hex. integer hex. — — 2–15 290–320 1–50 12 hex. digits — ethiie$ 2 300 6 — auto Entries in the [ethiie] section of the LAN Manager PROTOCOL.
202 Installation Guide for Clients Intel EtherExpress 16 Required entry: • drivername = exp16$ This driver is for the following network adapters: • Intel EtherExpress 16 • Intel EtherExpress 16TP The following table summarizes the possible entries and values in the [exp16] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername ioaddress — hex. — 200–370 exp16$ 300 Entries in the [exp16] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 203 Intel EtherExpress 32 Required entry: • drivername = ne3200$ or ne3200n$ This driver is for the following network adapters: • Compaq NE3200 • Intel EtherExpress 32 • Novell NE3200 The following table summarizes the possible entries and values in the [ne3200] section of the PROTOCOL.INI file: Entry Units Range Default drivername maxframesize maxmulticast maxreceives maxrequests maxtransmits netaddress — integer integer integer integer integer hex.
204 Installation Guide for Clients maxtransmits Sets the number of transmit-queue entries in the driver. netaddress Overrides the network address. Use this entry only when there are duplicate addresses on the network. The network address value is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001".
Chapter 9 Network Device Driver Options 205 Intel Motherboard Lan Module Required entry: • drivername = i82593$ or i82593n$ This driver is for the following network adapters: • Intel Motherboard Lan Module • Zenith Data Systems Z.Note 325L Notebook PC The following table summarizes the possible entries and values in the [i82593] section of the PROTOCOL.
206 Installation Guide for Clients inbuffer Indicates the size, in bytes, of the memory to use for a receive buffer. The buffer memory is in host memory, so any increase will reduce the amount of memory available to applications. This value should be 8 for MS-DOS. interrupt Indicates the interrupt level of the network adapter. The interrupt can be any legal ISA interrupt request (IRQ) line. The default is 10. ioaddress Indicates the current I/O address jumper configuration of the network adapter.
Chapter 9 Network Device Driver Options 207 Intel TokenExpress Adapters Required entry: • drivername = olitok$ or olitokn$ This driver is for the following network adapters: • Intel TokenExpress EISA 16/4 • Intel TokenExpress ISA 16/4 • Intel TokenExpress MCA 16/4 • Olicom 16 bit ISA • PureData PDI9025-16 • PureData PDE9025-32 • PureData PDuC9025 The following table summarizes the possible entries and values in the [olitok] section of the LAN Manager PROTOCOL.
208 Installation Guide for Clients maxrequests Specifies the maximum number of outstanding general requests and configures the size of the general request queue. maxtransmits Specifies the maximum number of outstanding transmit chain commands. This configures the size of the transmit chain request queue. nodeaddress If specified, this entry will be used in place of the universal burned-in node address on the adapter.
Chapter 9 Network Device Driver Options Madge Networks Smart 16/4 Required entry: • drivername = smartnd$ or smartndn$ This driver is for the following network adapters: • Madge Networks Smart 16/4 AT RingNode • Madge Networks Smart 16/4 EISA RingNode • Madge Networks Smart 16/4 MC RingNode • Madge Networks Smart 16/4 XT RingNode The following table summarizes the possible entries and values in the [madge] section of the LAN Manager PROTOCOL.
210 Installation Guide for Clients Entries in the [madge] section of the LAN Manager PROTOCOL.INI file have the following meanings: autoopen Indicates whether to provide the openadapter and closeadapter functions for the protocol. If this parameter is set to yes, these functions are not made available to the protocol, and the adapter is opened automatically by the driver at bind time. It is recommended that you specify autoopen=yes if you are using the network adapter in a server.
Chapter 9 Network Device Driver Options 211 nodeaddress Overrides the burned-in-address of the network adapter. This value is a 12-digit hexadecimal value enclosed in quotation marks, such as "02608C010001". openoptions Specifies a hexadecimal number that sets the open options for the token-ring adapter.
212 Installation Guide for Clients txbuffersize Specifies the size, in bytes, of the transmit buffer, which is used for holding received frames. This buffer must be at least big enough to contain a maximum size frame (maxframesize). Increasing the size of this buffer can improve system performance. If you have sufficient memory in your system, it is recommended that you increase this buffer. The default for MS-DOS is the maxframesize parameter.
Chapter 9 Network Device Driver Options 213 National Semiconductor EtherNODE Required entry: • drivername = ms2000$ or ms2000n$ This driver is for the following network adapters: • Amplicard AC210/AT • National Semiconductor EtherNODE *16AT • National Semiconductor EtherNODE 16-AT3 • Networth EtherneXt 16-bit UTP adapter • Novell NE2000 • Novell NE/2 The following table summarizes the possible entries and values in the [ne2000] section: Entry Units Range Default drivername interrupt iobase — intege
214 Installation Guide for Clients National Semiconductor Sonic EISA (DP83932EB) Required entry: • drivername = nseisa$ or nseisan$ The following table summarizes the possible entries and values in the [nseisa] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt ioaddress — integer hex. — 5, 9, 10, 11 1000–8000 nseisa$ or nseisan$ 9 4000 Entries in the [nseisa] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 215 NCR StarCard (8 bit) Required entry: • drivername = starlan$ The following table summarizes the possible entries and values in the [ncrslan] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dma_channel0 dma_channel1 drivername external_rom func_address interrupt lan_id_rom node_address integer integer — hex. — integer hex. hex.
216 Installation Guide for Clients func_address Indicates the NetBIOS functional address type. A value of new indicates that the address is compatible with LAN Manager; old indicates that the address is compatible with the first version of NCR StarLAN software. Specify old only for an existing network using the first version of NCR StarLAN software. interrupt Indicates the interrupt level of the network adapter. lan_id_rom Specifies the value of the LAN ID ROM where the burned-in address is stored.
Chapter 9 Network Device Driver Options 217 NCR Token-Ring 4 MBPS ISA Required entry: • drivername = ncrtrn$ or ncrtrnn$ The following table summarizes the possible entries and values in the [ncrtrn] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt max_xmt_size node_address port_address product_id shared_ram — — bytes hex. hex. hex. hex. — 2–7 64–4472 12 hex. digits 0A20–1A20 0–36 hex.
218 Installation Guide for Clients node_address Overrides the network address of the network adapter. Use this entry only when there are duplicate addresses on the network. The value is a hexadecimal string of 12 digits enclosed in quotation marks. The address must be in the range 400000000000 through 40007FFFFFFF. For strict IBM compatibility, use only decimal digits (0–9), as in "400001020304." The ncrtrn driver provides a unique default value for each network adapter.
Chapter 9 Network Device Driver Options 219 NCR Systems BV WaveLAN Required entry: • drivername = ncrwve$ or ncrwven$ This driver is for the following network adapters: • NCR Systems BV WaveLAN/AT • NCR Systems BV WaveLAN/MC • PureData PDI90211 • PureData PDuC90211 The following table summarizes the possible entries and values in the [wave_nif] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default acr drivername iobase decimal — hex.
220 Installation Guide for Clients Network Peripherals NP–EISA Required entry: • drivername = eisa_lm$ or eisa_lmn$ This driver is for the following network adapters: • NP–EISA/S • NP–EISA/D The following table summarizes the possible entries and values in the [eisa_lm] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername ethernetemulate force_ndis_v1 interrupt maxtransmits netaddress override_type stype_slot — — — integer integer hex.
Chapter 9 Network Device Driver Options 221 maxtransmits Indicates the number of transmits that can be queued by the driver. netaddress Overrides the network address. This entry should be used if, for some reason, there are duplicate addresses on the network. The value is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001". override_type Specifies whether the driver will override the type indicated by the adapter’s jumpers.
222 Installation Guide for Clients Network Peripherals NPI–AT Required entry: • drivername = at_lm$ or at_lmn$ This driver is for the following network adapters: • Network Peripherals NPI–AT/S • Network Peripherals NPI–AT/D The following table summarizes the possible entries and values in the [at_lm] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 223 netaddress Overrides the network address. This entry should be used if, for some reason, there are duplicate addresses on the network. The value is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001". override_type Specifies whether the driver will override the type indicated by the adapter’s jumpers. Values for this entry are yes or no; no is the default.
224 Installation Guide for Clients Networth EtherneXt 16-bit UTP Required entry: • drivername = ms2000$ or ms2000n$ This driver is for the following network adapters: • Amplicard AC210/AT • National Semiconductor EtherNODE *16AT • National Semiconductor AT/LANTIC EtherNODE 16-AT3 • Networth EtherneXt 16-bit UTP adapter • Novell NE2000 • Novell NE/2 The following table summarizes the possible entries and values in the [ne2000] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 225 Novell NE1000 Required entry: • drivername = ms1000$ or ms1000n$ This driver is for the following network adapters: • Amplicard AC210/XT • Novell NE1000 The following table summarizes the possible entries and values in the [ne1000] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — interrupt iobase integer hex. 2–5 200H–3E0H ms1000$ or ms1000n$ 3 300H Entries in the [ne1000] section of the LAN Manager PROTOCOL.
226 Installation Guide for Clients Novell NE2000 Required entry: • drivername = ms2000$ or ms2000n$ This driver is for the following network adapters: • Amplicard AC210/AT • National Semiconductor EtherNODE *16AT • National Semiconductor AT/LANTIC EtherNODE 16-AT3 • Networth EtherneXt 16-bit UTP adapter • Novell NE2000 • Novell NE/2 The following table summarizes the possible entries and values in the [ne2000] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 227 Novell NE3200 Required entry: • drivername = ne3200$ or ne3200n$ This driver is for the following network adapters: • Compaq NE3200 • Intel EtherExpress 32 • Novell NE3200 The following table summarizes the possible entries and values in the [ne3200] section of the PROTOCOL.INI file: Entry Units Range Default drivername — — maxframesize maxmulticast maxreceives maxrequests maxtransmits netaddress integer integer integer integer integer hex.
228 Installation Guide for Clients maxrequests Specifies the maximum number of general requests that can be pending at one time. maxtransmits Sets the number of transmit-queue entries in the driver. netaddress Overrides the network address. Use this entry only when there are duplicate addresses on the network. The network address value is a hexadecimal string of 12 digits enclosed in quotation marks, such as "02608C010001".
Chapter 9 Network Device Driver Options 229 Olicom 16 Bit ISA Required entry: • drivername = olitok$ or olitokn$ This driver is for the following network adapters: • Intel TokenExpress EISA 16/4 • Intel TokenExpress ISA 16/4 • Intel TokenExpress MCA 16/4 • Olicom 16 bit ISA • PureData PDI9025-16 • PureData PDE9025-32 • PureData PDuC9025 The following table summarizes the possible entries and values in the [omac] section of the PROTOCOL.
230 Installation Guide for Clients Entries in the [omac] section of the LAN Manager PROTOCOL.INI file have the following meanings: adapter Specifies which adapter will be accessed by the driver: Value Meaning 0 1 2 3 Primary adapter (I/O address is A20) Alternate adapter (I/O address is A24) Second primary adapter (I/O address is A50) Second alternate adapter (I/O address is A54) drivername Identifies the network driver.
Chapter 9 Network Device Driver Options 231 recbufsize Configures the size, in bytes, of buffers in the receive buffer pool. The maximum size of the frames that may be received by the adapter is determined by the following: min.(MaxFs, recbufsize * min.(8, recbufcount - 1)), where MaxFs is 4472 at 4 MBPS and 17954 at 16 MBPS. The maximum amount of receive buffers, recbufsize * recbufcount, must not exceed 64K. rpl Postpones the adapter initialization and diagnostics from boot time to bind time.
232 Installation Guide for Clients Proteon P134x, P1840 Required entry: • drivername = pro4$ or pro4n$ This driver is for the following network adapters: • Proteon P1340 • Proteon P1342 • Proteon P1346 • Proteon P1347 • Proteon P1840 The following table summarizes the possible entries and values in the [pro4] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel drivername interrupt iobase membase nodeaddr integer — integer hex. hex. hex.
Chapter 9 Network Device Driver Options 233 membase Indicates the base address of the shared memory on the adapter. This value must match the settings on the adapter’s jumpers. nodeaddr Overrides the burned-in-address of the network adapter. This value must be enclosed in quotation marks, such as "02608C010001".
234 Installation Guide for Clients Proteon ProNET-4/16 P139x Token Ring Required entry: • drivername = ndis139$ This driver is for the following network adapters: • Proteon P1390 • Proteon P1392 The following table summarizes the possible entries and values in the [proteon] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel dmaclock drivername intlevel integer — — integer 5 8 ndis139$ 5 iobase linkspeed maxtransmits media netaddress saen hex.
Chapter 9 Network Device Driver Options 235 iobase Indicates the base I/O address for the network adapter. linkspeed Configures the network adapter for either 4 MBPS or 16 MBPS data transfer rate. maxframesize Specifies the size of the RECEIVE and TRANSMIT buffers, in bytes. The maximum size of the buffers depends on the network speed setting. The adapter allows a value of 4096 at the 4 MBPS setting and 17952 at the 16 MBPS setting.
236 Installation Guide for Clients Proteon P1990 Required entry: • drivername = cpqtok$ or cpqtokn$ This driver is for the following network adapters: • Compaq 32-bit DualSpeed Token Ring • Proteon P1990 The following table summarizes the possible entries and values in the [cpqtok] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — earlyrelease maxframesize maxreceives maxrequests maxtransmits netaddress product_id — bytes integer integer integer hex. hex.
Chapter 9 Network Device Driver Options 237 maxreceives Specifies the maximum number of receive buffers that can be queued at one time. maxrequests Specifies the maximum number of general requests that can be pending at one time. maxtransmits Specifies the maximum number of buffers that can be queued for transmission at one time. netaddress Overrides the network address of the adapter. This entry should only be used if there are duplicate addresses on the network.
238 Installation Guide for Clients PureData Arcnet Adapters Required entry: • drivername = msarc$ or msarcn$ This driver is for the following network adapters: • PureData PDI508+ • PureData PDI516+ The following table summarizes the possible entries and values in the [msarc] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — interrupt iobase maxtransmits memorybase integer hex. integer hex.
Chapter 9 Network Device Driver Options 239 memorybase Indicates the base I/O memory address for the network adapter. If this entry does not match the adapter’s I/O address jumper settings, the driver reports an error. For the PDI508+, this value can be A000H, C000H, C400H, CC00H, D000H, DC00H, or E000H. For the PDI516+, this value can be C000H, C400H, CC00H, D000H, D400H, or DC00H.
240 Installation Guide for Clients PureData Ethernet Adapters Required entry: • drivername = pdieth$ or pdiethn$ This driver is for the following network adapters: • PureData PDI8023-8 • PureData PDI8023-16 • PureData PDuC8023 The following table summarizes the possible entries and values in the [pdieth] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — ioaddress hex.
Chapter 9 Network Device Driver Options 241 PureData Token Ring Adapters Required entry: • drivername = olitok$ or olitokn$ This driver is for the following network adapters: • Intel TokenExpress EISA 16/4 • Intel TokenExpress ISA 16/4 • Intel TokenExpress MCA 16/4 • Olicom 16 bit ISA • PureData PDI9025-16 • PureData PDE9025-32 • PureData PDuC9025 The following table summarizes the possible entries and values in the [omac] section of the PROTOCOL.
242 Installation Guide for Clients maxrequests Specifies the maximum number of outstanding general requests and configures the size of general request queue. maxtransmits Specifies the maximum number of outstanding transmit chain commands. This configures the size of the transmit chain request queue. nodeaddress If specified, this entry will be used in place of the universal burned-in node address on the adapter.
Chapter 9 Network Device Driver Options 243 PureData WaveLAN Adapters Required entry: • drivername = ncrwve$ or ncrwven$ This driver is for the following network adapters: • NCR Systems BV WaveLAN/AT • NCR Systems BV WaveLAN/MC • PureData PDI90211 • PureData PDuC90211 The following table summarizes the possible entries and values in the [wavelan] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default acr drivername decimal — 2 or 6 — iobase hex.
244 Installation Guide for Clients Racal-Datacom ES3210 Required entry: • drivername = es3210$ or es3210n$ The following table summarizes the possible entries and values in the [es3210] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — maxmulticasts maxreceives maxtransmits slotnumber integer integer integer hex. 1–16 1–6 1–50 1–F es3210$ or es3210n$ 10 3 6 See explanation Entries in the [es3210] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 245 Racal-Datacom NI5210 Required entry: • drivername = ni5210$ The following table summarizes the possible entries and values in the [ni5210] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default basemem drivername iobase irq maxmulticasts maxreceives maxtransmits hex. — hex. integer integer integer integer C000–EC00 — 200–3F8 2–7 0–16 1–6 1–50 D0000 ni5210$ 300 2 10 3 6 Entries in the [ni5210] section of the LAN Manager PROTOCOL.
246 Installation Guide for Clients Racal-Datacom NI 6510 Required entry: • drivername = ni6510$ or ni6510n$ The following table summarizes the possible entries and values in the [ni6510] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — iobase maxmulticasts maxreceives maxtransmits hex. integer integer integer 300–360 1–16 1–8 1–50 ni6510$ or ni6510n$ 360 10 4 6 Entries in the [ni6510] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 247 Racal-Datacom NI9210 The NI9210.OS2 driver is not supported on IBM PS/2 model 95 computers. Required entry: • drivername = ni9210$ The following table summarizes the possible entries and values in the [ni9210] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername maxmulticasts maxreceives maxtransmits slot — integer integer integer hex.
248 Installation Guide for Clients Racore Computer Products Required entries: • drivername = rtr16lm$ or rtr16lmn$ • ioaddress=value This driver is for the following network adapters: • Racore M8113 • Racore M8114 • Racore M8115 The following table summarizes the possible entries and values in the [rtr16lm] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — ioaddress maxtransmits netaddress hex. integer hex.
Chapter 9 Network Device Driver Options 249 netaddress Overrides the burned-in-address of the network adapter. This entry is a 12-digit hexadecimal string enclosed in quotation marks, such as "02608C010001". noearlyrelease Specifies that the early token release should be disabled. Early token release reduces the average time another network adapter must wait to transmit a frame. numreceivebuffers Specifies the number of receive buffers to allocate.
250 Installation Guide for Clients RCE France 8- and 16-Bit Required entry for MS-DOS: • drivername = rce_128$ or rce_128n$ Required entry for MS OS/2: • drivername = rce_207$ or rce_207n$ These drivers are for the following network adapters: • RCE MM031 • RCE MM036 The following table summarizes the possible entries and values in the [rce] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — int io_add mem_add mem_size phys (16-bit only) integer hex. hex.
Chapter 9 Network Device Driver Options 251 mem_add Specifies the double-access memory base address. For 8-bit adapters, this value can be D0000 or C8000. For 16-bit adapters, it can be CC000, D0000, D8000, or E0000. mem_size Specifies the size of the double-access memory. In 8-bit adapters, this value should be 8.
252 Installation Guide for Clients Research Machines Ethernet AT-2 Required entry: • drivername = rmateth$ or rmatethn$ The following table summarizes the possible entries and values in the [rmateth] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default adaptoraddress drivername hex. — 300–360 — maxrequests maxtransmits stationaddress integer integer hex. 1–10 1–50 12 hex. digits — rmateth or rmatethn$ 6 6 — Entries in the [rmateth] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 253 Research Machines MCA Ethernet Required entry: • drivername = rmmceth$ or rmmcethn$ The following table summarizes the possible entries and values in the [rmmceth] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default adaptoraddress drivername hex. — 1–8 — maxrequests maxtransmits stationaddress integer integer hex. 1–10 1–50 12 hex. digits — rmmceth or rmmcethn$ 6 6 — Entries in the [rmmceth] section of the LAN Manager PROTOCOL.
254 Installation Guide for Clients Spider Communications SC-100E Required entry: • drivername = spider$ The following table summarizes the possible entries and values in the [spider] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt iobase sramsize — integer hex. integer — 2-7 200-3E0 8-32 spider$ 3 300 8 Entries in the [spider] section of the LAN Manager PROTOCOL.INI file have the following meanings: drivername Identifies the device driver name.
Chapter 9 Network Device Driver Options 255 Standard Microsystems Ethernet 3016 Required entry: • drivername = smc_eth$ The following table summarizes the possible entries and values in the [smc_eth] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt micro_channel port_num xt_type — integer integer hex. integer — 3, 4, 5, 7, 9, 10 0, 1 200-3E0 0, 1 smc_eth$ 3 1 300 1 Entries in the [smc_eth] section of the LAN Manager PROTOCOL.
256 Installation Guide for Clients Standard Microsystems SMC 80x3 Adapters Required entry: • drivername = smcmac$ This driver is for the following network adapters: • SMC 8003EP • SMC 8003EPC • SMC 8013EPC • SMC 8013EWC • SMC 8013WC The following table summarizes the possible entries and values in the [smcmac] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 257 maxrequests Specifies the number or general request queue entries. If this parameter is not defined, the value will default to 8. maxtransmits Specifies the number or transmit queue entries. If this parameter is not defined, the value will default to 12. ramaddress Indicates the base address of the shared memory on the network adapter. receivebuffers Specifies the number of receive queue entries. If this parameter is not defined, the value will default to 12.
258 Installation Guide for Clients Standard Microsystems SMC ARCNET Adapters Required entry: • drivername = smc_arc$ This driver is for the following network adapters: • SMC ARCNET PC130 • SMC ARCNET PC130E • SMC ARCNET PC270E • SMC ARCNET PC550W • SMC ARCNET 600W • SMC ARCNET 600WS The following table summarizes the possible entries and values in the [smc_arc] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 259 i/o_8_bit (PC550W only) Specifies the bit-mode to operate. Set to 0 to operate in 16-bit mode, which is the usual way. Setting this entry to 1 will run the board in 8bit mode. This entry is only used for the PC550W adapter. memorybase Indicates the base I/O address for the network adapter. micro_channel Identifies the system type and displays it at the system startup time on the console.
260 Installation Guide for Clients Thomas Conrad Token Ring Required entry: • drivername = tcctok$ The following table summarizes the possible entries and values in the [tcctok] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default dmachannel drivername interrupt iobase microchannel netaddress packetsize integer — integer hex. — hex.
Chapter 9 Network Device Driver Options 261 netaddress Overrides the network node address of the network adapter. This value is a hexadecimal string of twelve digits and must be enclosed in quotation marks, such as "02608C010001". packetsize Specifies the size, in bytes, of the token-ring packet.
262 Installation Guide for Clients Thomas Conrad Arcnet Adapters Required entry: • drivername = tccarc$ This driver is for the following network adapters: • Thomas Conrad TC3045-CX • Thomas Conrad TC6145 • Thomas Conrad TC6245 The following table summarizes the possible entries and values in the [tccarc] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt memorybase microchannel — integer hex.
Chapter 9 Network Device Driver Options 263 Tiara 10Base-T LanCard/E*AT Required entry: • drivername = tndis$ The following table summarizes the possible entries and values in the [tndis] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt ioaddress maxtransmits slot — integer hex. integer integer — — — — — tndis$ 3 300 8 — Entries in the [tndis] section of the LAN Manager PROTOCOL.
264 Installation Guide for Clients ToshibaLAN Required entry: • drivername = tsbeth$ The following table summarizes the possible entries and values in the [tsbether] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername interrupt — integer tsbeth$ 9 iobase memorybase hex. hex. memorysize — — 3, 4, 5, 7, 9, 10 200–3E0 C8000–E800 0 32, 64 280 D0000 64 Entries in the [tsbether] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 265 Tulip TNCC-16 CAT Required entry: • drivername = ncc16$ The following table summarizes the possible entries and values in the [ncc16] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername — — ncc16$ The entry in the [ncc16] section of the LAN Manager PROTOCOL.INI file has the following meanings: drivername Identifies the driver name of the network device driver.
266 Installation Guide for Clients Ungermann-Bass UBNEI Required entries: • adaptertype = NIUpc, NIUpcPlus, NIUps, PCNIU, or PCNIUex • drivername = ubnei$ or ubnein$ The following table summarizes the possible entries and values in the [ubnei] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default adaptertype drivername io_port irq_level maxmulticast maxrequests maxtransmits memorywindow receivebuffers receivebufsize receivemethod permanentaddr slotnumber — — hex. — — — — hex.
Chapter 9 Network Device Driver Options 267 irq_level Indicates the interrupt level of the network adapter. This entry must match the adapter’s jumper settings. The entry is ignored if adaptertype is NIUps. On XT-class computers, interrupt level 5 is used by the hard disk controller. If you are running the ubnei$ driver on an XT-class computer, you will need to change the irq_level from the default (5) and the jumper setting on the board. maxmulticast Sets the maximum number of multicast addresses.
268 Installation Guide for Clients ReceiveChain, HostBuffered Tells the network device driver to copy frames into a separate buffer in the computer’s memory (not part of the network adapter’s RAM or the protocol driver’s buffer) until the protocol driver can copy them. If you use this option, receivebuffers must contain the number of buffers and receivebufsize must contain the size of each buffer. permanentaddr Overrides the network address of the network adapter.
Chapter 9 Network Device Driver Options 269 Ungermann-Bass UBNEA Required entries: • adaptertype = Access/PC-8, Access/PC-16, or Access/MC • drivername = ubnea$ or ubnean$ This driver supports the following adapters: • Ungermann-Bass Access/PC-8 • Ungermann-Bass Access/PC-16 • Ungermann-Bass Access/MC The following table summarizes the possible entries and values in the [ubnea] section of the LAN Manager PROTOCOL.
270 Installation Guide for Clients io_port Indicates the base I/O address for the network adapter. This entry must match the adapter’s I/O address jumper settings. The entry is ignored if adaptertype is Access/MC. For the Access/PC-8, the 8 possible choices for the I/O port base address are: 0x200, 0x240, 0x280, 0x2C0, 0x300, 0x340, 0x380, 0x3C0.
Chapter 9 Network Device Driver Options 271 receivebufsize If receivemethod is set to ReceiveChain, this entry specifies the size, in bytes, of each receive buffer. This entry must contain an even value. receivemethod Determines the method of received frame delivery the network device driver will use. Which method is best to use depends on (a) which kind of adapter you have, and (b) how the Protocol driver you’re using works.
272 Installation Guide for Clients Ungermann-Bass UBNEPS Required entry: • drivername = ubneps$ or ubnepsn$ The following table summarizes the possible entries and values in the [ubneps] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 273 receivemethod Determines the method of received frame delivery the network device driver will use. Which method is best to use depends mainly on how the protocol driver you’re using works. Use ReceiveLookahead if you don’t know anything about the protocol driver. slotnumber If there is more than one NICps/2 network adapter installed, the PROTOCOL.INI file contains more than one [ubneps] section.
274 Installation Guide for Clients Western Digital EtherCard Plus and EtherCard Plus/A Required entry: • drivername = macwd$ The following table summarizes the possible entries and values in the [macwd] section of the LAN Manager PROTOCOL.INI file: Entry Units Range Default drivername iobase (EtherCard Plus only) irq (EtherCard Plus only) maxrequests maxtransmits ramaddress (EtherCard Plus only) receivebuffers receivebufsize receivechains — hex. — 200–3E0 macwd$ 280 — integer integer hex.
Chapter 9 Network Device Driver Options 275 receivebufsize Specifies the size in bytes of a receive buffer. receivechains Specifies the number of receive chain header queue entries. Note The Western Digital EtherCard Plus may not perform properly if installed on an 80486 computer and subjected to heavy use.
276 Installation Guide for Clients Western Digital TokenCard, TokenCard WS, and TokenCard PLUS16 Required entry: • drivername = tokwd$ This driver is for the following network adapters: • Western Digital TokenCard (WD8005) • Western Digital TokenCard WS (WD8005 WS) • Western Digital TokenCard PLUS16 (WD8015) The following table summarizes the possible entries and values in the [tokwd] section of the LAN Manager PROTOCOL.
Chapter 9 Network Device Driver Options 277 irq Indicates the interrupt level of the network adapter. Not all values are available for all adapters; for information about available interrupt levels, see the manufacturer’s documentation. Value Meaning 2–7 2–7 3, 4, 5, 7, 9, 10, 11, 15 TokenCard: interrupt levels 2–7 TokenCard WS: interrupt levels 2–7 TokenCard PLUS 16: interrupt levels 3, 4, 5, 7, 9, 10, 11, 15 maxrequests Specifies the number of request-queue entries.
278 Installation Guide for Clients Zenith Data Systems Z.Note 325L Notebook PC Required entry: • drivername = i82593$ or i82593n$ This driver is for the following network adapters: • Intel Motherboard Lan Module • Zenith Data Systems Z.Note 325L Notebook PC The following table summarizes the possible entries and values in the [i82593] section of the PROTOCOL.
Chapter 9 Network Device Driver Options 279 inbuffer Indicates the size, in bytes, of the memory to use for a receive buffer. The buffer memory is in host memory, so any increase will reduce the amount of memory available to applications. This value should be 8 for MS-DOS. interrupt Indicates the interrupt level of the network adapter. The interrupt can be any valid ISA interrupt request (IRQ) level. ioaddress Indicates the current I/O address jumper configuration of the network adapter.
280 Installation Guide for Clients Monolithic Drivers The only monolithic driver supplied with LAN Manager 2.2 is a loopback driver, which you use to run LAN Manager without a network adapter. Available only with OS/2, this driver enables a single computer to emulate network operations without actually being connected to a network. It allows network requests to be sent to the local machine as if the machine were remote.
281 C H A P T E R 1 0 Creating Supplemental Drivers Disks The LAN Manager Setup program can install and configure network device drivers that aren’t shipped with the LAN Manager package. These drivers include protocol drivers (also known as protocols or transports) and network adapter drivers (also known as NDI or media access control drivers). The network device drivers to be installed must be on their own supplemental drivers disk, which must have the proper directory structure.
282 Installation Guide for Clients ⇔ To create a supplemental drivers disk 1. Set up the appropriate directory structure on a blank floppy disk. 2. Create a PROTOCOL.INI file for each driver to be added to the supplemental drivers disk. 3. Copy each driver and its associated PROTOCOL.INI file to the appropriate driver subdirectory on the supplemental drivers disk. 4. Create driver information files. 5. Copy driver information files to the supplemental drivers disk.
Chapter 10 Creating Supplemental Drivers Disks 283 The final step in setting up the directory structure on your supplemental drivers disk is to create individual subdirectories for each driver. For example, if the driver supports an Ethernet card, the driver must be copied to the DRIVERS\ETHERNET\drivername subdirectory. (Giving the subdirectory the same name as the driver is recommended.) If you are installing two Ethernet drivers, each must be installed in its own subdirectory.
284 Installation Guide for Clients Creating PROTOCOL.INI Files Each protocol driver and network adapter driver to be included on a supplemental drivers disk must have a corresponding PROTOCOL.INI file that contains configuration data for the driver. During LAN Manager installation, the Setup program combines the PROTOCOL.INI files for individual drivers into a master PROTOCOL.INI file that contains information about all the drivers installed on the computer. Create a PROTOCOL.
Chapter 10 Creating Supplemental Drivers Disks 285 Copying Drivers to the Supplemental Drivers Disk After creating PROTOCOL.INI files for all the drivers to be included on your supplemental drivers disk, copy the drivers and their corresponding PROTOCOL.INI files to the appropriate directories on the disk. Each driver must reside in its own subdirectory, and the path must be specified in a .NIF file for network adapter drivers or in an .XIF file for protocol drivers.
286 Installation Guide for Clients Creating .NIF Files Network information (.NIF) files contain information needed by the Setup program to install and coordinate network adapter drivers. To add a network adapter driver, create a .NIF file in the following format: model = sample driver 1 path = ethernet\sampldrvr devicedriver = smpldrvr.os2 devicename = smpldrvr_i type = ndis xports = netbeui xporta xportb Entries in a .
Chapter 10 Creating Supplemental Drivers Disks 287 type The type of network adapter driver, from the following list: ndis For network adapter drivers that conform to the Microsoft/3Com LAN Manager Network Driver Interface Specification (NDIS). ndis_sngl For NDIS drivers that you load only once in CONFIG.SYS, even if more than one network adapter is installed. mono For monolithic drivers. loop For the loopback driver, which tells the Setup program that there can be no other drivers loaded with this one.
288 Installation Guide for Clients Creating .XIF Files Protocol information (.XIF) files contain information needed by the Setup program to install and coordinate protocol drivers. The information relates only to data-transport protocols and not to particular network adapter drivers. To add a protocol driver, create an .XIF file in the following format: model = netbeui 2.0 path = protocol\netbeui devicedriver = netbeui.os2 devicename = netbeui$ type = ndis_xport class = netbios Entries in an .
Chapter 10 Creating Supplemental Drivers Disks 289 ndis_xport For NDIS-conformant protocol drivers that act as transports (such as TCP/IP). ndis_tsr For terminate-and-stay-resident (TSR) programs that function as protocol drivers. ndis_tcpip For the TCP/IP protocol. ndis_nonb Allows the Basic redirector to have two or more protocols attached to it, the secondary ones being non-NetBIOS protocols (such as IPX or XNSTP). ndis_rpl For RPL-type NDIS transports. ndis For generic protocol drivers.
290 Installation Guide for Clients 2. Copy the .NIF files to the \MSLANMAN.xxx\DRIVERS\NIF directory of the disk, where xxx is either DOS or OS2. For example, if the disk were in the A drive and you were copying .NIF files for use with MS-DOS, you would specify A:\MSLANMAN.DOS\DRIVERS\NIF. 3. Copy the .XIF files to the \MSLANMAN.xxx directory of the disk, where xxx is either DOS or OS2. For example, if the disk were in the A drive and you were copying .
Chapter 10 Creating Supplemental Drivers Disks 291 Examples The following figures show the directory structure of the supplemental drivers disk and the contents of the .NIF files for three common network configurations. MSLANMAN.DOS DRIVERS ETHERNET ELNK ELNK.SYS PROTOCOL.INI NIF ELNK.NIF model path devicedriver type = = = = 300M Etherlink ethernet\elnk elnk.dos ndis A Single driver supporting a single network adapter card MSLANMAN.OS2 DRIVERS ETHERNET MACWD MACWD.OS2 PROTOCOL.INI NIF ECARD.
292 Installation Guide for Clients MSLANMAN.OS2 DRIVERS TOKENRNG TITOK TITOK.OS2 DOWNLOAD.MAC WDTCM PROTOCOL.INI P1347 PROTOCOL.INI P1390 PROTOCOL.INI M8110 PROTOCOL.INI NIF WDTCM.NIF model path devicedriver type ancillary = = = = = WD Token Card Master tokenrng\titok\wdtcm @lanroot\drivers\tokenrng\titok\titok.os2 ndis_sngl @lanroot\drivers\tokenrng\titok\download.mac P1347.
Chapter 10 Creating Supplemental Drivers Disks MSLANMAN.OS2 DRIVERS ETHERNET MONOSTK MONOSTK.OS2 NIF MONOSTK.NIF A monolithic driver model path devicedriver devicename type = = = = = Monolithic Stack for Monodriver ethernet\monostk monostk.
294 Installation Guide for Clients
P A R T 5 Appendixes A B C D E F The LAN Manager Root Directory...............................................297 The LANMAN.INI File ................................................................311 TCP/IP Protocol...........................................................................339 Microsoft Data Link Control Protocol ..........................................349 Using the Network Application Starter .........................................361 Excluding Memory From Windows.................
297 A P P E N D I X A The LAN Manager Root Directory This appendix discusses the files that make up the LAN Manager software. Specifically, it describes the LAN Manager root directory, usually C:\LANMAN or C:\LANMAN.DOS, and its subdirectories. The contents of the LAN Manager root directory differ depending on whether the workstation is running LAN Manager Enhanced, LAN Manager Basic, or LAN Manager for OS/2.
298 Installation Guide for Clients Edits Made by Setup to System Files When you use the Setup program to change a computer’s configuration, Setup updates system files to reflect your changes. In some cases, this process can overwrite changes you had previously made to those files with a text editor. Setup makes these changes whether or not the automatic tuning feature is on. The automatic tuning feature primarily affects how Setup treats values in the LANMAN.INI file.
Appendix A The LAN Manager Root Directory 299 STARTUP.CMD Setup adds a net start workstation command, and adds an exit command at the end of the file. This file is used on OS/2 computers only. PRIVINIT.CMD All lines in this file are affected. When Setup modifies a system file, it first makes a backup copy of the file. You can use this backup file to retrieve the previous version of a system file after it has been modified.
300 Installation Guide for Clients The PROTOCOL.INI File Contains settings for protocols and network adapters. The SETUP.EXE File Starts the LAN Manager Setup program. The SETUP.INF File Contains information required by the Setup program. The SETUP.INI File Contains a history of the configuration settings for the Setup program. Do not edit this file. The SETUP.MSG File Contains messages required by the Setup program. The remainder of this section discusses the contents of the LANMAN.
Appendix A The LAN Manager Root Directory 301 PROTOCOL Contains the protocol device drivers in the directory. The PROTOCOL directory contains subdirectories only for installed transports. TOKENRNG Contains the media access control drivers for any installed token-ring network adapters. XIF Contains the transport-information files (XIF) for the protocol device drivers in the directory. Includes XIF files for protocol device drivers even if they are not installed on this system. The LANMAN.
302 Installation Guide for Clients MINSES.EXE Provides the interface between the workstation software and network drivers. MSD.EXE Contains a Microsoft diagnostics application. MSD.INI Contains the initialization parameters for MSD.EXE. NET.EXE Starts the LAN Manager Screen and processes LAN Manager Enhanced commands. NET.HLP Contains help messages for LAN Manager Enhanced command-line commands. NET.MSG Contains informational messages for LAN Manager Enhanced. NET.
Appendix A The LAN Manager Root Directory 303 NIFU.HLP Contains help messages for the user’s version of the LAN Manager Screen. OSO001.MSG Provides the text of error messages for LAN Manager Enhanced commands. PMSPL.DLL Provides library functions for the LAN Manager Enhanced spooler under Microsoft Windows. PRTSC.EXE Flushes the spooler to print a file within an application. READPRO.EXE Reads PROTOCOL.INI configuration information. UNLOAD.COM Unloads protocols. WINPOPUP.EXE Provides a version of NETPOPUP.
304 Installation Guide for Clients LANMAN.DOS Basic Directory The LANMAN.DOS Basic directory for an MS-DOS workstation includes the following subdirectories and files: The LANMAN.DOS\BASIC Directory Contains the programs that run the LAN Manager Basic services. The LANMAN.DOS\DRIVERS Directory Contains the device drivers and the network-information files for network adapters. This directory is explained in “The LANMAN.DOS\DRIVERS Directory” section, earlier in this appendix. The LANMAN.
Appendix A The LAN Manager Root Directory 305 NET.EXE Processes LAN Manager Basic commands. NET.PIF Provides the program-information file (PIF) for NET.EXE. NETBIND.COM Reads configuration information in PROTOCOL.INI. PRINTQ.EXE Processes print jobs. PRTSC.EXE Flushes the spooler to print a file within an application. REDIR.EXE Starts the workstation software. SETNAME.EXE Sets the computername for the workstation. UNLOAD.COM Unloads protocols. USE.EXE Establishes connections to shared resources. *.
306 Installation Guide for Clients The LANMAN\ SERVICES Directory Contains the programs that run the LAN Manager services. The SETUP.EXE File Contains the LAN Manager Setup program. The SETUP.INF File Contains information required by the Setup program. The SETUP.INI File Contains a history of the configuration settings for the Setup program. You should not edit this file. The SETUP.MSG File Contains messages required by the Setup program. The UPGRADE.
Appendix A The LAN Manager Root Directory 307 NIF Contains the network-information files (NIF) for the media-access control drivers. A NIF\README.TXT file describes the structure of the NIF files. PROTMAN Contains files for managing the protocol device drivers. PROTOCOL Contains the protocol device drivers. TOKENRNG Contains the media access control drivers for the token-ring network adapters, if a token-ring network-adapter is installed.
308 Installation Guide for Clients NETOEM.DLL Provides OEM-replaceable LAN Manager system calls. NETSPOOL.DLL Provides system calls for the LAN Manager spooler. ULAN.DLL Provides support for the workstation file-system driver (FSD). For more information about these programming libraries, see the Microsoft LAN Manager Programmer’s Reference. The LANMAN\NETPROG Directory The LANMAN\NETPROG directory contains the basic LAN Manager programs and commands.
Appendix A The LAN Manager Root Directory 309 NETUSER.EXE Runs the LAN Manager Screen. The net command uses this file; don’t type netuser as a command. NETWKSTA.SYS Contains the device driver for the workstation software. NIFU.HLP Contains help messages for the user’s version of the LAN Manager Screen. The net command uses NIFU.HLP. PRO.MSG Contains Protocol Manager messages. PROH.MSG Contains help for Protocol Manager messages. RDRHELP.
310 Installation Guide for Clients
311 A P P E N D I X B The LANMAN.INI File The LANMAN.INI file is the initialization file for LAN Manager workstations. This file determines the option settings for your computer. LAN Manager comes with a default LANMAN.INI file that is modified during setup to make your computer unique on the network. After your computer has LAN Manager installed, you can change the values in the LANMAN.INI file to serve the particular needs of your computer or domain. To see the default LANMAN.
312 Installation Guide for Clients How to Override Values The Control services command, from the Config menu on the LAN Manager Screen, and the net start command-line command have options that correspond to entries in the LANMAN.INI file. When starting a service, you can override values in the LANMAN.INI file by changing the corresponding option values of the Control services command or the net start command.
Appendix B The LANMAN.INI File 313 Why You Change Values Consider values for entries in the LANMAN.INI file to be in the following three categories: • Values you must supply to start the Workstation service You must supply a value for the network device driver net1 in the [networks] section of the LANMAN.INI file, and you must supply the name of the computer (computername) and the name of the workstation’s domain (domain) in the [workstation] section. The Setup program prompts for these values.
314 Installation Guide for Clients pathname When the value for an entry is a path, a relative path is assumed to be relative to the LAN Manager root directory (usually LANMAN.DOS or LANMAN) or an appropriate subdirectory of the LAN Manager root directory. See the descriptions of individual entries for specific directories for information about their relative paths.
Appendix B The LANMAN.INI File 315 The [networks] Section for MS-DOS The [networks] section of the LANMAN.INI file for MS-DOS contains only one entry, netservices, with the following list of services: • chknet (checks to see that the network has been installed) • minses (provides the interface between LAN Manager for MS-DOS and NetBIOS) • netbind (optional; binds together a transport driver such as NETBEUI.EXE and a media access control driver such as IBMTOK.
316 Installation Guide for Clients Entries in the [networks] section have the format netn=devicename$,ln,type,sess,ncb,name where netn= Sets the name of a network and a number for the network-adapter. The number (n) in each netn entry has no ordering effect; it is only a means of identifying a given network in later LANMAN.INI entries. This number is usually 1 because typically a workstation is connected to one network. Put each entry on a separate line.
Appendix B The LANMAN.INI File 317 The [workstation] Section The [workstation] section of the LANMAN.INI file configures the Workstation service. For the purpose of discussion, the entries in this section are divided into two types. The first type is default entries, which are included automatically in the file. The second type is optional entries, which can be added to the file or included as command options when starting the Workstation service using the net start commands.
318 Installation Guide for Clients othdomains Provides the names of additional domains to be shown in LAN Manager displays. The range is 0–4 names. Separate multiple name entries with commas. A domain name can have 1–15 characters, including letters, numbers, and the following symbols: !#$%&()-.@^_' {}~ wrkservices Lists the LAN Manager services to start along with the Workstation service. The names of all the services are listed in the [services] section.
Appendix B The LANMAN.INI File 319 charwait Sets the number of seconds that the workstation waits for a requested communication device (such as a modem) or named pipe to become available. Increase this number for heavy traffic on the network or heavy use of shared communication devices if you are willing to wait for shared devices. The range is 0–65535 seconds; the default is 128 seconds for MS-DOS or 3600 seconds for OS/2.
320 Installation Guide for Clients maxthreads Sets the maximum number of execution threads that can use the network by means of the Workstation service. Increase this number if you simultaneously run multiple applications that use LAN Manager. The range is 10–254 threads; the default is 10 threads. maxwrkcache (OS/2 only) Sets the maximum number of kilobytes for the workstation’s largetransfer buffers. Increase this number for better performance on fileintensive tasks like copying large files.
Appendix B The LANMAN.INI File 321 The default value for numdgrambuf assumes that the workstation will be using only one domain. You can use additional domains by specifying other domains through Setup, or with the othdomains entry in the LANMAN.INI file, or with the /othdom = switch to the net start workstation command. In these cases, the value for numdgrambuf must be 3 + the number of other domains.
322 Installation Guide for Clients sesstimeout Sets the number of seconds that the workstation waits before disconnecting a session with a server that is no longer responding. Note that sesstimeout does not affect the timeout periods of sessions using the MS TCP/IP protocol. Because MS TCP/IP is a WAN protocol, it requires a longer period before timeouts to ensure robust, reliable packet-delivery through all the slow-links, gateways, etc., in the Wide Area Network.
Appendix B The LANMAN.INI File 323 wrkheuristics (MS-DOS only) This set of digits configures the way an MS-DOS workstation processes network information. Digits read from left (0) to right (32). Except as noted, a digit value of 0 means “off” or “inactive,” 1 means “on” or “active,” and X sets the digit to the default value, allowing you to set specific digits without knowing the settings of all digits.
324 Installation Guide for Clients 9 Use Open and Read. 0 = no Open and Read 1 = Open and Read on files with R (Read) and W (Write) access 2 = Open and Read on files with R (Read), W (Write), and X (Execute) access The default is 2. 10 Controls network realization of MS-DOS commit calls as follows: 0 = flush dirty buffers to server and wait for server to flush buffers to hard disk 1 = flush dirty buffers to server but do not wait 2 = flush buffer when full or when job is done The default is 1.
Appendix B The LANMAN.INI File 325 wrkheuristics (OS/2 only) This set of digits configures the way the workstation processes network information. Digits read from left (0) to right (54). Except as noted, a digit value of 0 means “off” or “inactive,” 1 means “on” or “active,” and X sets the digit to the default value, allowing you to set specific digits without knowing the settings of all digits.
326 Installation Guide for Clients 5 LockRead and WriteUnlock as follows: 0 = never 1 = always 2 = only on a LAN Manager VC The default is 1. The following diagrams illustrate this option for a database.
Appendix B The LANMAN.INI File 7 8 9 10 11 12 13 14 15 16 17 327 Read-ahead to sector boundary. Reading ahead to a sector boundary creates better performance in a file system that is not sensitive to the location of information or the reading of partial sectors on a disk or one that has an active cache. The default is 1. Use the “chain send” NetBIOS NCB as follows: 0 = never 1 = only if the server’s buffer is larger than the workstation buffer 2 = always (to avoid copy) The default is 2.
328 Installation Guide for Clients 18 19 20 21 22 Set the write-behind size as follows: 0 = write to sector boundary 1 = use a multiple of the size that the user is writing The default is 1. Force 512-byte maximum transfers to and from core servers. On some systems, core servers, or servers with the same base SMB protocols as LAN Manager, could handle a maximum of 512-byte buffers. Set this bit only if your network has this type of server and your workstation accesses the server. The default is 0.
Appendix B The LANMAN.INI File 23 24 25 26 27 28 29 30 32 33 329 Buffer all files opened with “deny write” rights. The default is 1. Buffer all files opened with the R (read only) attribute. The default is 1. Read ahead when opening a file for execution. (Sometimes reading an executable file appears sequential when it is not.) The default is 1. Handle CTRL+C as follows: 0 = do not allow interrupts 1 = allow interrupts only on long-term operations 2 = always allow interrupts The default is 2.
330 Installation Guide for Clients 34 Allows compatibility with core level PCLP servers. Some PCLP servers send the date in word reversed order on the SMBgetatr response. The heuristic controls how the workstation will handle SMBgetatr dates from core level servers on the network: 0 - Verify date with preference towards PCLP server. 1 - Verify date with preference towards SMB specification. 2 - Assume date is supplied as specified in SMB specification. The default is 1. 35–54 Reserved.
Appendix B The LANMAN.INI File 331 nummsgnames (MS-DOS only) Sets the maximum number of aliases you can add on the workstation. The range is 1–10 aliases; the default is 2 aliases. sizmessbuf Sets the number of bytes for the buffer that holds network messages. Increase this number to send or receive longer messages. For MS-DOS, the range is 128–62000 bytes; the default is 256 bytes. For OS/2, the range is 512–62000 bytes; the default is 4096 bytes.
332 Installation Guide for Clients The [loadopts] Section (MS-DOS Only) The [loadopts] section allows you to select how LAN Manager Enhanced services are loaded into memory. By default, the services you specify in the [services] section are loaded into upper memory blocks (umbs) as available. In the [loadopts] section, you can set each service to load either low or umb. The format is: service = {low | umb} The [services] Section The [services] section of the LANMAN.
Appendix B The LANMAN.INI File 333 Sample LANMAN.INI File This section provides a sample file for a LAN Manager Enhanced workstation. An MS-DOS workstation running LAN Manager Basic has a LANMAN.INI file, but it is very different from the files for OS/2 workstations and MS-DOS workstations running LAN Manager Enhanced. For an MS-DOS workstation running LAN Manager Basic, the LANMAN.INI file is a simple command file. An example of this file is included with the examples that follow. LANMAN.
334 Installation Guide for Clients LANMAN.INI File for LAN Manager Basic The following is a sample LANMAN.INI file for a workstation running LAN Manager Basic. ; LM 2.2 ;********************************************************* ********; ;** Microsoft LAN Manager **; ;** Copyright(c) Microsoft Corp., 1991 **; ;********************************************************* ********; help use use help command.com /c type $Puse.hlp version command.com /c echo Microsoft LAN Manager 2.2.
Appendix B The LANMAN.INI File 335 start workstation /umb:no $1 start redirector $1 start wksta $1 start rdr $1 chknet minses redir /L:9 /S:9 setname $1 Although the LANMAN.INI files for OS/2 workstations and LAN Manager Enhanced workstations set a number of parameters, the LANMAN.INI file for LAN Manager Basic workstations is much simpler. It consists of command scripts used by NET.EXE to implement the net commands.
336 Installation Guide for Clients Summary Tables The summary tables provide the range and default values for default, optional, and autotuned entries in the LANMAN.INI file. See the descriptions of entries earlier in this appendix for more information. A value of 65535 for an entry means “forever” or “no limit.” Some entries can also have a value of –1. The –1 value is noted in the discussion of entries that can have this value; it usually has an effect similar to 65535, of removing a limit.
Appendix B The LANMAN.
338 Installation Guide for Clients The [messenger] Section Default entry Units Range/value logfile nummsgnames1 sizmessbuf pathname integer bytes — 1–10 128–62000 {512–62000} Default value MESSAGES.LOG 2 256 {4096} Braces ({ }) indicate defaults or ranges that are different for OS/2. 1The entry is only for an MS-DOS LANMAN.INI file.
339 A P P E N D I X C TCP/IP Protocol This appendix describes how computers are identified on a TCP/IP network and how computernames are matched with IP (internet protocol) addresses. Note For information about installing TCP/IP, see the documentation provided with the protocol stack.
340 Installation Guide for Clients The first three fields (w, x and, y) represent a range of possible numbers from 000 through 255. The fourth field (z) represents a range of possible numbers from 1 through 254. Every IP address has two parts: the network number, and the node number. • The network number identifies which network a computer is on. All computers on a given network must have the same network number. • The node number identifies a computer within a network (also called a node).
Appendix C TCP/IP Protocol 341 The following table summarizes the IP addressing scheme. IP Address Criteria Criteria IP address Class A IP address Class B IP address Class C Maximum number of networks Maximum number of computers per network Network number part 127 16,777,214 16,384 65,534 2,097,152 254 First field Network number range 001–127 Node number part Last three fields 000.000.001 – 255.255.254 255.0.0.0 First two fields 128.000– 191.255 Last two fields 000.001– 255.
342 Installation Guide for Clients Matching LAN Manager Server Names to IP Addresses When you use Microsoft TCP/IP with Windows NT or LAN Manager, server names are automatically matched to their corresponding IP addresses on a local network. To match server names across remote networks that are connected by routers (also called gateways in TCP/IP terminology), LAN Manager workstations use the LMHOSTS file. (A router or bridge is a piece of network hardware that connects networks.
Appendix C TCP/IP Protocol 343 When you use an LMHOSTS file, be sure to keep it up to date and organized following these guidelines: • Update an LMHOSTS file whenever a computer is changed, added to, or removed from the network. • Because LMHOSTS files are searched one line at a time from the beginning, list remote computers in priority order, with the ones used most often at the top of the file. This increases the speed of searches for the most often used LMHOSTS entries.
344 Installation Guide for Clients Tuning Microsoft TCP/IP When you tune a computer, you make tradeoffs between the speed of its operation and the amount of memory it uses. For example, making a computer operate faster requires more and larger buffers, and more processes working within the computer. These buffers and processes, however, require more memory. Most computers running Microsoft TCP/IP can be fine-tuned to run more efficiently. You do this by changing entries and values in the PROTOCOL.
Appendix C TCP/IP Protocol 345 ⇔ To make the network run faster or use less memory 1. Be sure Microsoft TCP/IP is properly installed on the computer being tuned. 2. Make a backup copy of the PROTOCOL.INI file. 3. Edit PROTOCOL.INI on the computer to be tuned. Change the values for one or more of the following entries, depending on what you want to accomplish: Note If you are using a 3C501 adapter (also known as an Etherlink adapter), we recommend that you set tcpwindowsize and tcpsegmentsize to 1024.
346 Installation Guide for Clients Adjusting Timing and Retry Parameters for Microsoft TCP/IP In some cases, you may want to adjust the timing and retry parameters used by the Microsoft TCP/IP protocol. For example, if an MS-DOS workstation is not using the messaging service, each print job it sends via Microsoft TCP/IP could result in a lengthy broadcast stream as the server tries to send a job completed message.
Appendix C TCP/IP Protocol 347 The [sockets] section of TCPUTILS.INI has the following entries and values: Entry Value drivername= The SOCKETS driver name. This is a required entry, and the value must be SOCKETS$. The maximum number of sockets to be supported. The range is 1 through 31; the default is 4. The buffer size (in bytes) used by the sockets driver for nonblocking send calls. The entry is set when the system is initialized. The range is 3200 through 28800 bytes; the default is 3200.
348 Installation Guide for Clients Running Microsoft TCP/IP Concurrently With Other Protocols If you encounter problems running Microsoft TCP/IP concurrently with other protocols, try changing the order in which the protocols are loaded. The best way to do this is by using the Setup program, as described in Chapter 9, “Network Device Driver Options.” Remove protocols and then replace them one at a time in the order you want them to load, returning to the Network Drivers dialog box after each addition.
349 A P P E N D I X D Microsoft Data Link Control Protocol In relation to the OSI model, the Microsoft Data Link Control (DLC) protocol provides a data link layer interface to the network. The data link layer is responsible for point-to-point transmission of data.
350 Installation Guide for Clients Terminal emulation applications call Microsoft DLC with the Int 0x5C (NetBIOS) interrupt vector. Microsoft DLC communicates only through the terminal emulation applications; it does not communicate with user applications directly, nor does it use LAN Manager to communicate with the network. It has no NetBIOS interface. However, you can load and unload Microsoft DLC in the same fashion as other NDIS protocols, and Microsoft DLC can co-exist with other protocols.
Appendix D Microsoft Data Link Control Protocol 351 Installing the Microsoft DLC Protocol Use the LAN Manager Setup program to install the Microsoft DLC protocol driver. To install the Microsoft DLC protocol driver 1. Start the LAN Manager Setup program. 2. From the Configuration menu select Network Drivers. The Workstation Configuration dialog box appears. 3. Select the network adapter driver to which you want to bind the Microsoft DLC protocol. Choose the Add/Remove Protocols button.
352 Installation Guide for Clients PROTOCOL.INI Options The following table summarizes the possible entries and values in the [msdlc_xif] section of the LAN Manager PROTOCOL.INI file. Required PROTOCOL.INI entries are drivername, bindings, load, and unload.
Appendix D Microsoft Data Link Control Protocol Entry Units Range Default unload — — usedix (Ethernet only) windowerrors xsaps0 xsaps1 xstations0 xstations1 — 0–1 msdlc[u] (required) 0 errors — — — — 0–10 0-127 0-127 0-127 0-127 0 0 0 0 0 353 Entries in the [msdlc_xif] section of the LAN Manager PROTOCOL.INI file have the following meanings: adaptrate Specifies the time in milliseconds between runs of the adaptive window algorithm.
354 Installation Guide for Clients denysaps Specifies a list of SAP values that may not be opened on the driver. The NetBIOS SAP (0xF0) is denied by default. To allow the NetBIOS SAP, set no value for denysaps. msdlcretries Specifies the number of transmission retries that Microsoft DLC makes before assuming that the receiver’s Microsoft DLC layer is not responding. You can lower the value of this entry on a highly reliable network, where few packets are dropped.
Appendix D Microsoft Data Link Control Protocol 355 maxmember Specifies the maximum number of SAPs that may belong to each Group SAP. The default values for maxgroup and maxmember are zero because most applications do not use Group SAPs. Increase these values if your applications use Group SAPs. maxout Specifies the number of packets to send before expecting an acknowledgment. This number is often called the send window.
356 Installation Guide for Clients If you don’t know the number of SAPs and stations your application requires, and you want to minimize the memory usage of your terminal emulation applications, start with large values and gradually reduce them until the application no longer works. The default is set to saps=3 and stations=20. This is more than enough for most Microsoft DLC applications. Unused SAPs and stations are harmless except that they consume memory.
Appendix D Microsoft Data Link Control Protocol 357 When the number is in the range of 6–10 units of milliseconds, the actual timer value is: (number selected 5) * (long-tick value) * 40 milliseconds Some network application programs adjust these timer entries automatically. The dlc.open.adapter command can override the default value. t1_tick_two Sets the retransmission-timer “long tick” value in units of 40 milliseconds.
358 Installation Guide for Clients trxbufsize Specifies the size of internal transmit and receive buffers. Increasing this value is required only when running applications that use Group SAPs or that issue transmits containing more buffers than the media access control driver can accept in one transfer call. uipackets Specifies the number of data descriptors to allocate for sending UIframes. unload Specifies how to unload Microsoft DLC from memory. This value should not be changed.
Appendix D Microsoft Data Link Control Protocol 359 Sample Configuration Files Sample configuration files are included with the Microsoft DLC files on your LAN Manager client disks. A readme file in the same directory explains the uses of the various sample files.
360 Installation Guide for Clients
361 A P P E N D I X E Using the Network Application Starter LAN Manager provides a means for you to administer and monitor use of Windows-based and non-Windows-based applications that are designed to run with MS-DOS.
362 Installation Guide for Clients One way to implement appstart is to set up a share on a server that contains a particular application, such as a word processor, and limit the number of users to that share to the number of users that your sitelicense has for the application.
Appendix E Using the Network Application Starter 363 The Appstart Command Line The command line in the Program Item Properties dialog box for the appstart utility is of this form: appstart [alias [parms...] | [/s:~:\path\to\start] [/p:#] [drive:|UNC] [\\server]\share\subdir\for\program.exe [parm1 parm2 parm3] Command line parameters are defined as follows: alias [parms...] The alias represents a name of a section in the APPSTART.INI file from which the command line is to be taken.
364 Installation Guide for Clients drive:|UNC An optional specification of the drive letter to use, where drive: is a drive letter designation. If this value is not specified, appstart will select a drive letter that is not in use. If this parameter is UNC in all caps, a UNC name will be used and no drive letter will be used. Note If you don’t specify a drive letter, appstart can’t change the path for the executable, which may cause some programs to be unable to access their data files or DLLs.
Appendix E Using the Network Application Starter 365 [Windows_Spreadsheet_Program] 1=\share1\spread\sprdsht.exe 2=UNC \\server1\winsprd\sprdsht.exe coolspread.dat 3=/s:z:\data z: \share2\maria\sales\sprdsht.exe Case is not significant in section names. [servers] Each line in the optional [servers] section has an entry describing a list of servers that support the named share. Each server should be separated by a comma or a space.
366 Installation Guide for Clients ExitWindows Specifies whether appstart should allow the user to exit the Windows operating system without first exiting appstart-launched applications. If this value is 1, appstart will let the user exit the Windows operating system, and it will attempt to clean up any used resources on the exit. If this value is 0, appstart will not let the user exit until all appstart-started applications have been exited.
Appendix E Using the Network Application Starter 367 APPSTART.INI Example The following example APPSTART.INI file shows how to set up servers, options, application aliases, and a centralized logging file: [servers] apps=production,database,mrkting [options] LogFile=\\bigguy\c$\lanman\logs\appstart.log UserMsgVerbose=0 LogMsgVerbose=1 LogMultiple=1 ExitWindows=0 ChangePath=0 [notepad] 1=\\bigguy\win31$\notepad.exe 2=UNC \\bigguy\win31$\notepad.exe [dos_word] 1=x: \\production\apps\word5.5\word.
368 Installation Guide for Clients Managing a Central APPSTART.INI Appstart can be set up so that there is one common APPSTART.INI file that all users can share. To use this feature, each user must have an environment variable APPSTART.INI (in AUTOEXEC.BAT) set to the literal path to the APPSTART.INI file. This can be a UNC path. For example: set APPSTART.INI=\\bigserver\appstart\subdept1\APPSTART.
369 A P P E N D I X F Excluding Memory From Windows When you install LAN Manager on an MS-DOS computer running Microsoft Windows version 3.0 or above, the Setup program modifies the configuration files for correct operation. However, if your computer has a network adapter that uses shared random access memory (RAM), you must manually modify SYSTEM.INI, the Windows configuration file. When you modify SYSTEM.INI, you must exclude the shared RAM memory area from use by the Windows program.
370 Installation Guide for Clients Excluding a Segment of Memory This section explains how to exclude a segment of memory from use by the Windows operating system. Specific information about which segments of memory to exclude for each adapter follows this section. ⇔ To exclude a segment of memory from use by Microsoft Windows 1.
Appendix F Excluding Memory From Windows 371 Western Digital EtherCard Plus and EtherCard Plus/A The Western Digital EtherCard Plus and EtherCard Plus/A have a segment of shared RAM that must be excluded from use by Microsoft Windows. The starting address of this segment is the shared RAM address; the size of the segment is the shared RAM buffer size. The shared RAM address for these network adapters is configured by a line in the PROTOCOL.INI file. Edit the PROTOCOL.
372 Installation Guide for Clients The starting address of the shared RAM segment used by these network adapters is configured by a line in the PROTOCOL.INI file. Edit the PROTOCOL.INI file, and find the block of lines that start with the comment “IBM Token Ring” and include a line like DRIVERNAME=IBMTOK$ or DRIVERNAME=IBMTOK2$. Look for the keyword RAM. The value after RAM is the starting address of shared RAM for this network adapter. The following is an example of the lines in a PROTOCOL.
Appendix F Excluding Memory From Windows 373 3Com EtherLink II (3C503) and EtherLink 16 (3C507) Network Adapters The 3Com EtherLink II (3C503) and EtherLink 16 (3C507) network adapters have a segment of shared RAM that must be excluded from use by Microsoft Windows. The starting address of this segment is the shared RAM address; the size of the segment is the shared RAM buffer size.
374 Installation Guide for Clients
375 Glossary A ASCII file A standard text file. absolute path A pathname whose reference to a file or directory does not depend on the current drive or directory. An absolute path for MS-DOS or OS/2 must start with a drive letter, a colon, and a backslash (\). Use the format n:\directory [ [\subdirectory][\filename]...]. See also network path, path, pathname, relative path. B basic workstation See LAN Manager Basic. batch file See batch program.
376 choose choose To pick an item that begins an action. configuration The way a computer, server, or You often choose a command on a menu to perform a task, and you choose an icon to start an application. local area network is set up, including both hardware and software. LAN Manager software configuration is stored in the LANMAN.INI and PROTOCOL.INI files. click To position the mouse pointer on a screen element, and then press and release the left mouse button. See also double-click.
driver name 377 device driver Software that enables a computer domain In LAN Manager or Windows NT to recognize and use a specific piece of hardware (device). Advanced Server, a group of devices, servers, and workstations grouped together to simplify network administration and security. Each domain has a unique name. Being logged on in one domain does not limit access to resources in other domains to which you have access.
378 EMS memory E EMS memory A type of expanded memory available on systems that conform to the Lotus/Intel/Microsoft Expanded Memory Specification (LIM EMS). Enhanced workstation See LAN Manager Enhanced. expanded memory Usable memory beyond the conventional memory limit of 640K for MS-DOS. MS-DOS applications that correspond to the Lotus/Intel/Microsoft (LIM) expanded memory specification can use expanded memory. The EMM386.EXE device driver accesses expanded memory.
LAN Manager Screen 379 IP address class A category of IP addresses I IFS See installable file system (IFS). that is determined by the number of nodes on that portion of the internet. There are three classes: A, B, and C. See also IP address. installable file system (IFS) With OS/2, file K systems that can be installed in addition to the existing FAT file system. The LAN Manager redirector software is an IFS for OS/2. keyword An item in the LANMAN.INI file.
380 LAN Manager Setup screen LAN Manager Setup screen The LAN Manager Setup program’s menu-oriented interface used for workstation configuration tasks. This screen is available only from computers that already have LAN Manager software installed. LANA number See local area network adapter (LANA) number. LANMAN.INI The LAN Manager initialization file.
Netrun service loopback driver A monolithic driver that allows a computer with no network adapter to run LAN Manager for testing purposes. M 381 MS-DOS Microsoft Disk Operating System. The operating system that supports some LAN Manager workstations. See also operating system. media access control driver A local area N network device driver that works directly with the network adapters, acting as an intermediary between the protocol driver and the hardware.
382 network adapter network adapter A printed circuit board, installed in a computer, that enables the computer to run LAN Manager software and join the local area network. node name The unique portion of the computername for those computers that are also identified by a TCP/IP domain. See also TCP/IP domain. network adapter driver A network device driver that controls the physical function of a network adapter. See also network adapter, network device driver, protocol driver.
protocol stack OS/2 workstation See LAN Manager OS/2 workstation. other domains Domains other than the logon and workstation domains of which your workstation is a member. See also domain, logon domain, workstation domain. 383 persistent connections The LAN Manager feature that automatically restores network connections at logon. By default, the connections that were in effect at last logoff are restored. Users can also save a particular set of connections, which will be restored at each logon.
384 PROTOCOL.INI protocol driver plus a media access control driver. See also media access control driver, monolithic driver, protocol driver. PROTOCOL.INI The Protocol Manager initialization file. This file, along with CONFIG.SYS and LANMAN.INI, controls the configuration of LAN Manager network device drivers. This file describes all protocol and network adapter drivers and defines how to bind them together. See also CONFIG.SYS, LANMAN.INI. R remote computer See remote.
subdirectory receives a copy of the domain’s security policy and domain database, and authenticates network logons. See also domain controller. share name A name that identifies a shared server role The role assigned to a can connect to. LAN Manager server that determines how the Netlogon service works on the server. The server role can be primary domain controller, backup domain controller, member server, or standalone server. See also Net Logon service, primary domain controller, standalone server.
386 subnet mask subnet mask A series of bits used to identify the subnet number portion of an IP address. See also IP address. system configuration file See CONFIG.SYS. T TCP/IP (transmission control protocol/internet protocol) A protocol that enables workstations and servers to connect to other computers on the internet. TCP/IP was originally developed by DARPA, the U.S. Defense Department’s Advanced Research Projects Agency. See also protocol. TCP/IP domain Different areas of the Internet.
Workstation service 387 user accounts database The NET.ACC file stored in the LANMAN\ACCOUNTS directory. This file contains the user accounts and groups that have been established. See also group, user account. workstation A computer from which a person uses word processing, spreadsheet, database, and other types of applications to accomplish work, taking advantage of resources shared on the local area network. user-level security A type of security in which a user account is set up for each user.
388 Workstation service
389 Index A Absolute path 375 Accton Technology EtherCoax - 16N device drivers 158 Acknowledgment(s), setting 135 ACLAPI.DLL 307 acr entry 219, 243 ACSNETB.DLL 307 adapter entry 229 – 230 adapterslot entry 185, 189 adaptertype entry 266, 269 Adaptive window algorithm 134, 139, 353 adaptoraddress entry 252 – 253 adaptrate entry 133, 134, 352 – 355 Add New Config command 65 ADD.
390 Index CCB descriptors 353 Centralized logging 362 ChangePath parameter (APPSTART.INI) 366 charcount entry (LANMAN.INI) 318 chartime entry (LANMAN.INI) 318 charwait entry (LANMAN.INI) 319 chknet 315 CHKNET.EXE 301, 304 class entry 289, 117, 118 Class1timeout entry 352, 353 Client 376 COM devicename 47 COM0x.SYS device driver 47 Command scripts, in LANMAN.INI file 335 Command(s) call 39, 47 dlc.open.adapter 357 dlc.open.
Index Directories appstart starting 363 Basic 304 – 305 DRIVERS 283, 300, 304, 306, 307 Enhanced 299 – 303 ETHERNET 283 home 378 NIF 283 PROTOCOL 283 setting up 282 TOKENRNG 283 Workstation 305 – 309 XIF 283 Disk(s), storage space requirements 10 DISK01.SYS 99 DISK02.
392 Index Driver(s) 3Com EtherLink 120 – 128, 145 3Com EtherLink 16 151 3Com EtherLink II 147 3Com EtherLink Plus 152 3Com EtherLink/MC 154 3Com EtherLink/MC32 155 3Com TokenLink 156 Accton Technology EtherCoax - 16N 158 AMD AM2100 159 Amplicard AC 210/AT 160 Amplicard AC 210/XT 161 Cabletron E2010-X 162 Cabletron E2112 163 Cabletron E3010-X 164 Cabletron E3112-X 165 Cabletron T2015 166 Cabletron T3015 168 Compaq 32-Bit DualSpeed Token Ring 170 Compaq NE3200 172 Compex ENET16/U 174 DCA 10 megabit 175 DCA
Index drivername entry (Continued) enet section 174 es3210 section 244 ethiie section 201 ethne section 158 exp16 section 202 hls6130 section 193 hplan section 185 hplanb section 187 hplane section 189 hplanp section 191 i82593 section 205, 278 ibmnet section 198 ibmneta section 199 ibmtok section 194 – 195 irmatr section 177 – 178 mac586 section 175 macevx section 184 macwd section 274 madge section 209 – 210 msarc section 238 msdlc_xif section 352 – 354 ncc16 section 265 ncrslan section 215 ncrtrn sectio
394 Index Enhanced workstations configuration(s) examples 120 – 129 network device drivers 58, 64 – 70 options 20 requirements 20 workstation settings 71 – 75 installing 21 memory management 26, 28 search path 40 system requirements 10 Error message log 365 ERRPOPUP.EXE 308 es3210 section 244 EtherCard Plus/A 371 EtherLink 16 network adapters 373 ETHERNET 300, 306 Ethernet DIX 2.
Index Installing (Continued) drivers 109 Enhanced workstations fundamental decisions 21 mouse driver 40 – 41 planning for 20 – 21, 24 – 25, 29 procedure 38 LAN Manager workstations during/after OS/2 installation 46 – 47 on MS-DOS computers 21 – 28 on OS/2 computers 29 – 34 prerequisites 11 Mouse driver 40 – 41 MS-DOS workstations after installation is complete 39 Connectivity Services 75 Custom Install 39 from disk 38 overview 37 procedure 38 OS/2 workstations 46 – 47, 95 TCP/IP protocol 339 – 343 Int 0x5C
396 Index smcmac section 256 spider section 254 tcctok section 260 tokwd section 276 tsbether section 264 wave_nif section 219 wavelan section 243 IP address address class 340 configuration 339 defined 23, 339 matching to LAN Manager server names 342 obtaining 341 parameter 31 partioning of 340 ipackets entry 352, 354 IPC 379 IRMA Workstation application 350 irmatr section 177 – 178 IRQ 379 irq entry ethne section 158 macwd section 274 ni5210 section 245 smcmac section 256 tokwd section 276, 277 irq_level
Index LOOPDRV.OS2 280 Looppackets entry 133, 135, 352, 354 LPT devicename 47 M mac586 section 175 – 176 macwd section 274 – 275 Madge network adapters 140 Madge Networks Smart 16/4 adapters 209 MAILSLOT.DLL 307 Managing memory 26 – 27, 28 max_xmt_size entry 217 maxcmds entry (LANMAN.INI) 319 maxerrorlog entry (MS OS/2 only) (LANMAN.
398 Index olitok section 207 – 208 omac section 229 – 230, 241 – 242 proteon section 234 – 235 rmateth section 252 rmmceth section 253 rtr16lm section 248 smcmac section 256 – 257 t20ndis section 166 – 167 t30ndis section 168 tlnk section 156 – 157 tndis section 263 tokwd section 276 – 277 ubnea section 269 – 270 ubnei section 266 – 267 ubneps section 272 maxwrkcache entry (MS OS/2 only) (LANMAN.
Index running LAN Manager with 25 SETUP.INF file 43 MINIPOP.EXE 303 minses 315 MINSES.EXE 302, 305 mintransmits entry 133, 136 model entry 286, 288, 115 Monolithic drivers and Protocol Manager driver 110 defined 31, 61, 80, 105, 381 LAN Manager 280 name in net line 114 overview 114 Protocol Manager 107 Mouse driver, installing 40 – 41 MS-DLC protocol bound to Ethernet driver 356 driver 351 drivername 354 implementation 349 – 350 installing 351 internal stack size 355 loading 350 PROTOCOL.
400 Index netaddress entry at_lm section 222 – 223 cpqtok section 170 – 171, 236 – 237 eisa_lm section 220 – 221 elmc32 section 155 elnk section 145 – 146 elnk16 section 151 elnk3 section 150 elnkii section 147 – 149 elnkmc section 154 elnkpl section 152 – 153 ethiie section 201 ibmtok section 194 – 195 irmatr section 177 – 178 ne3200 section 172 – 173, 203 – 204, 227 – 228 proteon section 234 – 235 rtr16lm section 248 – 249 tcctok section 260 – 261 tlnk section 156 – 157 NETAPI.
Index networks section of LANMAN.INI file 315 – 316 Networks, multiple 107, 114 Networth EtherneXt 16-bit UTP 140, 224 NETxxx.MSG 308 ni5210 section 245 ni6510 section 246 ni9210 section 247 NIF 115 – 117, 286 NIFU.
402 Index port_num entry 255 Presentation Manager 98 Primary (Token-Ring) network adapter 195 – 196 primary entry 194 – 195 Print jobs, fragmented 318 printbuftime entry 321 PRINTQ.EXE 305 Privilege levels 375, 382 PRIVINIT.CMD 299 PRO.MSG 309 pro4 section 232 – 233 Processor requirements 10, 20 product_id entry cpqtok section 170 – 171, 236 – 237 ibmtok section 194 – 195 ncrtrn section 217 – 218 tlnk section 156 – 157 Program Item Properties dialog box 363 Program(s), batch 375 PROH.
Index rmateth section 252 PROTOCOL.
404 Index receivemethod entry 266 – 267, 269, 271 – 273, 272 Receiver windows 138 recvbufcount entry 177 – 178 recvbufs entry 155, 194, 196 recvbufsize entry 177 – 178, 194, 196 REDIR.EXE 305 Redirector 111, 384 REDIRS directory 304 refresh entry (MS OS/2 only) (LANMAN.
Index slotnumber entry elmc32 section 155 elnkmc section 154 es3210 section 244 smcmac section 256, 257 ubnea section 269, 271 ubnei section 266, 268 ubneps section 272, 273 Sonic EISA 214 Spider Communications SC-100E 140, 254 spider section 254 sramsize entry 254 stacksize entry 133, 138, 352, 355 Standard Microsystems device drivers Ethernet 3016 140 SMC 8003EP 140 SMC 8003EPC 140 SMC 8013EPC 140 SMC 8013EWC 140 SMC 8013WC 140 SMC 80x3 256 SMC ARCNET 140, 258 SMC Ethernet 3016 255 STARTUP.
406 Index TOKENRNG 301, 307 tokwd section 276 – 277 Toshiba ToshibaLAN 140 ToshibaLAN 264 transceiver entry 147, 149, 201 Transmission size, limiting 136 Transmit buffers 149 Transmit chain-request queue for IBM network adapters 198, 200 Transmit queue entries for 3Com EtherLink II 148 for 3Com EtherLink/MC 154 for 3Com TokenLink 157 for Cabletron T2015 167 for Cabletron T3015 168 Transmit windows 146 transmitbuffers entry 272 – 273 Transport drivers 105 Trxbuffers entry 352, 357 Trxbufsize entry 352, 358
Index wrknets entry (LANMAN.INI) 330 wrkservices entry 42, 318 wrkservices line 28 X XIF 115, 117 – 118 xmitbufs entry 147, 149, 194, 196 xmitbufsize entry 194, 197 xsaps0 parameter (PROTOCOL.INI) 352, 358 xsaps1 parameter (PROTOCOL.INI) 352, 358 xsports entry 287 xsports entry entry 117 xstations0 parameter (PROTOCOL.INI) 352, 358 xstations1 parameter (PROTOCOL.
408 Index BLANK PAGE IMPORTANT: This text will appear on screen, but will not print on a PostScript printer. This page should be the last one in this file; it was inserted by running the InsertBlankPage macro.
Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.
