HP 9000 Networking NetWare® 4.1/9000 NetWare Client for DOS and MS Windows Technical Reference HP Part No. J2771-90016 Printed in U.S.A.
Notice Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Printing History Printing History The manual printing date and part number indicate its current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes.
Preface Preface Introduction NetWare Client for DOS and MS Windows Technical Reference provides you with detailed information to configure the NetWare® DOS Requester™ software, modify the NetWare Client™ configuration file, and troubleshoot client workstation error messages in order to manage client workstations on a NetWare network. This document is for supervisors responsible for managing NetWare client workstations.
Preface Documentation Conventions This manual uses the following Novell® conventions: Asterisk ( * ) An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, ™, etc.). An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a “Trademarks” section at the back of printed manuals.
Preface lowercase letters. Ellipses Ellipses in syntax examples indicate that parameters, options, or settings can be repeated. For example, in the command LOGIN SERVER1/SUPERVISOR /option... you could replace option with any number of available options. Emphasis Italic type also indicates emphasized text. For example: Remember to load the driver before you install the application. Key Names Angle brackets surround the name of a key. For example, corresponds to the Enter key on your keyboard.
Preface Default 54 (approximately 3 seconds) Range 4 to 65,535 Example To make NetBIOS wait longer before sending a request-for-acknowledgment packet, you could place the following lines in your NET.CFG file: netbios netbios verify timeout 1350 [End example] Because interpretation of this file is not case-sensitive, you can type its contents in uppercase or lowercase letters. Options In syntax examples, braces indicate that you are required to choose one of the enclosed options.
Preface example, /etc/hosts. Because UNIX is case-sensitive, these names usually are in lowercase letters. Type UNIX filenames exactly as shown. Variables Italic type indicates variables—descriptive item names, such as command parameters—that you replace with appropriate values. For example, in the command FTP –F remote_host you type the name of a computer on your network in place of remote_host.
Preface NetWare Application Notes, Sep 92 (Novell part no. 164-000031-009) • “NetWare and LAN Server Client Interoperability via ODINSUP: Part 2,” NetWare Application Notes, Nov 92 (Novell part no. 164-000031-011) • “NetWare and Windows for Workgroups 3.1 Interoperability,” NetWare Application Notes, Mar 93 (Novell part no. 164-000032-003) • NetWare Client for DOS and MS Windows User Guide, Novell Publication (Novell part no.
Preface x
Contents 1 Optimizing the NetWare Client Software Overview 1-2 Introduction 1-3 Increasing Speed 1-4 Using the Packet Burst Protocol 1-4 Requirement for Packet Burst 1-4 How Packet Burst Works 1-4 When to Use Packet Burst 1-5 Configuring for Packet Burst 1-5 Disabling Packet Burst 1-5 Using Large Internet Packet Functionality 1-5 How Large Internet Packet Works 1-6 When to Use Large Internet Packet 1-6 Configuring for Large Internet Packet 1-6 Disabling LIP 1-7 Improving Security 1-8 Using NCP Packet Sign
Contents Troubleshooting NCP Packet Signature 1-13 Client Workstations Are Not Signing Packets 1-13 Client Workstations Cannot Log In 1-13 The Error Message “Error Receiving from the Network” Appears Third-Party NLM Programs Do Not Work 1-14 Insecure Client Workstations Log In to a Secure Server 1-14 1-14 Using Other Client Security Guidelines 1-15 Additional Information 1-16 2 NET.CFG Options Reference Overview 2-2 Introduction 2-3 Creating and Modifying a NET.
Contents TRAP COMMUNITY [“name | public | private”] 2-18 Community Access Management 2-18 ENABLE MONITOR COMMUNITY [specified | any | off | omitted] 2-20 ENABLE CONTROL COMMUNITY [specified | any | off | omitted] 2-20 ENABLE TRAP COMMUNITY [specified | off | omitted] 2-20 MIB-II (Management Information Base) Support 2-22 System and SNMP Groups 2-22 SNMPENABLEAUTHENTRAP [on | off] 2-24 SYSCONTACT “contact” 2-24 SYSLOCATION “location” 2-25 SYSNAME “name” 2-25 Interface Group 2-25 TCP/IP Groups 2-26 Example o
Contents Listing of Commonly Used ODI LAN Drivers 2-41 Link Support Option 2-46 Available Parameters and Values for the Link Support Option LINK SUPPORT 2-46 BUFFERS communication_number [buffer_size] 2-47 MAX BOARDS number 2-49 MAX STACKS number 2-50 MEMPOOL number [k] 2-50 2-46 NetWare DOS Requester Option 2-52 Current Core Virtual Loadable Module (VLM) Programs 2-52 Current Non-Core Virtual Loadable Module Programs 2-53 Compatibility with NetWare Shell Parameters 2-54 Managing the NetWare DOS Reques
Contents CONNECTIONS=number 2-72 DOS NAME=“name” 2-72 EOJ=[on | off] 2-73 EXCLUDE VLM=path_vlm 2-74 FIRST NETWORK DRIVE=drive_letter 2-74 FORCE FIRST NETWORK DRIVE=[on | off] 2-75 HANDLE NET ERRORS=[on | off] 2-75 LARGE INTERNET PACKETS=[on | off] 2-76 LIP START SIZE=number 2-77 LOAD CONN TABLE LOW=[on | off] 2-77 LOAD LOW CONN=[on | off] 2-78 LOAD LOW IPXNCP=[on | off] 2-79 LOAD LOW REDIR=[on | off] 2-79 LOCAL PRINTERS=number 2-80 LOCK DELAY=number 2-81 LOCK RETRIES=number 2-81 LONG MACHINE TYPE=“name” 2-
Contents RESPONDER=[on | off] 2-94 SEARCH MODE=number 2-94 SET STATION TIME=[on | off] 2-96 SHORT MACHINE TYPE=“name” 2-96 SHOW DOTS=[on | off] 2-97 SIGNATURE LEVEL=number 2-97 TRUE COMMIT=[on | off] 2-98 USE DEFAULTS=[on | off] 2-99 VLM=path_VLM 2-100 WORKGROUP NET=workgroup_net_address 2-101 Protocol IPX Option 2-103 Available Parameters and Values for the Protocol IPX Option PROTOCOL IPX 2-103 BIND LAN_driver_name [#number] 2-104 INT64 [on | off] 2-104 INT7A [on | off] 2-105 IPATCH byte_offset, value
Contents LAN Drivers 2-115 BIND odi_driver [number frame_type network_name] 2-116 IP Addresses 2-117 IP_ADDRESS ip_address [network_name] 2-118 IP_NETMASK net_mask_address [network_name] 2-119 IP_ROUTER ip_address [network_name] 2-120 Connection Sockets 2-120 Transmission Control Protocol (TCP) Sockets 2-121 TCP_SOCKETS number 2-121 User Datagram Protocol (UDP) Sockets 2-122 UDP_SOCKETS number 2-122 Raw Sockets 2-123 RAW_SOCKETS number 2-123 Additional Support 2-124 NO_BOOTP 2-124 PATH TCP_CFG [[ drive: ]p
Contents DOSNP Software 3-10 4 System Messages xviii
1 Optimizing the NetWare Client Software 1-1
Optimizing the NetWare Client Software Overview Overview This chapter explains how to optimize the NetWare® Client™ software for increasing the speed of client workstations by using the Packet Burst™ protocol and Large Internet Packets (LIP). It also explains how to protect information on client workstations. The following topics are covered in this chapter.
Optimizing the NetWare Client Software Introduction Introduction You can increase the speed and improve the security of client workstations by using the Packet Burst protocol and Large Internet Packets (LIPs), and by implementing the NCP™ packet signature feature available in NetWare 4™ and 3.12 software.
Optimizing the NetWare Client Software Increasing Speed Increasing Speed NetWare 3.12 and 4 support the Packet Burst and Large Internet Packet technologies which increase the access speed of network resources and services for client workstations. Using the Packet Burst Protocol The Packet Burst protocol allows high-performance data transmission between client workstations and servers. Some network topologies, such as Ethernet and token ring, allow large packets to be sent over the network.
Optimizing the NetWare Client Software Increasing Speed When to Use Packet Burst Packet Burst is not required for every installation; however, disabling LIP will results in noticeable speed degradation. Some network supervisors might choose not to use Packet Burst because some of the servers that the client workstations are connecting to do not support it. Configuring for Packet Burst Although Packet Burst is automatically enabled in the NetWare DOS Requester, you can configure it for your needs.
Optimizing the NetWare Client Software Increasing Speed The following sections provide you with information and procedures for setting parameters used in the client workstation configuration file (NET.CFG). The Large Internet Packet technology on the client workstation is enabled automatically in the NetWare DOS Requester software. NOTE: Some LAN drivers might not operate correctly using this parameter. If you experience trouble, disable this parameter or update the version of your LAN driver.
Optimizing the NetWare Client Software Increasing Speed Disabling LIP To disable LIP functionality at the client workstation, add this line to the NET.
Optimizing the NetWare Client Software Improving Security Improving Security You can increase the security of your network by using the NCP packet signature feature available in NetWare 4 and 3.12. The following sections provide you with information and procedures for setting a parameter used in the client workstation configuration (NET.CFG) file and the SET command used at each NetWare server.
Optimizing the NetWare Client Software Improving Security When to Use NCP Packet Signature NCP packet signature is not required for every installation. Some network supervisors might choose not to use it because they can tolerate certain security risks.
Optimizing the NetWare Client Software Improving Security Effective Packet Signature Levels The signature levels for the server and the client workstations combine to determine the overall level of NCP packet signature on the network called the effective packet signature level. Some combinations of server and client packet signature levels might slow performance. However, low-CPU-demand systems might not show any performance degradation.
Optimizing the NetWare Client Software Improving Security Sensitive and Nonsensitive Information Reside on the Same Server Example The NetWare server has a directory for executable programs and a separate directory for corporate finances (such as accounts receivable). Solution The network supervisor sets the server to level 2 and the client workstations that need access to accounts receivable to level 3. All other client workstations remain at the default level 1.
Optimizing the NetWare Client Software Improving Security netware dos requester signature level = 2 Replace number with 0, 1, 2, or 3. The default is level 1, which provides the most flexibility while still offering protection from forged packets. See “SIGNATURE LEVEL=number” for details on how to configure for NCP packet signature support on the client workstation. NOTE: Some LAN drivers might not operate correctly using this parameter.
Optimizing the NetWare Client Software Improving Security Troubleshooting NCP Packet Signature This section describes some solutions to problems that might be associated with using NCP packet signature. Client Workstations Are Not Signing Packets Problem Client workstations are not signing NCP packets. Solution The SECURITY.VLM file is not loading. Ensure the signature level on the client workstation is not set to 0. SECURITY.VLM loads by default when the client signature level is set to 1, 2 or 3.
Optimizing the NetWare Client Software Improving Security The Error Message “Error Receiving from the Network” Appears Problem The error message “Error receiving from the network” appears. Solution The client workstation is using a version of LOGIN.EXE file that doesn’t include NCP packet signature. Make sure the new LOGIN.EXE and other new utility files are installed on all NetWare servers on the network.
Optimizing the NetWare Client Software Using Other Client Security Guidelines Using Other Client Security Guidelines In addition to installing NCP packet signature, you can use other NetWare security features and protective measures to keep client workstations secure. We suggest the following security guidelines for client workstations: • Use only the most current versions of system software, NetWare Client software, and patches. • Check for viruses regularly.
Optimizing the NetWare Client Software Additional Information Additional Information Topic Reference Setting up and modify your NET.CFG file for Packet Burst, LIP, and NCP packet signatures Chapter 2, “NET.
2 NET.
NET.CFG Options Reference Overview Overview This chapter explains how to create or modify a NET.CFG file and contains an alphabetical listing and discussions of the currently available NET.CFG file options. The following topics are covered in this chapter. Topic Creating and Modifying a NET.CFG File Using NET.CFG Options and Parameters Using the NET.
NET.CFG Options Reference Introduction Introduction NET.CFG is the configuration file that you use to specify nondefault value settings for your NetWare Client™ software configuration options. Use entries in the NET.CFG file to change the client workstation’s network environment or configuration.
NET.CFG Options Reference Creating and Modifying a NET.CFG File Creating and Modifying a NET.CFG File 1 Use a DOS text editor to type section headings and options in an existing NET.CFG file or a NET.CFG file that you create to set up your client workstation configuration. The default location of the NET.CFG file is C:\NWCLIENT. 2 After a NET.CFG file is created or modified, copy or save the NET.CFG file to the client workstation diskette or directory. If all client workstations use the same NET.
NET.CFG Options Reference Creating and Modifying a NET.CFG File If a semicolon is placed in front of a NET.CFG option line, all of the parameters listed below are disabled. The following figure illustrates the NET.CFG file format. link driver ne2000 int 4 port 360 frame ethernet_802.3 Options typed flush left, one per line. Settings indented under option, one setting per line.
NET.CFG Options Reference Creating and Modifying a NET.CFG File ; Change the port to 340 (hex) port #1 340 netware dos requester ; Set up F: as the first drive on network first network drive = f NOTE: Changing the value setting in the NET.CFG does not change the hardware setting for the device you are using. Run the appropriate configuration utility or manually change the appropriate jumper settings to correspond with value setting used in the NET.CFG file.
NET.CFG Options Reference Using NET.CFG Options and Parameters Using NET.CFG Options and Parameters NetWare and Personal NetWare™ workstations support the following configuration options in the NET.CFG file: NOTE: • Desktop SNMP Option • Link Driver Option • Link Support Option • NetWare DOS Requester Option • Protocol IPX Option • Protocol SPX Option • Protocol TCPIP Option • Transport Provider IPX | UDP Option Because many products use the NET.
NET.CFG Options Reference Using NET.CFG Options and Parameters Table 2-1 NET.
NET.CFG Options Reference Using NET.CFG Options and Parameters Table 2-1 NET.
NET.CFG Options Reference Using NET.CFG Options and Parameters Table 2-1 NET.
NET.CFG Options Reference Using NET.CFG Options and Parameters Table 2-1 NET.CFG Options no_bootp path tcp_cfg [[ drive: ]path [; ...
NET.CFG Options Reference Using the NET.CFG Reference Pages Using the NET.CFG Reference Pages The following figure explains how to read the following NET.CFG reference pages in this chapter. Option name Link Driver Option Use this option to specify the hardware and software configurations of the LAN drivers for each network board in your workstation.
NET.CFG Options Reference Desktop SNMP Option Desktop SNMP Option Use this option to manage MIB-II support and communities for SNMP desktops on NetWare and Personal NetWare networks. Available Parameters and Values for the Desktop SNMP Option This option has the following categories, parameters, and values.
NET.CFG Options Reference Desktop SNMP Option Syntax desktop snmp parameter_name value Replace parameter_name with the name of the parameter you want to use. Replace value with the number or setting which corresponds with the parameter name. Example To identify the name of the system administrator for MIB II, you would place these lines in your NET.CFG file: desktop snmp sysname “Suzanne Morley x893” NOTE: For transport providers used with SNMP desktops, see “Transport Provider IPX | UDP Option”.
NET.CFG Options Reference Desktop SNMP Option Syntax asynchronous timeout number Default 20 Example For example, to have Desktop SNMP wait 35 system ticks (approximately 2 seconds) before attempting to cancel a request, you would place the following lines in your NET.CFG file: desktop snmp asynchronous timeout 35 NOTE: The timeout number is in ticks (18.21 ticks per second on IBM* PCs and compatibles).
NET.CFG Options Reference Desktop SNMP Option NOTE: If Desktop SNMP receives a request protocol data unit (PDU) whose community name is not authorized, it does not respond to the request. For example, suppose the control community name is “secret,” and Desktop SNMP receives a SETRequest PDU with a community name of “public.” Desktop SNMP discards the SETRequest UDP and does not respond to the UDP. However, Desktop SNMP does send an authentication trap to the trap targets if SNMPENABLEAUTHENTRAPS ON.
NET.CFG Options Reference Desktop SNMP Option Table 2-2 Desktop SNMP Option Parameters for Community Names Parameter Explanation control community Describes the read/write community (the community that is allowed to do SET operations). Any community name established for read/write access is also valid for read-only access. The default value is “public.” When the control community is disabled, all write access is disabled.
NET.CFG Options Reference Desktop SNMP Option CONTROL COMMUNITY [“name | public | private”] Specifies the control community name. Syntax control community [“name | public | private”] Default public Example To specify the control community as “secret,” you would place the following lines in your NET.CFG file: desktop snmp control community “secret” TRAP COMMUNITY [“name | public | private”] Specifies the trap community name.
NET.CFG Options Reference Desktop SNMP Option For example, if you disable the control community, no one can use Desktop SNMP to do SET operations against the data it manages. For examples of complete files, see “Example of NET.CFG Files Using the Community Name and Types.
NET.CFG Options Reference Desktop SNMP Option ENABLE MONITOR COMMUNITY [specified | any | off | omitted] Enables the value settings for the monitor community. Syntax enable monitor community [specified | any | off | omitted] Default specified Example To enable the monitor community as “private” only, you would place the following lines in your NET.
NET.CFG Options Reference Desktop SNMP Option Example of NET.CFG Files Using the Community Name and Types To use the default trap community, allow any community name to be used for read access, but set the read/write community name to “secret,” you would place the following lines in your NET.
NET.CFG Options Reference Desktop SNMP Option desktop snmp enable monitor community any monitor community “private” enable control community specified control community “private” enable trap community specified trap community “agenttrap” Desktop SNMP ignores the monitor community “private” line until you reset the enable monitor community line to “specified.” This allows you to temporarily change the value to “any” or “off” without deleting the specific community name.
NET.CFG Options Reference Desktop SNMP Option You can define some parameters for your workstation environment in the NET.CFG file (or other defined configuration file). The following table explains these parameters. Table 2-4 Desktop SNMP Option Parameters for MIB-II Support Parameter Explanation snmpenableauthentrap The snmpenableauthentraps parameter defaults to “off.
NET.CFG Options Reference Desktop SNMP Option NOTE: Always enclose the name, location, or contact information in quotation marks. SNMPENABLEAUTHENTRAP [on | off] Instructs the Desktop SNMP to send a trap message if someone without proper access tries to use SNMP to get or change information that Desktop SNMP manages.
NET.CFG Options Reference Desktop SNMP Option SYSLOCATION “location” Informs the SNMP manager of the physical location of your workstation. Syntax syslocation “location” Default None Example To notify the SNMP manager that your workstation is in “Building 2,” you would place the following lines in your NET.CFG file: desktop snmp syslocation “Building 2” SYSNAME “name” Informs the SNMP manager of your username.
NET.CFG Options Reference Desktop SNMP Option NOTE: Always place the vlm=mib2if.vlm line after the lines that load the Desktop SNMP VLM suite of files. TCP/IP Groups Desktop SNMP also provides a separate VLM file, MIB2PROT.VLM, that supports the TCP/IP groups (all groups except interface, system, and SNMP, which are supported by other VLM files, and EGP and transmission, which are not supported). Load this VLM when you are using the TCP/IP stack from LAN WorkPlace® software.
NET.CFG Options Reference Link Driver Option Link Driver Option Use this option to specify the hardware and software configurations of the LAN drivers for each network board in your workstation. The value settings you specify for each parameter with this option should match the hardware and software settings for your network board. This option also allows you to set up the proper frame type and protocols for NetWare supported LAN drivers.
NET.CFG Options Reference Link Driver Option Syntax link driver driver_name parameter_name, value Replace driver_name with the name of the LAN driver. Replace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name. (See Table 2-6 “List of ODI LANB Driver Names and Supported Network Boards” for more information.
NET.CFG Options Reference Link Driver Option Bus Type NOTE: Identification Number ISA 0 MCA 1 EISA 2 PCMCIA 3 PCI 4 VL (VESA Local Bus) 5 This is not a conclusive list of bus types. You can obtain an updated list of identifiers from the Novell Labs™ facility. The default value indicates that the LAN driver should search each of the machine’s buses for a supported network board. The LAN driver should then initialize the first supported network board it finds.
NET.CFG Options Reference Link Driver Option Syntax dma [#1 | #2] channel_number Enter the channel number to be used. You can specify two DMA values. Default #1 Example If the first configurable DMA channel on your NE2100TM network board uses DMA channel 3 and the second configurable channel uses channel 4, you would place the following lines in your NET.CFG file: link driver ne2100 dma #1 3 dma #2 4 FRAME frame_type_name [addressing_mode] Enables the frame types used by the LAN driver.
NET.CFG Options Reference Link Driver Option Default Ethernet LAN drivers: Ethernet_802.2 Token-ring LAN drivers: Token-Ring TCP/IP LAN driver SLIP_PPP: SLIP See Table 2-4 “List of Frame Types, Protocols, and LAN Drivers” for more information. Example To enable the Token-Ring frame type for an NTR2000 LAN driver, you would place the following lines in your NET.CFG file: link driver ntr2000 token-ring lsb To enable the Ethernet_II and Ethernet 802.
NET.CFG Options Reference Link Driver Option Table 2-5 List of Frame Types, Protocols, and LAN Drivers Frame Type and Description ETHERNET_802.
NET.CFG Options Reference Link Driver Option Table 2-5 List of Frame Types, Protocols, and LAN Drivers Frame Type and Description FDDI_802.2 Protocols LAN Drivers IPX/SPX † IP IPX/SPX † IPX/SPX RPL SNA NetBIOS LANSUP, MADGEODI, NTR2000, ODINSUP, OSH391R, OSH392R, OSH89XR, OSH990R, SMC8100, T20ODI, T30ODI, TCTOKSH, NTR2000 FDDI using an 802.2 envelope IP IP Tunnel frame envelope Token-Ring Token ring (802.5) using an 802.
NET.CFG Options Reference Link Driver Option IRQ [#1 | #2] interrupt_request_number Specifies which interrupt (IRQ) the network board is set to use. Syntax irq [#1 | #2] interrupt_request_number Use the same interrupt request number that is set on the network board. Default #1 See your LAN driver documentation for the specific IRQ default values. Example To specify interrupt 5 on an NE2100 network board, you would place the following lines in your NET.
NET.CFG Options Reference Link Driver Option Syntax max frame size number If the line speed is 16 Mbps, the value for number must be between 638 and 17,954. If the line speed is 4 Mbps, the value must be between 638 and 4464. The value must include the number of bytes for the data packet (usually 1, 2, 4, or 8KB), and for the largest possible header (currently, 52 bytes LAN header + 74 bytes protocol header = 126 bytes).
NET.CFG Options Reference Link Driver Option Replace hex_starting_address with the hexadecimal physical (absolute) address of the memory used by the network board. Replace the hex_length with the memory address range (in hexadecimal paragraphs, with each paragraph being 16 bytes) used by the network board. Usually, the hex length is not needed.
NET.CFG Options Reference Link Driver Option For example, node addresses for both modes could appear as follows: NOTE: • node address 0800005A656BL (canonical LSB) • node address 1000005AA6D6M (non-canonical MSB) If the “M” or “L” is not specified, the default mode for the node address is the physical layer form of the address.
NET.CFG Options Reference Link Driver Option If the IBM LAN Support driver’s DXMT0MOD.SYS file is to load in the CONFIG.SYS file, one of two actions must be performed: 1 Set “o=n” on the command line for loading the DXMT0MOD.SYS file in the CONFIG.SYS file and use this parameter in the NET.CFG file. 2 Set “o=y” on the command line to load the DXMT0MOD.SYS file and set the frame size for the NDIS driver. Do not use this parameter in the NET.CFG file.
NET.CFG Options Reference Link Driver Option PROTOCOL “name” hex_protocol_ID frame_type Allows existing LAN drivers to handle new network protocols. Syntax protocol name hex_protocol_ID frame_type Replace name with the name of the new protocol. Replace hex_protocol_ID with the assigned hexadecimal protocol ID that the protocol is assigned. Replace frame_type with the frame type that the new protocol ID applies to.Table 5-6 for more information.
NET.CFG Options Reference Link Driver Option Table 2-6 List and Description of Protocols and Frame Types with Their Identification Numbers Frame ID Frame Type Protocol Protocol ID Number Description 2 ETHERNET_II IPX/SPX 8137h Ethernet using a DEC* Ethernet II envelope 2 ETHERNET_II IP 800h Ethernet using a DEC Ethernet II envelope 3 ETHERNET_802.2 IPX/SPX E0h Ethernet (802.3) using an 802.2 envelope 4 Token-Ring IPX/SPX E0h Token ring (802.5) using an 802.
NET.CFG Options Reference Link Driver Option Example If you were using two NE/2™ boards in the same workstation and you inserted one network board into slot 1 and the other into slot 2, you would place the following lines in your NET.CFG file: link driver NE2 slot 1 link driver NE2 slot 2 Listing of Commonly Used ODI LAN Drivers The following table lists some of the common ODI™ LAN drivers used with NetWare Client™ software for DOS and MS Windows.
NET.CFG Options Reference Link Driver Option Driver Name (.
NET.CFG Options Reference Link Driver Option Driver Name (.
NET.CFG Options Reference Link Driver Option Driver Name (.COM) NULLDRV Network Board This is not a working LAN driver. The NetWare client installation program copies this file to the client directory during installation for dedicated (not ODI) IPX drivers. Contact the network board manufacturer for copies of the latest ODI drivers. This LAN driver can also be used to support the Personal NetWare™ client and server software running on a workstation without a network board installed. OC32TR16.
NET.CFG Options Reference Link Driver Option Driver Name (.
NET.CFG Options Reference Link Support Option Link Support Option Use this option of the NET.CFG file to configure the number and size of the receive buffers, the size of the memory pool buffers, and the number of boards and stacks used by the Link Support Layer™ (LSL). Available Parameters and Values for the Link Support Option This option has the following parameters and values, which are discussed on the following pages.
NET.CFG Options Reference Link Support Option BUFFERS communication_number [buffer_size] Configures the number and size of receive buffers that the Link Support Layer (LSL) manages. Communication Number The number of communication buffers must be large enough to hold all protocol headers and the maximum data size. If you make many connections, you should increase the number of buffers to increase performance.
NET.CFG Options Reference Link Support Option Default For IPX: communication_number: The IPX protocol utilizes its own buffers and does not require the Link Support Layer software to provide buffers for it. buffer_size: 1500 bytes For TCP/IP: communication_number: 8 buffers buffer_size: 1500 bytes TCP/IP requires only 1500 bytes, because the LAN driver places the 14 bytes of media header on the frame, prior to transmission.
NET.CFG Options Reference Link Support Option NOTE: For the most efficient communication, your link support buffer size should be the same size as the packets that your workstation receives over the network. You might want to set the link support buffer size equal to the largest buffer size that the network boards in your workstation supports. MAX BOARDS number Configures the maximum number of logical boards that the LSL.COM file can manage. Each LAN driver can use more than one board resources.
NET.CFG Options Reference Link Support Option NOTE: Each LAN driver resource or frame type requires approximately 200 bytes of memory. MAX STACKS number Configures the maximum number of logical protocol stack IDs the LSL.COM file can manage. Each protocol stack can use more than one stack ID resources. If a protocol stack fails to load because of an out-of-resource condition, increase the value for this option. The amount of resident memory the LSL.
NET.CFG Options Reference Link Support Option Syntax mempool number [k] Default 0 Example To configure the size of the memory pool, you could place the following lines in your NET.CFG file: link support mempool 1024 NOTE: The IPXODI protocol stack does not use memory pool buffers.
NET.CFG Options Reference NetWare DOS Requester Option NetWare DOS Requester Option Use this option of the NET.CFG file to configure the NetWare Client software for various types of networking support and connectivity. The NetWare DOS Requester software provides networking support for DOS and Microsoft (MS) Windows client workstations. The NetWare DOS Requester is built on an architecture of Virtual Loadable Module (VLM) software. The VLM.
NET.CFG Options Reference NetWare DOS Requester Option The table also includes descriptions and flags indicating whether the module is required (R) or optional (O) for NetWare Directory Services™ (NDS) support, bindery services (BIND), and Personal NetWare™ (PNW) services. Table 2-7 Module Name List of Current Core VLM Programs and the Respective Load Order Description NDS BIND PNW BIND.VLM NetWare protocol implementation using the bindery O R O CONN.VLM Connection table manager R R R FIO.
NET.CFG Options Reference NetWare DOS Requester Option The table also includes descriptions and flags indicating whether the module is used (U) or not used (N) for NetWare Directory Services (NDS), bindery services (BIND), and Personal NetWare (PNW) services. Table 2-8 List of Current Non-Core VLM Programs Module name Description NDS BIND PNW AUTO.VLM Auto-reconnect/auto-retry U U U MIB2IF.VLM MIB-II interface groups support U U U MIB2PROT.
NET.CFG Options Reference NetWare DOS Requester Option Parameters and Values Status all servers=[on | off] ¤ cache buffers=number † checksum=[on | off] ¤ (Now requires a number value from 0 to 3.) dos name=name † entry stack size=number ¤ environment pad=number ¤ eojs=[on | off] † file handles=number ¤ (Functionality is provided by the FILES parameter setting in the CONFIG.SYS file.
NET.
NET.CFG Options Reference NetWare DOS Requester Option Condition Specifying a NET.CFG file outside the current directory Explanation At the command line, enter a command similar to the following (or add the command to the AUTOEXEC.BAT file): VLM /C=C:\NWCLIENT\NET.CFG Loading the NetWare DOS Requester memory managers under MS Windows 3.0 If you are running MS Windows 3.0, ensure that the VLM.EXE file is loaded after any upper- or high-memory managers are loaded.
NET.
NET.CFG Options Reference NetWare DOS Requester Option This entry indicates the following: • The CACHE BUFFER SIZE is set for an Ethernet network board • The “DOS FILES=” command in the CONFIG.SYS file is set above 64 files • The servers are running NetWare 3.12 Best Conventional Memory Usage For the best memory usage, use the following parameters under the NetWare DOS Requester option in the NET.CFG file.
NET.
NET.
NET.
NET.CFG Options Reference NetWare DOS Requester Option NETWARE DOS REQUESTER Controls network requests from your client workstation to a NetWare server or network. Syntax netware dos requester parameter_name=value Replace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name. Example To configure for four server connections, you would place these lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option Use this parameter for binder connections if your username and password total more than 32 characters. For this parameter to work, also set BIND RECONNECT=ON. AUTO RECONNECT=[on | off] When this parameter is set to “on,” the AUTO.VLM program reconnects a client workstation to a NetWare server and rebuilds the workstation’s environment (excluding file-specific items) prior to connection loss. When this parameter is set to “off,” the AUTO.
NET.CFG Options Reference NetWare DOS Requester Option Example To make the AUTO.VLM program wait for one minute before retrying a connection, you would place the following lines in your NET.CFG file: netware dos requester auto retry=60 To enable the VLM.EXE program to load the AUTO.VLM file, you must include the VLM=AUTO.VLM parameter and value. You must also load RSA.VLM if you are re-establishing a NetWare Directory Services (NDS) connection, by using the VLM=RSA.VLM parameter.
NET.CFG Options Reference NetWare DOS Requester Option Example To save memory by shortening the average name length allowed to eight characters, you would place the following lines in your NET.CFG file: netware dos requester average name length=9 BIND RECONNECT=[on | off] Automatically rebuilds bindery connections and restores drive mappings and printer connections. Syntax bind reconnect=[on | off] Default off Modules AUTO.VLM, BIND.
NET.CFG Options Reference NetWare DOS Requester Option Syntax broadcast retries=number Default 3 Range 1 to 255 Modules PNW.VLM Example To enable a workgroup to display in the WGLIST utility that is not reachable by using the default value, you could place the following lines in your NET.CFG file: netware dos requester broadcast retries=10 BROADCAST SEND DELAY=number Sets the number of ticks the NetWare DOS Requester software waits between performing any function.
NET.CFG Options Reference NetWare DOS Requester Option Set this to a higher number if you are trying to see resources physically located at a long distance from your workstation. NOTE: Increasing this number decreases the response time of some utilities. Syntax broadcast timeout=number Default 2 Range 1 to 255 Modules PNW.VLM Example To enable a workgroup to display in the WGLIST utility that is unreachable by using the default value, you could place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option WARNING: When specifying the value for this parameter, don’t exceed the maximum packet size of the network board. Doing so might cause system failure. CACHE BUFFERS=number Sets the number of cache buffers the NetWare DOS Requester software uses for local caching of nonshared, nontransactionally tracked files. Each buffer allocated allows one file to be cached.
NET.CFG Options Reference NetWare DOS Requester Option Leaving the value for this parameter set to the “on” default can cause data loss if the NetWare server runs out of disk space between write requests. Syntax cache writes=[on | off] Default on Modules FIO.VLM Example To increase data integrity at the expense of performance, you could place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option NOTE: Ethernet frame type 802.3 doesn’t support checksums. CONFIRM CRITICAL ERROR ACTION=[on | off] Determines the default method used for handling network critical error messages in MS Windows.
NET.CFG Options Reference NetWare DOS Requester Option For this parameter to function properly, use the NETWARE.DRV version 3.03 or later, and include the “network.drv=netware.drv” line under the [boot] heading in the MS Windows SYSTEM.INI file. This parameter affects the performance of your MS Windows environment. CONNECTIONS=number Sets the maximum number of connections the NetWare DOS Requester software supports. The NetWare DOS Requester supports up to 50 connections in its connection table.
NET.CFG Options Reference NetWare DOS Requester Option The %OS variable in the login or profile script uses this variable when mapping a search drive to the network DOS directory. Syntax dos name=“name” Default MSDOS Range 1 to 5 characters Modules GENERAL.VLM, NETX.VLM Example To set the operating system used for the shell to DR DOS®, you would place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option EXCLUDE VLM=path_vlm Specifies a .VLM file that the VLM.EXE program should not load. This parameter causes any .VLM file listed in the VLM.EXE program default load table or in the VLM vlm_path parameter to not load when the VLM.EXE program runs. You must specify the complete filename, including the .VLM extension. Syntax exclude vlm=path_vlm Range 1 to 50 Modules VLM.EXE Example To exclude the loading of the PRINT.VLM, SECURITY.VLM, and NMR.
NET.CFG Options Reference NetWare DOS Requester Option Example To set the first drive to G:, you would place the following lines in your NET.CFG file: netware dos requester first network drive=g FORCE FIRST NETWORK DRIVE=[on | off] Specifies the network drive letter the SYS:LOGIN directory is mapped to after logging out of a server or network. Setting the value to “on” specifies that the drive letter must be the same as the one use in FIRST NETWORK DRIVE.
NET.CFG Options Reference NetWare DOS Requester Option On = interrupt 24 handles network errors Off = return NET_RECV_ERROR (example: 8805h) Syntax handle net errors=[on | off] Default on Modules IPXNCP.VLM Example To receive an error return of “NET_RECV_ERROR,” you would place the following lines in your NET.CFG file: netware dos requester handle net errors=on LARGE INTERNET PACKETS=[on | off] Sets the Large Internet Packet (LIP) packet size above the default of 576 bytes.
NET.CFG Options Reference NetWare DOS Requester Option NOTE: Some routers and bridges have been hardcoded to use 576-byte packets. In this case, the NetWare DOS Requester can use only 576-byte packets, regardless of this parameter. LIP START SIZE=number Specifies the packet size of used by the NetWare DOS Requester when starting LIP negotiations. Use this parameter to reduce the amount of traffic caused by the negotiation process across slow links.
NET.CFG Options Reference NetWare DOS Requester Option Syntax load conn table low=[on | off] Default off Modules CONN.VLM Example To increase conventional memory requirements required by the NetWare Client software for supporting the initial release of NetWare 4.0 utilities, you would place the following lines in your NET.CFG file: netware dos requester load conn table low=on NOTE: Use the VLM /D command line parameter to determine how much conventional memory is used by this parameter setting.
NET.CFG Options Reference NetWare DOS Requester Option NOTE: Use the VLM /D command line parameter to determine how much conventional memory is used by this parameter setting. LOAD LOW IPXNCP=[on | off] Specifies whether the transport manager for IPX is loaded in high (XMS or EMS) or conventional memory. By default, the transport protocol implementation for IPX, IPXNCP.VLM, is loaded in conventional memory. If the value for this parameter is set to “off,” IPXNCP.
NET.CFG Options Reference NetWare DOS Requester Option Syntax load low redir=[on | off] Default off Modules REDIR.VLM Example To load REDIR.VLM in conventional memory, thereby increasing performance but sacrificing memory, you would place the following lines in your NET.CFG file: netware dos requester load low redir=on NOTE: Use the VLM /D command line parameter to determine how much conventional memory is used by this parameter setting.
NET.CFG Options Reference NetWare DOS Requester Option LOCK DELAY=number Determines the amount of time (in ticks) the NetWare DOS Requester software waits before trying to get a lock. When many users access a file at the same time, the NetWare DOS Requester software might be unable to gain access before its allotted wait time. Use this parameter if client workstations frequently receive error messages when a file is requested.
NET.CFG Options Reference NetWare DOS Requester Option It is part of an equation that determines the total time the NetWare DOS Requester waits when attempting to access a locked file. If a client workstation frequently receives error messages when a file is requested, increase the value of this parameter. Syntax lock delay=number Default 1 tick Range 0 to 255 (approximately six hours) Modules GENERAL.VLM Example To automatically lock files, you could place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option Syntax long machine type=“name” Default IBM-PC Range 1 to 6 Modules GENERAL.VLM, NETX.VLM Example To specify the machine type as COMPAQ, you would place the following lines in your NET.CFG file: netware dos requester long machine type=“compaq” MAX TASKS=number Configures the maximum number of tasks that can be active simultaneously.
NET.CFG Options Reference NetWare DOS Requester Option The values are as follows: 0 = Display copyright message and critical errors 1 = Display warning messages 2 = Display program load information for VLM programs 3 = Display configuration information 4 = Display diagnostic information Syntax message level=number Default 1 Modules VLM.EXE Example To display only configuration information, you would place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option MINIMUM TIME TO NET=number Overrides the time-to-net value defined by the local router during connection.
NET.CFG Options Reference NetWare DOS Requester Option Syntax name context=“name_context” Default Root Range Root to 257 (256 characters plus the NULL command) Modules NDS.VLM Example To set your name context to the marketing Organization, you would place the following lines in your NET.CFG file: netware dos requester name context=“ou=mngt.o=marketing” NETWARE PROTOCOL=netware_protocol_list Allows you to list the order that the NetWare protocols (NDS, BIND, and PNW) are used in.
NET.CFG Options Reference NetWare DOS Requester Option NETWORK PRINTERS=number Sets the number of LPT ports the NetWare DOS Requester software can capture. This parameter allows you to capture and redirect LPT1 through LPT9. Increasing the number value increases memory use. Setting the value for this parameter to 0 specifies that PRINT.VLM does not load. If you are setting more than three ports in MS Windows, edit the MS Windows WIN.
NET.CFG Options Reference NetWare DOS Requester Option If you are using any application that uses the “netx=off” command, such as Microsoft Office, ensure that this parameter value is set to “on.” PB BUFFERS=number Controls the use of the Packet Burst protocol for file input/output. Packet Burst is automatically enabled in the NetWare DOS Requester software. The values are as follows: 0 = off nonzero = on and increases the number of buffers.
NET.CFG Options Reference NetWare DOS Requester Option Example To increase the read buffer size for better performance, you could place the following lines in your NET.CFG file: netware dos requester pburst read windows size=64 WARNING: If you are using this option on any client workstation not running Packet Burst, changing the default of this parameter might result in critical network errors. PBURST WRITE WINDOWS SIZE=number Sets the write buffer size (in bytes) for MS Windows.
NET.CFG Options Reference NetWare DOS Requester Option Syntax preferred server=“server_name” Default None Modules BIND.VLM Example To specify the MKT_9 server as your preferred server connection, thereby speeding up log in to bindery services, you would place the following lines in your NET.
NET.CFG Options Reference NetWare DOS Requester Option NOTE: If both PREFERRED TREE (for NetWare Directory Services) and PREFERRED SERVER (for bindery services) are specified, then the first protocol to successfully attach is used, such as NetWare Directory Services or Bindery services. PREFERRED WORKGROUP=“workgroup_name” Sets the Personal NetWare workgroup you attach to first and helps guarantee your connection to the network.
NET.CFG Options Reference NetWare DOS Requester Option Modules PRINT.VLM Example To set the buffer size for printing to 86, you would place the following lines in your NET.CFG file: netware dos requester print buffer size=86 NOTE: While increasing the speed in some of your printing output, this parameter also increases memory use. PRINT HEADER=number Sets the size of the buffer (in bytes) that holds the information used to initialize a printer for each print job.
NET.CFG Options Reference NetWare DOS Requester Option Syntax print tail=number Default 16 Range 0 to 1024 Modules PRINT.VLM Example To increase the size of the print header, you could place the following lines in your NET.CFG file: netware dos requester print header=64 READ ONLY COMPATIBILITY=[on | off] Determines whether a file marked Read Only can be opened with a read/ write access call. Certain applications require the value for this parameter to be set to “on.
NET.CFG Options Reference NetWare DOS Requester Option NOTE: If you are using any application that uses the “netx=off” command, such as Microsoft Office, ensure that this parameter value is set to “on.” RESPONDER=[on | off] Controls the communication and response of the client workstation. Also helps in reducing the NetWare DOS Requester software memory use on the client workstation. Setting the value to “off” causes the client workstation to ignore broadcasts and diagnostic communication.
NET.CFG Options Reference NetWare DOS Requester Option Value Explanation 0 No search instructions. Default value for executable files. 1 If a directory path is specified in the executable file, the executable file searches only that path. If a path is not specified, the executable file searches the default directory and network search drives. 2 The executable file searches only the default directory or the path specified.
NET.CFG Options Reference NetWare DOS Requester Option Example To cause the executable file to search only the default directory or the path specified, you would place the following lines in your NET.CFG file: netware dos requester search mode=2 SET STATION TIME=[on | off] Synchronizes the client workstation date and time with that of the NetWare server that the client workstation initially attaches to. Setting this option to “off” disables the synchronization feature.
NET.CFG Options Reference NetWare DOS Requester Option Range 1 to 4 Modules GENERAL.VLM, NETX.VLM Example To specify the machine type as AST, you would place the following lines in your NET.CFG file: netware dos requester short machine type=“ast” SHOW DOTS=[on | off] Specifies to display parent dots in list boxes for file and directory navigation. NOTE: This parameter is supported only by NetWare 2.11 and later. The NetWare server doesn’t have directory entries for (“.” and “..”) as DOS does.
NET.CFG Options Reference NetWare DOS Requester Option 1 = Enabled but not preferred 2 = Preferred 3 = Required NOTE: Setting this option to 2 or 3 increases security but decreases performance. Syntax signature level=number Default 1 Modules NWP.VLM, SECURITY.VLM Example To designate the level of enhanced security support as “required,” you would place the following lines in your NET.CFG file: netware dos requester signature level=3 Do not set the signature level in the NET.
NET.CFG Options Reference NetWare DOS Requester Option Example To select integrity over performance, you would place the following lines in your NET.CFG file: netware dos requester true commit=on USE DEFAULTS=[on | off] Overrides the default .VLM files that the VLM.EXE program loads. Without it, the VLM.EXE program attempts to load the following files in the given order: CONN.VLM IPXNCP.VLM TRAN.VLM SECURITY.VLM NDS.VLM BIND.VLM NWP.VLM FIO.VLM GENERAL.VLM REDIR.VLM PRINT.VLM NETX.VLM AUTO.
NET.CFG Options Reference NetWare DOS Requester Option Syntax use defaults=[on | off] Default on Modules VLM.EXE Example To load the AUTO.VLM file with the core modules and disable loading of the BIND.VLM file, you would place the following lines in your NET.CFG file: netware dos requester use defaults=off vlm=conn.vlm vlm=ipxncp.vlm vlm=tran.vlm vlm=security.vlm vlm=nds.vlm ;vlm=bind.vlm vlm=nwp.vlm vlm=fio.vlm vlm=general.vlm vlm=redir.vlm vlm=print.vlm vlm=netx.vlm vlm=auto.
NET.CFG Options Reference NetWare DOS Requester Option NMR.VLM RSA.VLM WSASN1.VLM WSDRVPRN.VLM WSREG.VLM WSSNMP.VLM WSTRAP.VLM You must specify the complete filename, including the .VLM extension. Syntax vlm=path_vlm Default None Range 1 to 50 Modules VLM.EXE Example To load AUTO.VLM, RSA.VLM, and NMR.VLM with the core modules, you would place the following lines in your NET.CFG file: netware dos requester vlm=c:\nwclient\auto.vlm vlm=c:\nwclient\rsa.vlm vlm=c:\nwclient\nmr.
NET.CFG Options Reference NetWare DOS Requester Option Syntax workgroup net=workgroup_net_address Default None Modules PNW.VLM Example To set a network address of 00123099:FFFFFFFFFFFF for your workgroup, you would place the following lines in your NET.
NET.CFG Options Reference Protocol IPX Option Protocol IPX Option Use this option of the NET.CFG file to change the default value of parameters for the IPX™ protocol.
NET.CFG Options Reference Protocol IPX Option BIND LAN_driver_name [#number] Usually a protocol binds to the first LAN driver it finds. This parameter forces the protocol to bind to the LAN driver you specify. You are informed of the board number you are binding to when the LAN driver is loading. Syntax bind LAN_driver_name [#number] Replace LAN_driver_name with the name of the LAN driver you want the protocol to bind to. Replace number with the occurrence of the LAN driver you are loading.
NET.CFG Options Reference Protocol IPX Option IPX now uses interrupt 64h to maintain compatibility with earlier versions of NetWare software. If an application’s documentation requests interrupt 64h, or if you have an application that works with earlier versions of NetWare but hangs with NetWare 3.1, set the value for this parameter to “off.” Syntax int64 [on | off] Default on Example To allow an application use interrupt 64h, you would place the following lines in your NET.
NET.CFG Options Reference Protocol IPX Option IPATCH byte_offset, value Allows any address in the IPXODI.COM file to be patched with any specified byte offset value. Syntax ipatch byte_offset, value Default None Example To patch a byte offset value in the IPXODI.COM file, you could place the following lines in your NET.CFG file: protocol ipx ipatch 6775 IPX PACKET SIZE LIMIT number Reduces the maximum packet size (in bytes) set by each LAN driver.
NET.CFG Options Reference Protocol IPX Option Example To reduce the maximum packet size for an Ethernet ODI LAN driver from the default, you could place the following lines in your NET.CFG file: protocol ipx ipx packet size limit 1200 IPX RETRY COUNT number Sets the number of times the client workstation resends a packet. On networks that lose many packets, this retry count might need to be increased. The IPX protocol does not actually resend a packet.
NET.CFG Options Reference Protocol IPX Option A program developed to the IPX protocol standard, such as the LANSchool utility, might require more than the default number of sockets. Syntax ipx sockets number Replace number with the maximum number of sockets that IPX can have open at the client workstation. Default 20 Example To set the number of open sockets on a client workstation to 30, you would place the following lines in your NET.
NET.CFG Options Reference Protocol SPX Option Protocol SPX Option Use this option of the NET.CFG file to change the default value of parameters for the SPX protocol.
NET.CFG Options Reference Protocol SPX Option MINIMUM SPX RETRIES number Determines how many unacknowledged transmit requests are allowed before assuming the connection has failed. SPX applications have two methods of specifying a transmit retry count to SPX: • The application can specify a retry value at the time of connection. • If the application doesn’t specify a retry value, SPX uses the configured value setting for the IPX RETRY COUNT parameter (default is 20).
NET.CFG Options Reference Protocol SPX Option Syntax spx abort timeout number Replace number with a number of ticks. Default 540 (about 30 seconds) Example To set the amount of time (in ticks) that SPX waits before it terminates the session to 20 seconds, you would place the following lines in your NET.CFG file: protocol spx spx abort timeout 300 NOTE: There are approximately 18.21 ticks per second on IBM PCs and compatibles.
NET.CFG Options Reference Protocol SPX Option If SPX has not heard from the other side of the connection within this time, it sends packets to the other side asking for verification that the connection still exists. Syntax spx listen timeout number Replace number with a number of ticks. Default 108 (about 6 seconds) Example To set the amount of time (in ticks) that SPX waits before it requests a packet to 11 seconds, you would place the following lines in your NET.
NET.CFG Options Reference Protocol SPX Option NOTE: There are approximately 18.21 ticks per second on IBM PCs and compatibles.
NET.CFG Options Reference Protocol TCPIP Option Protocol TCPIP Option Use this option of the NET.CFG file to configure the TCP/IP protocol stack used by the TCPIP.EXE program. The TCPIP.EXE program reads the NET.CFG file for configuration information while loading. Run the TCP/IP Transport for DOS installation program provided on the TCP/IP Transport for DOS diskette to obtain a copy of the TCPIP.EXE file.
NET.CFG Options Reference Protocol TCPIP Option Category Additional Support Parameters and Values NO_BOOTP PATH TCP_CFG [[ drive: ]path [ ; ... ]] PROTOCOL TCPIP Specifies the protocol option you are making configurat ions for. Syntax protocol tcpip parameter_name value Replace parameter_name with the name of the parameter you want to use. Replace value with the value setting which corresponds with the parameter name.
NET.CFG Options Reference Protocol TCPIP Option You can set up client workstations to use either an Ethernet connection with a SLIP/PPP serial link or a network gateway machine with two network boards. Protocol TCPIP supports one network board and LAN driver per client workstation. BIND odi_driver [number frame_type network_name] Binds the TCP/IP protocol stack to a LAN driver.
NET.CFG Options Reference Protocol TCPIP Option Syntax (continued) Replace frame_type with the frame type used for your network connection. This value is the same as the frame value for the LINK DRIVER parameter. Replace network_name with a descriptive name for this network connection. The network name is used with the IP_ADDRESS, IP_ROUTER, and IP_NETMASK parameters to distinguish between the values for each network connection.
NET.CFG Options Reference Protocol TCPIP Option Parameters and Values IP_ADDRESS ip_address [network_name] IP_NETMASK net_mask_address [network_name] IP_ROUTER ip_address [network_name] IP_ADDRESS ip_address [network_name] Specifies the IP address for your client workstation. Syntax ip_address ip_address [network_name] Replace ip_address with the correct address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address.
NET.CFG Options Reference Protocol TCPIP Option IP_NETMASK net_mask_address [network_name] Specifies the default subnetwork mask if subnetworks are used. Syntax ip_netmask net_mask_address [network_name] Replace net_mask_address with the correct subnetwork mask address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address. Replace network_name with a descriptive name for this network connection.
NET.CFG Options Reference Protocol TCPIP Option IP_ROUTER ip_address [network_name] Specifies the default router address for all packets being sent to remote networks. All other gateways are dynamically discovered using the ICMP redirect mechanism. Syntax ip_router ip_address [network_name] Replace ip_address with the correct address in dotted notation. If this parameter is missing or is 0.0.0.0, the protocol stack uses BOOTP or Reverse ARP to determine the IP address.
NET.CFG Options Reference Protocol TCPIP Option Parameters and Values TCP_SOCKETS number UDP_SOCKETS number RAW_SOCKETS number Transmission Control Protocol (TCP) Sockets Transmission Control Protocol (TCP) sockets are used to support concurrent TCP connections. If you configure multiple ODI LAN drivers for TCP/IP and anticipate using applications that make heavy concurrent use of sockets, modify the number of TCP sockets by configuring the TCP_SOCKETS parameter value to a larger number.
NET.CFG Options Reference Protocol TCPIP Option User Datagram Protocol (UDP) Sockets User Datagram Protocol (UDP) sockets are used by the LWPCON utility and by all applications that query a name server using the domain name system (DNS). DNS name servers are the only type of name server that the TCP/IP Transport for DOS software supports. The software accesses a DNS name server through the information provided in the RESOLV.CFG file.
NET.CFG Options Reference Protocol TCPIP Option Raw Sockets One raw socket is required when using the PING utility, the LWPCON utility, or other applications that have ping functions. The default NET.CFG file configured by the TCP/IP Transport for DOS installation program provides for eight TCP sockets, eight UDP sockets, and one raw socket. These default values are sufficient for most configurations.
NET.CFG Options Reference Protocol TCPIP Option Additional Support Use these parameters and values to configure your client workstation’s boot process and path to client workstation configuration files, as discussed on the following pages: Parameters and Values NO_BOOTP PATH TCP_CFG [[ drive: ]path [ ; ...
NET.CFG Options Reference Protocol TCPIP Option PATH TCP_CFG [[ drive: ]path [ ; ... ]] Specifies the directories that contain the database configuration files HOSTS, NETWORKS, PROTOCOL, SERVICES, and RESOLV.CFG. The syntax is the same as the DOS PATH command. Syntax path tcp_cfg [[drive:] path [; ...]] Replace drive with the letter of the drive where the database configuration files exist. Replace path with the directory path to the location of the database configuration files.
NET.CFG Options Reference Transport Provider IPX | UDP Option Transport Provider IPX | UDP Option The Desktop SNMP transport providers, STPIPX.COM and STPUDP.COM, read the configuration file to discover trap targets on NetWare networks. Use this option of the NET.CFG file to specify the trap target address for your SNMP desktops. For more information, see “Desktop SNMP Option.
NET.CFG Options Reference Transport Provider IPX | UDP Option TRAP TARGET ipxaddress | ipaddress Trap targets define the addresses that the SNMP manager sends SNMP traps to. To receive traps sent by Desktop SNMP, make sure your management workstation address is listed in the IPX (for IPX transport) or UDP (for UDP/IP transport) section of the NET.CFG file. NOTE: If you do not configure at least one trap target, Desktop SNMP does not send traps.
NET.
3 Command Line Parameters Reference 3-1
Command Line Parameters Reference Overview Overview This chapter contains a listing of command line parameters for the NetWare® Client™ for DOS and MS Windows software.
Command Line Parameters Reference Introduction Introduction The command line parameters for the NetWare Client software are used to specify nondefault value settings for NetWare Client software configuration options. Command line parameters require a specific syntax format. The following example and table explain these syntax format conventions. PROGRAM_NAME /parameter [option] Convention Explanation PROGRAM_NAME Uppercase words. Type these words as shown.
Command Line Parameters Reference Core NetWare Client Software Core NetWare Client Software The core NetWare Client software for the DOS and MS Windows environment are four terminate-and stay-resident (TSR) programs, listed and described in the following table. Table 3-1 Explanation of the Core NetWare Client Software Software IPXODI.COM (Internetwork Packet Exchange™ Open Data-Link Interface™) Explanation Delivers requests and replies between a client workstation and the network.
Command Line Parameters Reference Core NetWare Client Software Table 3-1 Explanation of the Core NetWare Client Software Software Explanation VLM.EXE NetWare DOS Requester DOS client software that provides the interface between DOS and the network. Is loaded when you run the STARTNET.BAT file. Consists of individual modules that provide various network services. Loads drivers that the NetWare DOS Requester needs in order to communicate with the network hardware.
Command Line Parameters Reference Core NetWare Client Software Parameter Mobile IPX Option /M Explanation Loads diagnostic responder and SPX. Disables /D and /A values. Requires NESL.COM be loaded before loading IPXODI. Unload /U Unloads IPXODI.COM file from memory. The syntax for using these parameters is as follows: IPXODI [option] Following is an example of an IPXODI command that you could execute at a client workstation: IPXODI /D /C=C:\NWCLIENT\NET.
Command Line Parameters Reference Core NetWare Client Software Following is an example of an LSL command that you could execute at a client workstation: LSL /C=C:\NWCLIENT\NET.CFG This command indicates the following: • The NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory. ODI LAN driver.COM Use the following command line parameters to manage the LAN driver software. Parameter Option Explanation Help /? Displays help screen. Unload /U Unloads ODI LAN driver.
Command Line Parameters Reference Core NetWare Client Software Parameter Configuration File Option /C Explanation Indicates alternate filename for configuration information. /C = [path\]filename Conventional Memory /MC Uses conventional memory when loading VLM.EXE file. Diagnostics /D Displays VLM.EXE file diagnostics. Expanded Memory /ME Uses expanded memory when loading VLM.EXE file. Extended Memory /MX Uses extended memory when loading VLM.EXE file. Help /? Displays help screen.
Command Line Parameters Reference Core NetWare Client Software This command indicates the following: • Diagnostic information is displayed. • The NetWare Client configuration file is NET.CFG in the C:\NWCLIENT directory. • SALES is the preferred server connection. • The VLM software is loaded into conventional memory.
Command Line Parameters Reference DOSNP Software DOSNP Software Use the following command line parameters for managing the DOSNP software. Parameter Option Explanation Help /? Displays help screen. Unload /U Unloads file from memory. Version /I Displays version and load information.
4 System Messages A system message points to a software or hardware error that doesn’t allow further processing.
System Messages An explanation of the nature of the message and a recommended course of action follow each message. AUTO-1.00-1: The message file is invalid. The program cannot be loaded. Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version. Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS Requester™ software uses the default messages that are bound to the binary files.
System Messages Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. AUTO-1.00-43: There is a missing or invalid ON/OFF value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.
System Messages Explanation: The .VLM file requires that the .VLM file be loaded first. Either the current configuration has .VLM and .VLM loading out of order, or .VLM did not load successfully. Action: Make sure that .VLM is configured to load before .VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file. BIND-1.00-7: In order to load the .VLM, one of the following VLMs must be loaded: .
System Messages BIND-1.00-45: The parameter specified for the following option was out of range and has been adjusted. Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message. Action: Check and correct the parameter specified in the NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information. CONN-1.00-1: The message file is invalid. The program cannot be loaded. Explanation: The .
System Messages CONN-1.00-42: There is a missing or invalid value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing. Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process. Action: No action is required at this point. However, to avoid this message the next time the VLM.
System Messages CONN-1.00-51: An older version of the shell is loaded. The NetWare Requester for DOS cannot be loaded. Unload the shell; then load the NetWare Requester for DOS files. Explanation: The NetWare® DOS Requester™ software cannot be loaded with the NetWare shell. The NetWare shell has been loaded in your machine. For NetWare shell compatibility. Action: Type “NETX /U” to unload the NetWare shell.
System Messages Action: Delete unnecessary files from the hard disk. DOSCLINST-1.0-3: The INSTALL.OVL file could not be found. Explanation: The INSTALL.OVL file could not be found. This file is an integral piece of the INSTALL utility; it must be in the same directory as the INSTALL.EXE file. Action: Make sure that INSTALL.OVL is in the same directory as the INSTALL.EXE file; then run INSTALL again. DOSCLINST-1.0-4: A read error occurred while the program was reading INSTALL.OVL.
System Messages Explanation: The .VLM file requires that the .VLM or .VLM file be loaded first. Either the current configuration has .VLM loading before .VLM or .VLM, or .VLM or .VLM did not load successfully. Action: Make sure that .VLM or .VLM loads successfully before .VLM. FIO-1.00-42: There is a missing or invalid value for ‘’ on line of the configuration file.
System Messages FIO-1.00-60: Too much cache is configured. The FIO.VLM file will reduce the cache blocks by blocks and load successfully. Check the CACHE BUFFERS and BUFFER SIZE parameters in the NET.CFG file; then load the FIO.VLM file. Explanation: The amount of cache available in DOS is limited by conventional memory. Neither of the parameters determining the amount of memory to be used, CACHE BUFFERS nor BUFFER SIZE, can be configured to use more than 64 KB of memory.
System Messages Action: If you want Packet Burst, make sure that the LSL.COM file is loaded before the NetWare DOS Requester. If you do not want Packet Burst, add PB BUFFERS=0 to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information. FIO-1.00-63: The IPX socket for packet burst could not be opened. The FIO.VLM file will load successfully without packet burst support. configure the IPXODI.COM file for enough sockets in the NET.
System Messages FIO-1.00-65: The NetWare DOS Requester is being loaded in a MS Windows DOS box. The FIO.VLM file will load successfully without packet burst support. Explanation: This message is only a warning. The NetWare® DOS Requester™ software functions properly without the use of the Packet Burst™ protocol. Packet Burst, which is a part of the FIO.VLM file, cannot function when loaded in an MS Windows DOS box. Action: You can use Packet Burst if it is loaded before starting MS Windows.
System Messages Action: Make sure that .VLM or .VLM loads successfully before .VLM. GENERAL-1.00-42: There is a missing or invalid value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing. Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.
System Messages Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS Requester™ software uses the default messages that are bound to the binary files. IPXNCP-1.00-5: .VLM is not loaded. The .VLM file cannot be loaded before .VLM. Load the .VLM file first then try to load the .VLM file. Explanation: The .VLM file requires that the .VLM file be loaded first. Either the current configuration has .
System Messages Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process. Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. IPXNCP-1.
System Messages IPXNCP-1.00-55: The IPX interface does not support checksums. The IPXNCP.VLM file will load successfully without using checksums. Make sure the installed IPXODI. COM is version 2.01 or later and that it is not bound to a board configured to use the ETHERNET_802.3 frame format. Explanation: The IPXNCP.VLM file loads without supporting checksums. For checksum to be supported in IPXNCP.VLM, the loaded IPXODI.COM file must support checksums. Either the loaded version of the IPXODI.
System Messages Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version. Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS Requester™ software uses the default messages that are bound to the binary files. NDS-1.00-5: .VLM is not loaded. The .VLM file cannot be loaded before .VLM. Load the .VLM file first then try to load the .VLM file.
System Messages NDS-1.00-43: There is a missing or invalid ON/OFF value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing. Explanation: The configuration file contains a parameter that is defined to use either an ON or OFF value, but a different value or no value has been specified. This invalid line is ignored by the configuration process. Action: No action is required at this point.
System Messages Action: Make sure that .VLM is configured to load before .VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file. NETX-1.00-7: In order to load the .VLM, one of the following VLMs must be loaded: .VLM, .VLM. Explanation: The .VLM file requires that the .VLM or .VLM file be loaded before .VLM can run effectively. Either the current configuration has .
System Messages Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message. Action: Check and correct the parameter specified in the NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information. NETX-1.00-57: DOS is only configured for drives, NETX.VLM requires 26 drives for full functionality. The NETX.VLM file will load with partial support. Add LASTDRIVE=Z to the CONFIG.
System Messages NMR-1.00-5: .VLM is not loaded. The .VLM file cannot be loaded before .VLM. Load the .VLM file first then try to load the .VLM file. Explanation: The .VLM file requires that the .VLM file be loaded first. Either the current configuration has .VLM and .VLM loading out of order, or .VLM did not load successfully. Action: Make sure that .VLM is configured to load before .VLM.
System Messages Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. NMR-1.00-45: The parameter specified for the following option was out of range and has been adjusted. Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message. Action: Check and correct the parameter specified in the NET.
System Messages Explanation: The NetWare® MS Windows driver (NETWARE.DRV) allocates temporary drives on the server to perform some functions. Action: Contact the network supervisor to make sure that NetWare is running and the server is operating correctly. NWP-1.00-1: The message file is invalid. The program cannot be loaded. Explanation: The .MSG file is invalid. This problem could be the result of a corrupted file, a bad translation, or an outdated file version. Action: Either update the .
System Messages Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process. Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. NWP-1.00-43: There is a missing or invalid ON/OFF value for ‘’ on line of the configuration file.
System Messages Action: If you want NCP authentication, make sure that SECURITY.VLM is configured to load before NWP.VLM and that it loads successfully before attempting to load NWP.VLM. If you do not want NCP authentication, add SIGNATURE LEVEL=0 to the NetWare DOS Requester section of the NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information. REDIR-1.00-1: The message file is invalid. The program cannot be loaded. Explanation: The .MSG file is invalid.
System Messages Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process. Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. REDIR-1.00-43: There is a missing or invalid ON/OFF value for ‘’ on line of the configuration file.
System Messages Explanation: The .VLM file requires that the .VLM file be loaded first. Either the current configuration has .VLM and .VLM loading out of order, or .VLM did not load successfully. Action: Make sure that .VLM is configured to load before .VLM. To do this, change the load order of the VLM= parameter in the NET.CFG file. RSA-1.00-7: In order to load the .VLM, one of the following VLMs must be loaded: .
System Messages RSA-1.00-45: The parameter specified for the following option was out of range and has been adjusted. Explanation: A configurable parameter has been configured too high or too low to be valid. The parameter is specified on the line following the message. Action: Check and correct the parameter specified in the NET.CFG file. See Chapter 2, “NET.CFG Options Reference,” for more information. SECURITY-1.00-1: The message file is invalid. The program cannot be loaded. Explanation: The .
System Messages SECURITY-1.00-42: There is a missing or invalid value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing. Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process. Action: No action is required at this point. However, to avoid this message the next time the VLM.
System Messages Explanation: This message is only a warning. The NetWare® DOS Requester™ software functions properly without the NetWare Core Protocol™ (NCP) authentication. The SECURITY.VLM file must be loaded before any NetWare protocol modules (BIND.VLM or NDS.VLM) to function properly. Action: If you want NCP™ authentication, load the SECURITY.VLM after TRAN.VLM and before any NetWare protocol module (BIND.VLM or NDS.VLM); then set the SIGNATURE LEVEL= parameter in the NET.CFG file.
System Messages Action: Make sure that .VLM or .VLM loads successfully before .VLM. TRAN-1.00-42: There is a missing or invalid value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing. Explanation: The configuration file contains a parameter that has an invalid value or that does not specify a value. This invalid line is ignored by the configuration process.
System Messages Action: Either update the .MSG file with a valid copy or delete the file. The NetWare® DOS Requester™ software uses the default messages that are bound to the binary files. VLM-1.00-8: The VLM.EXE file is already loaded. VLM.EXE cannot be reloaded. If you want to load VLM.EXE with a different configuration, unload VLM.EXE first with the /U parameter and then try loading the VLM.EXE file. Explanation: The VLM.EXE file has already been loaded into memory.
System Messages Explanation: The VLM.EXE file can use expanded memory (EMS), extended memory (XMS), or conventional memory. The VLM.EXE file has determined that there is not enough of any one of these types of memory to support loading the VLM™ files. Action: Check the amount of all memory available. Some memory managers provide dynamic memory pools by converting extended memory to expanded memory or vice versa. Other memory managers require you to configure the amount and type of memory you want.
System Messages Explanation: The NetWare® DOS Requester™ software cannot function properly when loaded after a task switcher. A task switcher has been previously loaded. (Task switchers include DR DOS® TaskMax, MS-DOS* 5.0 DOSSHELL, and MS Windows 3.1 in standard mode.) Action: Unload the task switcher before attempting to load the NetWare DOS Requester. VLM-1.00-31: Network error on server . Check network cabling or server status.
System Messages VLM-1.00-34: The loaded VLM.EXE file indicates it is unsafe to execute an unload for VLM number . VLM.EXE will not be unloaded. Unload all memory resident programs (TSRs) that were loaded after the VLM.EXE file and then try to unload VLM.EXE. Explanation: An attempt was made to unload the VLM.EXE file using the / U parameter. The loaded VLM.EXE file refused to unload. This usually is caused by interrupts being used after the VLM.EXE file was loaded.
System Messages load the VLM™ programs. The VLM.EXE file attempts to use an alternate type of memory, either expanded (EMS) or conventional, before failing to load. Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, either make sure an extended memory manager is loaded with sufficient memory, or do not specify the / MX parameter when loading VLM.EXE. VLM-1.00-39: The VLM.EXE file is using extended memory (XMS).
System Messages Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message. VLM-1.00-43: There is a missing or invalid ON/OFF value for ‘’ on line of the configuration file. This entry will be ignored. Correct the line specified in the configuration file before continuing.
System Messages Explanation: The VLM™ programs for the NetWare® DOS Requester™ software have been improperly configured to include two programs with the same VLM ID. This can be caused by either a VLM being included twice in the VLM= parameter list, or by a VLM attempting to reuse a VLM ID assigned to a different VLM. Action: Check the NET.CFG file for duplicates in the VLM list. Make sure that the USE DEFAULTS= parameter is set to OFF. See Chapter 2, “NET.CFG Options Reference,” for more information.
System Messages Action: No action is required at this point. However, to avoid this message the next time the VLM.EXE file is loaded, delete or correct the line specified by the error message.
System Messages 4-40
Index A ALTERNATE Link driver option parameter, explained, 2-28 Asynchronous Timeout Connections (Desktop SNMP NET.CFG option category) parameters, listed and explained 2-14.
Index Domain Name System (DNS) UDP socket requirements, 2-122 DOS conventions, explained command, v file, path, and directory names, v DOS NAME NetWare DOS Requester option parameter, explained, 2-72 DOS Requester.
Index LOCK DELAY NetWare DOS Requester option parameter, explained, 2-81 LOCK RETRIES NetWare DOS Requester option parameter, explained, 2-81 LONG MACHINE TYPE NetWare DOS Requester option parameter, explained, 2-82 LSL.
Index command example, 3-7 explained, 3-4 parameters and values, listed and explained, 3-7 Optimizing NetWare Client software memory usage, 2-59 security, 1-8, 1-15 speed, 1-4, 2-57 Options. See NET.CFG options P Packet forgery, preventing, 1-8 sending large, over network, 1-5 signature (see NCP packet signature) Packet Burst disabling, 1-5 memory requirements, 1-4 using, to increase client speed, 1-4 when to use, 1-5 Parameters. See BIND parameters; Command line parameters; NET.
Index T TCP/IP groups, MIB-II support (Desktop SNMP NET.CFG option) example NET.CFG file using, 2-26 explained, 2-26 TCP/IP Transport for DOS software explained, 2-114 name servers supported by, 2-122 TCP_SOCKETS Protocol TCPIP option parameter, explained, 2-121 TCPIP.EXE program, specifying NET.CFG file location to, 2-114 Third-party NLM problems, troubleshooting, 1-14 Transport Provider IPX | UDP NET.
Index I-6
