                       LAN WorkGroup v4.1
                  Configuring the NET.CFG File
                           NETCFG.TXT

Copyright (c) 1993 Novell, Inc.   All Rights Reserved.

THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND
TREATIES.  NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED,
COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED,
CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST,
TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF
NOVELL, INC.  ANY USE OR EXPLOITATION OF THIS WORK WITHOUT
AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL
LIABILITY.

This release document includes the following sections:

     INTRODUCTION
     SHARED NET.CFG FILE ON THE LAN WORKGROUP SERVER
     CLIENT WORKSTATION CONFIGURATION
     CLIENT WORKSTATION MEMORY
     CONFIGURING DISKLESS WORKSTATIONS
     CLIENT NET.CFG FILE
     EDITING THE NET.CFG FILE
     LINK DRIVER SECTION
     LINK SUPPORT SECTION
     PROTOCOL TCPIP SECTION
     OTHER PROTOCOL SECTIONS
     EXAMPLE NET.CFG CONFIGURATIONS
     RELATED README FILES

Please use the search features of your text editor to jump directly
to a section of interest.


INTRODUCTION:
~~~~~~~~~~~~

This file provides detailed technical information for experienced
users who want to customize the operation of their link drivers,
LSL, and TCP/IP Transport software by manually editing the NET.CFG
file.  It is intended for use by experts only.

The NET.CFG file is used to supply configuration parameters to a
variety of programs in addition to those mentioned above.  For LAN
WorkGroup, the LWGCON server utility and the WGSETUP client
workstation configuration program automate NET.CFG configuration
for the majority of users.  You should not need to edit the NET.CFG
file directly unless you have an unusual, custom, or complex
workstation configuration that is not easily dealt with using the
automated administration tools.

Novell strongly recommends that users administer NET.CFG via LWGCON
and WGSETUP whenever possible.  LWGCON allows you to set up custom
Link Driver and Link Support parameters in multiple-user
workstation profiles.

If you choose to edit the NET.CFG file manually, exercise caution
in modifying entries created and maintained by WGSETUP.  Maintain
backup copies and test your modifications rigorously.

Further information about the NET.CFG file is available in the
following publications:

     The LAN WorkPlace Administrator's Guide (details about
     SLIP_PPP.COM, IPTUNNEL, NETBIOS, and the SNMP agent).

     The NetWare Workstation for DOS manual (link drivers).

     The LAN WorkPlace Configuration Guide (configuration details
     that can be adapted for use with LAN WorkGroup).

For experienced users who want to adapt the NET.CFG file for a
specific purpose, this file provides most of the required technical
detail.  The LAN WorkPlace for DOS Administrator's Guide provides
detailed information about the optional features that are
available.

===================================================================

SHARED NET.CFG FILE ON THE LAN WORKGROUP SERVER:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The shared NET.CFG file is in the <vol>:NET directory on the
workgroup server; <vol> is the volume on the server where the
shared LAN WorkGroup software is installed.  This file is created
by LWGCON when you save the LAN WorkGroup Parameters form.  It
contains only the Protocol TCPIP section with PATH statements for
SCRIPT, PROFILE, LWP_CFG, and TCP_CFG.

LWGCON restricts the PATH statements to two directories each.  The
first must always be the private directory.  The second must always
be the shared directory.  When LWGCON next writes the NET.CFG file,
any other directories are lost.

No Link Driver or Link Support sections can be placed in the
server's NET.CFG file.  These sections are only used if they are in
the private workstation NET.CFG file.  These sections are read by
the link drivers and LSL.COM, which must be loaded BEFORE access to
the NetWare server is established.

Additional TCP/IP parameters and other NET.CFG fields should be
placed in the private workstation NET.CFG file.  If you are adding
workstation specific Protocol TCPIP section parameters to a private
workstation NET.CFG file, also include the PATH statements in the
shared NET.CFG file AND remove the -C=<drive>:NET\NET.CFG command-
line argument from the WGTCPIP command in the workstation LANWG.BAT
file.  This directs WGTCPIP to use the workstation NET.CFG file,
instead of the shared NET.CFG file, to set the TCP/IP parameters.

===================================================================

CLIENT WORKSTATION CONFIGURATION:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The LAN WorkGroup client installation program sets up a
workstation's configuration so that the user can immediately begin
using the applications and utilities provided by LAN WorkGroup.
However, if a workstation has a customized configuration, or if you
want to take advantage of some of the optional LAN WorkGroup
features, you may want to make changes to your client workstation
configuration.

LAN WorkGroup is very flexible in allowing you to both standardize
and customize your configuration.  On the server you can set up a
standard configuration that can be used by the client workstations.
You can then configure all workstations to use the same standard
approach, or each workstation can configure individual features and
capabilities, overriding the standard configuration from the
server.

This file describes how to customize your client workstation
configuration and provides several example configurations.

===================================================================

CLIENT WORKSTATION MEMORY:
~~~~~~~~~~~~~~~~~~~~~~~~~

Because some of the utilities in LAN WorkGroup (for example,
LWPCON) require a large block of conventional DOS memory, you might
want to reconfigure your workstation's memory after installing LAN
WorkGroup.  If you have DOS v5.0 (or later), or you have a memory
manager program for an earlier DOS version, you can successfully
run many of the LAN WorkGroup drivers and programs in upper memory.

Running these programs in upper memory generally involves making
changes to their load commands in your CONFIG.SYS, AUTOEXEC.BAT, or
LANWG.BAT file.  Refer to your DOS v5.0 or memory manager
documentation for the specific procedures.  It is advisable to move
programs into upper memory one at a time, restarting the
workstation and verifying correct operation after each change.

The following drivers and programs may run successfully in upper
memory, depending on your configuration:

     ANSI.SYS driver (loaded by CONFIG.SYS)

     LSL.COM (loaded by LANWG.BAT)

     Network board link driver (loaded by LANWG.BAT)

     IPXODI.COM (loaded by LANWG.BAT)

     NETX.COM (loaded by LANWG.BAT; alternatively you can install
     NETX.EXE, BNETX.EXE, XMSNETX.EXE or EMSNETX.EXE)

     EMSNETX.EXE cannot be used in Windows standard mode.

     WGTCPIP.EXE (loaded by LANWG.BAT)

===================================================================

CONFIGURING DISKLESS WORKSTATIONS:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This section explains all of the special considerations that are
required to set up a diskless workstation.

When the system administrator configures a diskless workstation to
start up (boot) and access NetWare, a boot image is created
containing specific startup information for that workstation.  When
the diskless workstation is booted via Remote Program Load (RPL),
this boot image is downloaded to the workstation.

The boot image is created and customized using the NetWare DOSGEN
utility.  This process is described in Appendix D of the NetWare
Version 3.11 Installation manual.

The boot image contains instructions to load the diskless
workstation's link driver and LSL.  As a result, WGSETUP does not
create or modify a private client NET.CFG file for a diskless
workstation.  If you want to update the link driver and LSL used by
the workstation to newer versions provided by LAN WorkGroup, you
must manually copy the files from the workgroup server to the
diskless workstation's private directory, then update the boot
image as needed using DOSGEN.

If you want WGTCPIP.EXE to use a private client NET.CFG file for
its configuration parameters, you must create a NET.CFG file as
described in this file, then modify the diskless workstation's
WGTCPIP command line in LANWG.BAT to access the private NET.CFG
file.  This process is described in the section "Using the Client
NET.CFG File."

Because a diskless workstation does not have an accessible
AUTOEXEC.BAT file, WGSETUP cannot modify this file to run the
LANWG.BAT file.  WGSETUP creates a LANWG.BAT file on the diskless
workstation's private client drive.  This LANWG.BAT file does not
contain commands to load the link driver and LSL, because this
information is configured in the workstation's boot image.

To run LANWG.BAT automatically, loading the networking software
whenever the diskless workstation is booted, add a command similar
to the following as the last line of the remote program load (RPL)
AUTOEXEC.BAT file:

    M:\LANWG.BAT

Include the mapped drive letter and full path to the user's
LANWG.BAT file in this command.

===================================================================

CLIENT NET.CFG FILE:
~~~~~~~~~~~~~~~~~~~

The client configuration procedure creates or modifies the client
NET.CFG file in the root directory of your startup (boot) drive.
The configuration program (WGSETUP) uses the information placed in
the WGSETUP.CFG file by LWGCON to provide the minimum NET.CFG
settings required to run the LAN WorkGroup software.  You can
further customize your workstation's NET.CFG file to enable
optional LAN WorkGroup features and accommodate specialized network
features.


Using the Client NET.CFG File:
*****************************

The TCP/IP Transport software, WGTCPIP.EXE, can be configured to
use either the shared server NET.CFG file or the private client
NET.CFG file to obtain its configuration parameters.

When you restart your workstation, the NET.CFG file in the root
directory of your startup (boot) disk is used by your link driver
and LSL.COM to obtain their configuration parameters.  Diskless
workstations get this information from the boot image.

By default, your LANWG.BAT file runs WGTCPIP.EXE using the shared
server NET.CFG file.  If you customize your client workstation
NET.CFG file to include parameter settings for WGTCPIP, you must
change the WGTCPIP command line in LANWG.BAT.

To use a customized client workstation NET.CFG file instead of the
shared NET.CFG file on the workgroup server, change the WGTCPIP.EXE
command line in your workstation's LANWG.BAT file to the following:

    WGTCPIP.EXE -C=C:\NET.CFG

Substitute your workstation's boot drive if different from the C:
drive.  This change loads the TCP/IP Transport software using the
customized NET.CFG file on your workstation instead of the shared
server NET.CFG file (<vol>:NET\NET.CFG by default).


NET.CFG File Overview:
*********************

The NET.CFG file has three sections that are used by the LAN
WorkGroup software:

     Link Driver - configures Open Datalink Interface (ODI) drivers
     (link drivers).  You can set up multiple drivers if you have
     more than one network board or want to run SLIP/PPP to use LAN
     WorkGroup over a COM port serial link.

     Link Support - determines the sizes of the LSL memory pool and
     buffers.  You can change these values to suit your network
     configuration and application usage.

     Protocol TCPIP - contains settings used by the LAN WorkGroup
     TCP/IP Transport software (WGTCPIP.EXE).  You can modify this
     section to support optional features.

The NET.CFG file is used by NetWare as well as LAN WorkGroup.  It
can contain additional Protocol sections to configure other
protocols, such as IPX.  For example, the Protocol RFCNBIOS section
specifies fixed NetBIOS-name-to-IP-address mappings, and the
IPTUNNEL driver makes use of the Protocol IPX section.  Both
configurations are described in the LAN WorkPlace for DOS
Administrator's Guide.  For instructions about configuring NET.CFG
for NetWare, refer to the NetWare Workstation for DOS manual.

The sections that follow explain the NET.CFG format and discuss
NET.CFG settings that you can customize in the Link Driver, Link
Support, and Protocol TCP/IP sections.  Interaction between the
shared NET.CFG file on the workgroup server and the private client
NET.CFG file is also covered.  These discussions are followed by a
selection of example configurations.

===================================================================

EDITING THE NET.CFG FILE:
~~~~~~~~~~~~~~~~~~~~~~~~

If you want to change your configuration at any time, you can use a
DOS text editor, such as DOS 5.0 EDIT, to update this file.  The
NET.CFG file uses the following format:

     Section headings start at the beginning of a line (first
     column) and precede the parameter settings that apply to the
     section:

        Section Heading

     Parameter settings listed under each section heading are
     indented with a tab or one or more spaces:

        Section Heading
           Parameter setting parameter value(s)

     Type numbers for parameter values in decimal notation unless
     directed otherwise.

     Section headings and parameter settings can be typed in any
     combination of uppercase and lowercase letters.

     Comments can be added to the file by preceding them with a
     number sign (#) or semicolon (;).

     Each line ends with a carriage return.

After changing NET.CFG, you might also need to change your
LANWG.BAT file to load any new drivers you are configuring.  The
drivers read the information in NET.CFG when they are loaded into
memory.  For your NET.CFG changes to take effect, restart your
workstation to load the drivers and the TCP/IP Transport software
using the new NET.CFG information.

===================================================================

LINK DRIVER SECTION:
~~~~~~~~~~~~~~~~~~~

The Link Driver section is used for naming your link driver or
drivers and specifying various hardware and software settings for
each driver.  The installation program sets up the Link Driver
section for your network board using the parameter settings
necessary to run the LAN WorkGroup software.  Other settings are
optionally available to configure the board and its driver for use
by other software.

Below is a summary of the available Link Driver settings.


Link Driver drivername

     Section heading for Open Datalink Interface (ODI) driver
     drivername.  This heading is followed by parameter settings
     that apply to this driver.  The drivername parameter is the
     name of the link driver file.  For example, if the driver file
     is NE2000.COM, drivername is NE2000.

Int [ #1 | #2 ] IRQ_number

     Specifies the hardware interrupt number, IRQ_number, used by
     the network board.

     The Int parameters are as follows:

       [ #1 | #2 ]

     Optionally specifies which network board channel you are
     configuring.  Use this parameter only if you are configuring
     both communications channels on a board that supports two
     channels, or two network boards of the same type.

       IRQ_number

     Decimal interrupt request number.

Port [ #1 | #2 ] address [ ports ]

     Specifies the starting port address and number of ports used
     by the board.

     The Port parameters are as follows:

       [ #1 | #2 ]

     Optionally specifies which network board channel you are
     configuring.  Use this parameter only if you are configuring
     both communications channels on a board that supports two
     channels, or two network boards of the same type.

       address

     Address, in hexadecimal, of the hardware port to use or the
     first port in a range of ports.

       [ ports ]

     Number of ports in the range, in hexadecimal.

DMA [ #1 | #2 ] channel

     Specifies the DMA channel to be used by the network board.

     The DMA parameters are as follows:

       [ #1 | #2 ]

     Optionally specifies which network board channel you are
     configuring.  Use this parameter only if you are configuring
     both communications channels on a board that supports two
     channels, or two network boards of the same type.

       channel

     Decimal DMA channel number.

Mem [ #1 | #2 ] address [ length ]

     Specifies the range of DOS conventional memory to be reserved
     for use by the board.

     The Mem parameters are as follows:

       [ #1 | #2 ]

     Optionally specifies which network board channel you are
     configuring.  Use this parameter only if you are configuring
     both communications channels on a board that supports two
     channels, or two network boards of the same type.

       address

     Starting memory address, in hexadecimal.

       length

     Length of the memory segment, in hexadecimal.

Slot number

     For MCA boards, specifies the number, in decimal, of the slot
     into which you inserted the network board.  This setting is
     required only if your workstation has more than one board of
     the same type.

Connector DIX

     For the 3C503.COM driver, configures the board to use the DIX
     (thick Ethernet) connector.  If this setting is not included,
     the BNC/TP (thin) connector is used.

Node Address address

     MAC address for the board, in hexadecimal.  This setting
     overrides the hard-coded node address in the network board, on
     boards that allow this software override.

Frame frame_type

     Specifies the frame type used by the network board.  This
     setting can be included more than once for boards and drivers
     that support multiple frame types.

Protocol name protocol_ID frame_type

     Specifies the network protocol to be supported by the ODI
     driver.

     The Protocol parameters are as follows:

       name

     Name of the network protocol to be supported.

       protocol_ID

     Hexadecimal ID number assigned to this protocol (the ID
     numbers are listed later in this file).

       frame_type

     Frame type used by this protocol.  See the preceding Frame
     setting.

SAPS number

     For the LANSUP.COM driver, specifies the number, in decimal,
     of Service Access Points (SAPs) needed.  The default if this
     setting is not included is 1 service access point.

Link Stations number

     For the LANSUP.COM driver, specifies the number of link
     stations needed, in decimal.  The default if this setting is
     not included is 1 link station.

Alternate

     If you are using more than one network board, specifies that
     the driver use the alternate board instead of the primary
     board.  The primary board is used if this setting is not
     included.  This setting is used only by the LANSUP.COM,
     TOKEN.COM, and PCN2L.COM drivers.

Max Frame Size number

     Specifies the maximum number of bytes, in decimal, that the
     ODI driver can put in a network packet.

The Link Driver settings used for each driver vary according to the
board's hardware interface, its hardware capabilities, and the
software capabilities it can support.  Below is a table that
identifies the Link Driver parameters used for selected network
board drivers included with the LAN WorkGroup software, according
to the workstation hardware interface (bus) used to install the
network board.


  Driver         DMA         Int       Mem        Port       Slot

  3C1100.COM     --         --         --         --         --
  3C501.COM      --         ISA, MCA   --         ISA, MCA   --
  3C503.COM      --         ISA, MCA   ISA, MCA   ISA, MCA   --
  3C505.COM      ISA, MCA   ISA, MCA   --         ISA, MCA   --
  3C523.COM      --         --         --         --         MCA
  EXOS.COM       --         ISA, MCA   ISA, MCA   ISA, MCA   MCA
  LANSUP.COM     --         --         --         --         --
  NE1000.COM     --         ISA, MCA   --         ISA, MCA   --
  NE1500T.COM    ISA        ISA        --         ISA        --
  NE2-32.COM     --         --         --         --         MCA
  NE2.COM        --         --         --         --         MCA
  NE2000.COM     --         ISA        --         ISA        --
  NE2100.COM     ISA        ISA, MCA   --         ISA, MCA   --
  NE3200.COM     --         --         --         --         EISA
  PCN2L.COM      --         --         --         --         MCA
  TOKEN.COM      --         --         --         --         MCA
  TRXNET.COM     --         ISA        ISA        ISA        MCA

  Legend:

       ISA     Industry Standard Architecture interface.
       EISA    Extended ISA interface.
       MCA     Micro Channel Architecture.
       --      The parameter is not used by this driver.


Additional link drivers are available from third-party vendors.  If
you are using a link driver not listed above, refer to its
documentation for parameter applicability.

The sections that follow describe how to use each Link Driver
parameter.


Link Driver name

Each link driver that you configure has a separate Link Driver
section in your NET.CFG file.  Replace name with the executable
filename of the driver you are using, omitting the extension (for
example, NE2000 for NE2000.COM).

The following driver names are provided as part of the LAN
WorkGroup software:

  3C1100.COM     -- 3Com 3C1100 3Station (Ethernet)
  3C501.COM      -- 3Com EtherLink 3C501 (Ethernet)
  3C503.COM      -- 3Com EtherLink Series II (Ethernet)
  3C505.COM      -- 3Com EtherLink Plus (Ethernet)
  3C509.COM      -- 3Com 3C509 EtherLink III
  3C523.COM      -- 3Com EtherLink/MC (Ethernet)
  E20ODI.COM     -- Cabletron Systems Ethernet E20
  E21ODI.COM     -- Cabletron Systems Ethernet E21
  E2HODI.COM     -- Cabletron Systems Ethernet E2HUB
  E30ODI.COM     -- Cabletron Systems Ethernet E30xx
  E31ODI.COM     -- Cabletron Systems Ethernet E31, E31-X
  ES3210.COM     -- Racal-Datacom ES3210
  EXOS.COM       -- EXOS205 and EXOS215 (Ethernet)
  EXP16ODI.COM   -- Intel EtherExpress
  HPISAODI.COM   -- Hewlett-Packard PC Adapter 8, 16, and 16+
  HPMCAODI.COM   -- Hewlett-Packard MC Adapter 16
  IBMFDDIO.COM   -- IBM FDDI
  IBMODISH.COM   -- IBM PS/2 Ethernet Adapter
  ILANAT.COM     -- Racal-Datacom InterLan AT/XT
  INTEL593.COM   -- Intel LAN593
  INTEL596.COM   -- Intel LAN596
  LANSUP.COM     -- IBM LAN Support program (Token-Ring)
  LANZENET.COM   -- LANZENET Ethernet
  MADGEODI.COM   -- Madge Ringnode
  NCRWL05.COM    -- NCR WaveLAN
  NE1000.COM     -- Novell Ethernet NE1000 (Ethernet)
  NE1500T.COM    -- Novell Ethernet NE1500T (Ethernet)
  NE2_32.COM     -- Novell Ethernet NE2-32 (Ethernet)
  NE2.COM        -- Novell Ethernet NE2 (Ethernet)
  NE2000.COM     -- Novell Ethernet NE2000 (Ethernet)
  NE2100.COM     -- Novell Ethernet NE2100 (Ethernet)
  NE3200.COM     -- Novell Ethernet NE3200 (Ethernet)
  NI5210.COM     -- Racal-Datacom NI5210
  NI6510.COM     -- Racal-Datacom NI6510
  NI9210.COM     -- Racal-Datacom NI9210
  NTR2000.COM    -- Novell NTR2000 Token-Ring Adapter
  OSH391R.COM    -- Proteon p1319 RapiDrive
  OSH392R.COM    -- Proteon p1392 RapiDriver
  OSH89XR.COM    -- Proteon p189x RapiDriver
  OSH990R.COM    -- Proteon p1990 RapiDriver
  PCN2L.COM      -- IBM PC Network II and II/A (Token-Ring)
  ROUTE.COM      -- IBM Token-Ring (Token-Ring)
  SMC8000.COM    -- SMC EtherCard PLUS Family Adapter
  SMC8100.COM    -- SMC Token Ring EliteFamily Adapter
  SMCARCWS.COM   -- SMC PC/PS
  T20ODI.COM     -- Cabletron Systems Token-Ring T20
  T30ODI.COM     -- Cabletron Systems Token-Ring T30
  TCCARC.COM     -- Thomas-Conrad TC ARCnet/TCNS
  TCE16ATW.COM   -- Thomas-Conrad TC5045 Ethernet Adapter
  TCE16MCW.COM   -- Thomas-Conrad TC5046 Ethernet Adapter
  TCE32MCW.COM   -- Thomas-Conrad TC5046 Ethernet Adapter
  TCNSW.COM      -- Thomas-Conrad TC3042/TC3045/TC3046/TC3047 TCNS
  TCTOKSH.COM    -- Thomas-Conrad TC4035/TC4045/TC4046
  TOKEN.COM      -- IBM Token-Ring (Token-Ring)
  TRXNET.COM     -- Novell RX-Net and Turbo RX-Net (ARCnet)
  UBODI.COM      -- Ungermann-Bass NIUpc/ps, Personal NIU
  SLIP_PPP       -- Asynchronous serial ports (COMn:)


Int [ #1 | #2 ] IRQ_number

The Int setting (called IRQ, for interrupt request, by some
vendors) specifies which interrupt your network board uses.

For example, to specify interrupt 5 on an NE2000 board, place the
following lines in your NET.CFG file:

    Link Driver NE2000
      Int #1 5

To specify the IRQ_number for both of a board's communications
channels, use the following syntax in your NET.CFG file:

    Link Driver 3C505
      Int #1 2
      Int #2 3

You do not need to include the characters #1 if you are specifying
a value for only one network board communications channel.  For
example, if you are configuring only the first communications
channel on a 3C505 board, and this channel uses Interrupt 5, you
can place the following lines in your NET.CFG file:

    Link Driver 3C505
      Int 5

If, however, you are using more than one channel or network board,
each of which has an Int value, you must include the characters #1
for the first channel's value and #2 for the second channel's
value.

Port [ #1 | #2 ] address [ ports ]

Use the Port setting to specify the starting port (address, a
hexadecimal number) and the number of ports in the range (ports,
also hexadecimal).

For example, suppose you want to specify the starting port for the
first communications channel on your board.  The port address for
the board is 300.  Place the following lines in the NET.CFG file:

    Link Driver NE2000
       Port #1 300

The number of ports (ports) is optional.  The following example
specifies port ranges for both of a board's communications channels
with 32 ports (20 hexadecimal) in each range:

    Link Driver 3C505
       Port #1 300 20
       Port #2 700 20

You do not need to include the characters #1 if you are specifying
a value for only one network board communications channel.  For
example, if you are configuring only the first communications
channel on a 3C505 board, and this channel uses 32 ports starting
at address 300, you can place the following lines in your NET.CFG
file:

    Link Driver 3C505
       Port 300 20

If, however, you are using more than one channel or network board,
each of which has a Port address and range, you must include the
characters #1 for the first channel's values and #2 for the second
channel's values.


DMA [ #1 | #2 ] channel

The DMA (direct memory access) option specifies the hardware DMA
channel setting of the network board.  This option lets you
configure DMA channels by entering the channel number (channel, a
decimal number) to be used.  The default value is the first DMA
channel (channel = 1).

Do not confuse your workstation's DMA channels with the
communications channels on your network board.  Some network boards
have more than one network communications channel, each of which
can be connected to a separate network communications line.  DMA
channels, on the other hand, are a feature of your workstation.  A
set number of DMA channels are allocated among all of your
workstation's controller boards that make use of this facility.

For example, if the first communications channel on your board uses
DMA channel 3 and the second communications channel uses DMA
channel 4, place the following lines in your NET.CFG file:

   Link Driver 3C505
      DMA #1 3
      DMA #2 4

You do not need to include the characters #1 if you are specifying
a value for only one network board communications channel.  For
example, if you are configuring only the first communications
channel on a 3C505 board, and this channel uses DMA channel 3, you
can place the following lines in your NET.CFG file:

    Link Driver 3C505
       DMA 3

If, however, you are using more than one channel or network board,
each of which has a DMA value, you must include the characters #1
for the first channel's value and #2 for the second channel's
value.


Mem [ #1 | #2 ] address [ length ]

The Mem option specifies a range of conventional DOS memory to be
reserved for use by the network board.

Use the hexadecimal physical (absolute) address of the memory used
by the board for the address parameter.  This address must match
the starting address configured on the board.  Enter the optional
length parameter in hexadecimal paragraphs (a paragraph is 16
bytes) of the memory segment used by the board.

For example, if your board addresses the memory segment from D0000
to D4000, the starting address is D0000 and the range is 400
hexadecimal paragraphs.  You would place the following lines in
your NET.CFG file for an EXOS board:

    Link Driver EXOS
       Mem D0000 400

You do not need to include the characters #1 if you are specifying
a value for only one network board communications channel.  For
example, if you are configuring only the first communications
channel on a 3C505 board, and this channel uses memory address
C0000, you can place the following lines in your NET.CFG file:

    Link Driver EXOS
       Mem C0000

If, however, you are using more than one channel or network board,
each of which has a Mem value, you must include the characters #1
for the first channel's value and #2 for the second channel's
value:

    Link Driver EXOS
       Mem #1 C0000
       Mem #2 D0000

Some network boards, such as the 3C503 board, can be configured to
use either shared DOS memory (requiring a Mem setting) or their own
on-board memory.  Refer to the manufacturer's documentation for
your network board to determine how best to configure your board.


Slot number

In slot-based computers, the driver usually locates the board by
scanning through the slots in order from lowest to highest.  The
Slot option directs the driver to eliminate the scan and locate the
board in the specified slot.

Use the number of the slot into which you inserted the board for
the number parameter (a decimal value).  The slot number is usually
found on the back of the workstation.

For example, if you are using two NE/2 boards in the same
workstation and you insert one board into slot 1 and the other into
slot 2, place the following lines in your NET.CFG file:

    Link Driver NE2
       Slot 1

    Link Driver NE2
       Slot 2

You would then set up your LANWG.BAT file to load the NE2.COM
driver twice.  The Slot option directs the first NE2 driver loaded
to use the NE/2 board in slot 1 and directs the second NE2 driver
to use the NE/2 board in slot 2.


Connector DIX

The Connector DIX option configures the 3C503 LAN driver to use the
DIX (thick) connector.  BNC/TP (thin) is the default value.  To
specify the DIX connector, place the following lines in your
NET.CFG file:

    Link Driver 3C503
       Connector DIX

DIX can also be selected in the LANWG.BAT command line that loads
the 3C503.COM driver, as in the following example:

     3C503 -D


Node Address address

The Node Address option overrides any hard-coded Media Access
Control (MAC) addresses in the network board, if the board allows
it.  Use the address parameter to specify a hexadecimal address
number.

Changing the node address on a board can create conflicts with
other network boards.  Use the hardware-based node address whenever
possible.

The following example shows how to change the node address on a
3C523 board:

     Link Driver 3C523
        Node Address 0612D43


Frame frame_type

The Frame option enables the frame types used by the network board.
You can use this option more than once with network boards that
support multiple frame types.  For example, to enable the
ETHERNET_II frame type on an NE1000 board, place the following
lines in the NET.CFG file:

    Link Driver NE1000
       Frame ETHERNET_II

Use the following frame formats for TCP/IP networks:

     Ethernet -- ETHERNET_II or ETHERNET_SNAP

     Token Ring -- TOKEN-RING_SNAP
     
     IBM PCN2 -- IBM_PCN2_SNAP
     
     FDDI -- FDDI_SNAP

     ARCnet -- NOVELL_RX-NET

For OSI networks, use frame type ETHERNET_802.2.  For IPX networks,
Ethernet LAN drivers default to the ETHERNET_802.3 frame type;
token ring LAN drivers default to the TOKEN-RING frame type.

Below is a table that lists the network types that support each
NET.CFG frame type parameter.  Additional frame types are supported
by the SLIP_PPP driver; refer to the LAN WorkPlace for DOS
Administrator's Guide for more information.


                 Hex ID
Frame Type       Number  Ethernet  Token Ring  ARCnet   PCN  FDDI

ETHERNET_II      8137    Yes        --          --       --    --
ETHERNET_SNAP    8137    Yes        --          --       --    --
ETHERNET_802.2   E0      Yes        --          --       --    --
ETHERNET_802.3   0       Yes        --          --       --    --
TOKEN-RING_SNAP  8137    --         Yes         --       --    --
TOKEN-RING       E0      --         Yes         --       --    --
NOVELL_RX-NET    FA      --         --         Yes       --    --
IBM_PCN2_802.2   E0      --         --          --       Yes   --
IBM_PCN2_SNAP    8137    --         --          --       Yes   --
FDDI802.2        EO      --         --          --       --    Yes
FDDI_SNAP        8137    --         --          --       --    Yes

Legend:  PCN indicates PCN baseband; -- indicates frame type is not
supported on this network type; Yes indicates frame type is
supported.


Protocol name protocol_ID frame_type

The Protocol option lets existing link drivers handle new network
protocols.

Replace name with the name of the new protocol.

Replace protocol_ID with the hexadecimal protocol ID number that
the protocol is assigned.

Replace frame_type with the frame type that the new protocol ID
applies to.  Make sure the Link Driver section for this driver
contains a Frame setting enabling support of this frame type.

For example, if you want to use a new protocol XYZ with an NE/2-32
network board, the NET.CFG file has the following lines:

    Link Driver NE2-32
       Frame ETHERNET_SNAP
       Protocol XYZ 904A ETHERNET_SNAP


SAPS number

If you use the LANSUP.COM driver, you can specify the number (in
decimal) of service access points (SAPS) needed.  Set the SAPS
option to allow for all applications using the IBM LAN Support
program.  The maximum value depends on the type of network board
used.  The default value is 1 service access point.

The SAPS option is ignored if another application has already
opened the board before the LANSUP.COM driver was loaded.


Link Stations number

If you use the LANSUP.COM driver, you can specify the number (in
decimal) of link stations needed.  Set the Link Stations option to
allow for all applications using the IBM LAN Support program.  The
maximum value depends on the type of network board used.  The
default value is 1 link station.

The Link Stations option is ignored if another application has
already opened the board before the LANSUP.COM driver was loaded.


Alternate

Normally, the LANSUP, token ring, and PCN2L drivers have you
specify a primary board when you are using more than one board.
Use the Alternate option if you want your driver to use the
alternate board.

Specify Alternate under the appropriate driver section heading, as
follows:

    Link Driver LANSUP
       Alternate


Max Frame Size number

The Max Frame Size option sets the maximum number of bytes per
packet that can be put on the network by the link driver.

The TOKEN.COM driver's default maximum frame size is 4216 bytes.
However, if your network board has 8 KB of shared RAM available,
the default size is 2168 bytes.

The LANSUP.COM driver's default is normally 1144 bytes.  However,
if you are using the IBM LAN Support program with an Ethernet
device driver, the maximum size is 1496 bytes.

For TOKEN.COM and LANSUP.COM, the value for number (a decimal
value) must be a multiple of 8.  It must include the number of
bytes for the data packet (usually 1, 2, 4, or 8 KB), for network
board overhead (6 bytes), and for the largest possible header
(currently, 35 bytes for the LAN header + 5 bytes for the SNAP
header + 74 bytes for the protocol header = 114 bytes).

For 2 KB data packets, for example, number is calculated as
follows:

    (data packet) + (header) + (constant)

        2048      +   114    +     6        = 2168

If the number supplied is not a multiple of 8, the TOKEN.COM driver
rounds the total up to the next multiple of 8.

The NET.CFG file for the TOKEN.COM driver using a maximum frame
size of 2168 has the following lines:

    Link Driver TOKEN
       Max Frame Size 2168

When the driver loads, the sign-on message does not reflect the 6
bytes of overhead.  Therefore, the Max Frame Size for the preceding
example is displayed as 2162.

If the line speed is 16 Mbps, the value for number can be between
632 and 17,960 bytes.  If the line speed is 4 Mbps, the value for
number must be between 632 and 4464 bytes.

For other drivers, refer to your hardware documentation for frame
size information.

===================================================================

LINK SUPPORT SECTION
~~~~~~~~~~~~~~~~~~~~

The TCP/IP Transport software uses the buffer management functions
provided by the LSL driver.  The Link Support section of the
NET.CFG file includes parameters that determine the number and
sizes of buffers available for the TCP/IP protocol.  IPX does not
use these buffers.

The settings that can be included in the Link Support section are
described in the following subsections.


Buffers number [ size ]

The Buffers setting controls the number and size of receive packet
buffers.  The default number of receive buffers is 8, and the
default size is 4200 bytes for token ring and 1500 bytes for all
other media types.  You can reduce the number of receive buffers if
TCP connections are used sequentially.  If you make heavy use of
multiple TCP connections, you can increase the number of buffers
for better performance.


MemPool size

The MemPool setting controls the size of an internal send-buffer
pool used by TCP/IP.  TCP send data is copied into this pool before
being sent to the remote system.  The default size is 4096 bytes.
You might need to increase the MemPool size when communicating with
remote TCP hosts that offer large receive windows and delay
acknowledgments.


Max Boards number

This option configures the maximum number of logical boards LSL can
support.

Each driver and frame type supported by the driver uses one LSL
logical board resource.  For example, if you are configuring
NE1000.COM to load all possible Ethernet frame types (ETHERNET_II,
ETHERNET_802.3, ETHERNET_80202, and ETHERNET_SNAP), four board
resources are used.

You must include the Max Boards setting only if you require more
than four logical boards (the default).  The range of values for
number is from 1 to 16.


Max Stacks number

This option configures the maximum number of logical protocol
stacks LSL can support.  Each protocol stack uses one or more stack
ID resources.

If a protocol stack fails to load because of an out-of-resource
condition, you can solve the problem by increasing this value.
Because support for additional stacks increases the amount of
memory used by LSL.COM, you can conserve some memory by reducing
this value if your system is not using all allocated stack support.

You must include the Max Stacks setting only if you require more
than four logical stacks (the default).  The range of values for
number is from 1 to 16.

===================================================================

PROTOCOL TCPIP SECTION:
~~~~~~~~~~~~~~~~~~~~~~

The parameters that can be set in the Protocol TCPIP section of the
NET.CFG file are summarized below.


Board Settings:
**************

    Bind driver [ #board frame_type network_name ]

     Specifies the network board for the TCP/IP protocol stack.
     This parameter is needed only if you are running more than one
     link driver to support TCP/IP (for example, a workstation that
     uses both Ethernet and a SLIP/PPP serial link, or a network
     gateway machine with two network boards).

     If this parameter is not specified, TCP/IP uses the first
     driver it finds in memory (the first one loaded by LANWG.BAT).

     The Bind parameters are as follows.  Parameters #board,
     frame_type, and network_name are optional.  Include them only
     when configuring TCP/IP to run over multiple network
     interfaces.

       driver

         Name of the link driver for this board.  For example, if
         the driver is NE1000.COM, the value for the driver
         parameter is NE1000.

       #board

         Number of the board to bind to this driver.  This is the
         physical load sequence number of the board (not the same
         as the logical board number displayed by the driver when
         it is loaded).  Using board number 0 instructs TCP/IP to
         bind to the first board it finds that supports TCP/IP and
         also supports the specified frame_type.

       frame_type

         The frame format used for this network connection. This is
         the same as the frame value in the Link Driver section for
         this driver.

       network_name

         A descriptive name for this network connection.  The
         network_name is used with the ip_address, ip_router, and
         ip_netmask settings to distinguish between the values for
         each network connection.


Directory Path Settings:
***********************

     PATH SCRIPT [ [ drive: ] path [ ; ... ] ]

       Specifies the directory or directories that contain script
       files.  The syntax is the same as the DOS PATH command.  The
       default value is \NET\SCRIPT.

     PATH PROFILE [ [ drive: ] path [ ; ... ] ]

       Specifies the directory or directories that contain profile
       files.  The syntax is the same as the DOS PATH command.  The
       default value is \NET\PROFILE.

     PATH LWP_CFG [ [ drive: ] path [ ; ... ] ]

       Specifies the directory or directories that store the LAN
       WorkGroup internal configuration and data files.  The syntax
       is the same as the DOS PATH command.  The default value is
       \NET\HSTACC.

     PATH TCP_CFG [ [ drive: ] path [ ; ... ] ]

       Specifies the directory or directories that contain the LAN
       WorkGroup database configuration files HOSTS, NETWORKS,
       PROTOCOL, SERVICES, and RESOLV.CFG.  The syntax is the same
       as the DOS PATH command.  The default value is \NET\TCP.


Address Settings:
****************

     ip_address address [ network_name ]

       The IP address of the workstation.  The value for this
       parameter is supplied during installation.  The ip_address
       parameter has no default value.  If no ip_address is used,
       WGTCPIP uses the BOOTP server to get its IP address.

     The ip_address parameters are as follows:

       address

         IP address in dotted notation.  If this parameter is
         missing or is 0.0.0.0, the protocol stack uses Reverse ARP
         or BOOTP to determine the IP address.

       network_name

         The descriptive network name used in the Bind setting for
         this network connection.  The network_name is required
         only if you are configuring multiple link drivers for
         TCP/IP.

     ip_router address [ network_name ]

       The default router address to send all packets destined for
       remote networks.  All other gateways are dynamically
       discovered by using the ICMP redirect mechanism.  The value
       for this parameter is supplied during installation.  The
       ip_router parameter has no default value.

       The ip_router parameters are as follows:

       address

         IP address in dotted notation.

       network_name

         The descriptive network name used in the Bind setting for
         this network connection.  The network_name is required
         only if you are configuring multiple link drivers for
         TCP/IP.

     ip_netmask mask [ network_name ]

       Specifies the subnetwork mask if subnetworks are used.  The
       value for this parameter is supplied during installation.
       The ip_netmask parameter has no default value.

       The ip_netmask parameters are as follows:

       mask

         Subnetwork mask in dotted notation.

       network_name

         The descriptive network name used in the Bind setting for
         this network connection.  The network_name is required
         only if you are configuring multiple link drivers for
         TCP/IP.


Socket Settings:
***************

     tcp_sockets number

       Specifies the maximum number of concurrent TCP connections.
       If you configure multiple link drivers for TCP/IP, the
       number of tcp_sockets you specify is the total shared by all
       drivers.

       The default value is 8.  The range of values is 0 through
       64.

     udp_sockets number

       Specifies the maximum number of concurrent UDP connections.
       You should have at least 1 UDP socket for each concurrently
       run application if you are planning to use the Domain Name
       System.  NetBIOS requires at least 2 UDP sockets.  If you
       configure multiple link drivers for TCP/IP, the number of
       udp_sockets you specify is the total shared by all drivers.

       The default value is 8.  The range of values is 0 through
       32.

     raw_sockets number

       Specifies the maximum number of raw IP connections.  You
       should have 1 raw IP socket if you are planning to use the
       PING command or the applications that use this capability
       (Serving FTP, IP Resolver, LWPCON).  If you configure
       multiple link drivers for TCP/IP, the number of raw_sockets
       you specify is the total shared by all drivers.

       The default value is 1.  Valid values are 0 and 1.


NetBIOS Settings:
****************

     nb_sessions number

       Specifies the maximum number of concurrent NetBIOS sessions.
       When you set this parameter, you must increase the number of
       TCP sockets you allocate (tcp_sockets parameter) to at least
       nb_sessions + 1.

       The default value is 4.  The range of values is 0 through
       64.

     nb_commands number

       Specifies the maximum number of asynchronous NetBIOS
       commands.  The default value is 20.  The range of values is
       0 through 80.

     nb_domain domain_name

       Specifies the name of the logical domain for this NetBIOS
       station.  The default domain_name (null) is used if this
       setting is not specified.  The value of this parameter is an
       ASCII string.

     nb_adapter { 0 |  1 }

       Specifies which NetBIOS board to use.

     nb_brdcast { 0 |  1 }

       Specifies the format of IP broadcasts used when RFCNBIOS.EXE
       sends broadcast messages.

       The value 0 sets the broadcast address to use zeroes for the
       host portions of the IP address.  For example, a Class B
       network with network address 122.44 has broadcast address
       122.44.0.0.

       The value 1 sets the broadcast address to use 255 for the
       host portions of the IP address.  For example, a Class B
       network with network address 122.44 has broadcast address
       122.44.255.255.


Setting the Directory Paths:
***************************

The four PATH settings in the NET.CFG file let you use
configuration files, scripts, and profiles stored on private client
drives or shared server drives as well as your workstation's hard
disk.  Maintaining multiple copies of the LAN WorkGroup
configuration files lets you make use of the centrally maintained
configuration files on your workgroup server, while continuing to
maintain your personal configuration information on your
workstation's disk or your private network disk space.

The example below shows how a user can configure the PATH
statements to use both local and network configuration directories.
In this configuration the LAN WorkGroup software first checks the
directories on the workstation's C: drive.  If the file or
information within the file is not present on C:, the directories
on a private area of the network server (drive J:) are searched
next.  The last area searched is a public area on the server (drive
F:).

     Protocol TCPIP
       PATH SCRIPT     C:\NET\SCRIPT;J:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE    C:\NET\PROFILE;J:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG    C:\NET\HSTACC;J:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG    C:\NET\TCP;J:\NET\TCP;F:\ETC

Below is an example that shows how a diskless workstation could be
configured.  In this example, the workstation user's disk storage
is provided by a private area of the network server (mapped to
drive J:).  The LAN WorkGroup software looks for configuration
files in the private area first and, if the information is not
found, then searches a public area on the server (for example,
drive F:).

NOTE: In the following examples, F: is mapped to the SYS: volume,
      but this is not required.  Also, note that LWGCON cannot
      handle more than two paths in a PATH statement.


     Protocol TCPIP
       PATH SCRIPT     J:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE    J:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG    J:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG    J:\NET\TCP;F:\ETC


Allocating Sockets:
******************

The default WGTCPIP provides for 8 TCP sockets, 8 UDP sockets, and
1 raw socket.  These default allocations should be sufficient for
most configurations.  If you expect to make heavy concurrent use of
applications that use sockets, you might want to modify the number
of TCP sockets in NET.CFG (tcp_sockets).

LAN WorkGroup socket requirements are as follows:

     Each Telnet session (Host Presenter or TNVT220) requires 1 TCP
     socket.

     Each FTP session (Rapid Filer or FTP) requires 2 TCP sockets.

     Each R-utility requires 2 TCP sockets.

     Each L-utility uses 1 TCP socket.

     Each Serving FTP or FTPD session requires 2 TCP sockets.

     Each XPC session uses 1 TCP socket.

     Each FINGER session uses 1 TCP socket.

     Each Windows Talk session uses 1 TCP socket.

For example, to run two sessions of Host Presenter (2 TCP sockets),
Rapid Filer connected to two remote hosts at the same time (4 TCP
sockets), and RSH (2 TCP sockets) while your Windows applications
are active, you need 8 TCP sockets, the default value.

UDP sockets are used by LWPCON, TFTP, TFTPD, and by all
applications that query DNS nameservers.  Because UDP sockets are
used briefly to send and receive datagrams, then released, you need
more than the default 8 UDP sockets only if you make very heavy use
of DNS or TFTP.

One raw socket is required for use by PING, IP Resolver, LWPCON,
and other applications that have ping functions.

Each allocated socket uses a small amount of memory, insufficient
to impact memory allocation if you are fine-tuning your
workstation's memory use.  For a discussion about LAN WorkGroup
memory use and reconfiguration, refer to the LAN WorkPlace for DOS
Administrator's Guide.


Setting Up NetBIOS:
******************

The NET.CFG NetBIOS parameters allow you to configure the
RFCNBIOS.EXE driver to provide RFC 1001/1002-compliant NetBIOS
capability.  These parameters are fully documented in the LAN
WorkPlace for DOS Administrator's Guide.

===================================================================

OTHER PROTOCOL SECTIONS:
~~~~~~~~~~~~~~~~~~~~~~~

The NET.CFG file can contain additional Protocol sections to
configure other network protocols, such as IPXODI, IPTUNNEL, and
RFCNBIOS.  For IPXODI configuration instructions, refer to the
NetWare Workstation for DOS manual.  IPTUNNEL and RFCNBIOS
configuration instructions are provided by the LAN WorkPlace for
DOS Administrator's Guide.

===================================================================

EXAMPLE NET.CFG CONFIGURATIONS:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This section contains examples of NET.CFG files set up for
different purposes.  You can copy the appropriate parts of these
examples into your workstation's NET.CFG file, if you have a
similar configuration.

This section provides examples for the following cases:

     Setting up an Ethernet configuration

     Setting up a token ring configuration

     Setting up an ARCnet configuration

     Setting up the IPTUNNEL driver

     Configuring a SLIP or PPP asynchronous serial line

     Configuring the SNMP agent

Because LAN WorkGroup uses NetWare to provide shared access to the
product files, the client workstation NET.CFG file must be
configured to support both TCP/IP and IPX.  The Open Datalink
Interface (ODI) supports concurrent TCP/IP and IPX protocol stacks.
The examples include the Link Driver statements required to run
both TCP/IP and IPX.

All examples assume that a BOOTP server is providing the TCP/IP
address parameters.


Ethernet Configuration:
**********************

Below is a sample NET.CFG file for using TCP/IP and IPX in an
Ethernet configuration (ECONFIG) environment.  In this example,
because both IPX and TCP/IP use the ETHERNET_II frame format, no
Protocol IPX setting is required.

     Link Driver NE1000
       Int #1 5
       Port #1 320
       Frame ETHERNET_II   # Allow Ethernet II packets

     Link Support
       Buffers 8 1500
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT     C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE    C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG    C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG    C:\NET\TCP;F:\ETC

Below is a sample NET.CFG file for using TCP/IP and IPX in the
default Ethernet 802.3 environment.  The following line configures
IPX to run over Ethernet 802.3:

     Protocol IPX 0 Ethernet_802.3

A Protocol IPX setting must be present to run IPX with TCP/IP, when
IPX is operating in an Ethernet 802.3 environment.  In this
example, TCP/IP uses the ETHERNET_II frame format, and IPX uses the
ETHERNET_802.3 frame format.

     Link Driver NE1000
       Int #1 5
       Port #1 320
       Frame ETHERNET_II               # Allow Ethernet II packets
       Frame ETHERNET_802.3            # Allow 802.3 packets
       Protocol IPX 0 Ethernet_802.3   # Make IPX use 802.3

     Link Support
       Buffers 8 1500
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT      C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE     C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG     C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG     C:\NET\TCP;F:\ETC


Token Ring Configuration:
************************

The example below shows how to configure NET.CFG for a token ring
TCP/IP network using the TOKEN.COM driver.  The frame type used on
token ring TCP/IP networks is always TOKEN-RING_SNAP.  In this
example, TCP/IP uses the TOKEN-RING_SNAP frame format and IPX uses
the TOKEN-RING frame format.  The increased buffer size (4202) is
recommended only if problems are encountered using the default size
(1500).

     Link Driver TOKEN
       Frame TOKEN-RING_SNAP
       Frame TOKEN-RING
       Protocol IPX E0 TOKEN-RING

     Link Support
       Buffers 8 4202
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT      C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE     C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG     C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG     C:\NET\TCP;F:\ETC


ARCnet Configuration:
********************

The example below shows how to configure NET.CFG for an ARCnet
network.  This example uses a TRXNET board with NOVELL_RX-NET frame
format, which is the frame format used on ARCnet TCP/IP and IPX
networks.  Because both protocols use the same frame format, no
Protocol IPX setting is needed.

     Link Driver TRXNET
       Frame NOVELL_RX-NET

     Link Support
       Buffers 8 1500
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT      C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE     C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG     C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG     C:\NET\TCP;F:\ETC


Setting Up IPTUNNEL:
*******************

The IPTUNNEL.EXE program allows your workstation to communicate as
a NetWare DOS client with a NetWare server that is accessible only
through an IP internet connection.  Below is an example NET.CFG
file configured to enable the IPTUNNEL capability.

     Link Driver NE2000
       Int #1 5
       Port #1 320
       Frame ETHERNET_II

     Link Driver IPTUNNEL
       gateway            144.52.66.50
       gateway            149.31.1.100
       port               213
       checksum           yes

     Link Support
       Buffers 8 1500
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT        C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE       C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG       C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG       C:\NET\TCP;F:\ETC

     Protocol IPX
       Bind IPTUNNEL

This NET.CFG file does the following:

     Specifies the gateway addresses of the two NetWare servers in
     the IP Tunnel configuration (the gateway setting can also be
     used to specify the broadcast address).

     Sets a UDP port for use by the IPTUNNEL driver (port 213).

     Enables UDP checksum calculation.

     Binds the IPTUNNEL driver for use by IPX.

The IPTUNNEL parameters are described in detail in the LAN
WorkPlace for DOS Administrator's Guide.


Setting Up SLIP and PPP Connections:
***********************************

SLIP and PPP allow the LAN WorkGroup software to operate over
asynchronous serial line media.  For example, you can configure LAN
WorkGroup with SLIP or PPP on an offsite workstation with a Hayes-
compatible modem connected to a COMn: port.  You can then use the
DIALUP utility to dial into an IP router with asynchronous dialup
serial line access and run the applications and utilities provided
by LAN WorkGroup in the same manner as over an Ethernet, token
ring, or ARCnet network connection.

Because you can configure multiple link drivers for use with
TCP/IP, you can set up your workstation to support LAN WorkGroup
communications over both a network board and a COMn: port link
simultaneously.  Below is a NET.CFG file that configures an
Ethernet board (NE2000) and the COM1: port (SLIP_PPP) for TCP/IP
over SLIP use.

     Link Driver NE2000
       Int #1 2
       Port #1 340 10
       Frame ETHERNET_II
       Frame ETHERNET_802.3
       Protocol IPX 0 Ethernet_802.3

     Link Driver SLIP_PPP
       Int 4
       Port 3F8
       Baud 9600
       tcpipcomp vj
       Frame SLIP

     Link Support
       Buffers 8 1500
       MemPool 4096

     Protocol TCPIP
       PATH SCRIPT           C:\NET\SCRIPT;F:\NET\SCRIPT
       PATH PROFILE          C:\NET\PROFILE;F:\NET\PROFILE
       PATH LWP_CFG          C:\NET\HSTACC;F:\NET\HSTACC
       PATH TCP_CFG          C:\NET\TCP;F:\ETC
       Bind ne2000
       ip_address            150.37.7.8               LOCAL-NET
       ip_router             150.37.4.254             LOCAL-NET
       ip_netmask            255.255.0.0              LOCAL-NET
       Bind slip_ppp #0 SLIP LOCAL-NET

This NET.CFG file does the following:

     Configures two network connections, one provided by an NE2000
     board (which receives its TCP/IP parameters from a BOOTP
     server) and one provided by SLIP_PPP (assigned network name
     LOCAL-NET; SLIP_PPP connections cannot receive their TCP/IP
     parameters from a BOOTP server).

     The network name is arbitrary and is used only within the
     NET.CFG file.  It identifies which parameter settings to apply
     to each network connection.

     Configures the SLIP_PPP driver to operate on the COM1: port
     (interrupt 4) and use the LOCAL-NET address parameters.

     Configures the NE2000 driver to use both ETHERNET_II and
     ETHERNET_802.3 frame types, and to run TCP/IP concurrently
     with IPX.

Configuring multiple link drivers is not sufficient to employ a
client workstation as a router.  The workstation in the example
above can operate solely as a LAN WorkGroup client workstation on
one network connection and one serial connection simultaneously.
It cannot route packets between these two connections for other
workstations.

The SLIP_PPP driver has several optional Link Driver parameters and
supports other frame types in addition to those illustrated above.
All SLIP_PPP parameters are described in detail in the LAN
WorkPlace for DOS Administrator's Guide.


Configuring the SNMP Agent:
**************************

Below is an example NET.CFG file that configures the SNMP agent
program.

     Link Support
       Buffers 8 1500
       MemPool 4096

     Link Driver NE2000
       Protocol IPX 8137 ETHERNET_II
       Frame ETHERNET_II
       Int 5
       Port 300

     Protocol TCPIP
       PATH SCRIPT      D:\NET\SCRIPT
       PATH PROFILE     D:\NET\PROFILE
       PATH LWP_CFG     D:\NET\HSTACC
       PATH TCP_CFG     D:\NET\TCP
       ip_router        129.47.4.254  # TCP/IP info goes here
       ip_netmask       255.255.252.0
       ip_address       129.47.6.90
       tcp_sockets      8
       udp_sockets      8
       raw_sockets      1
       nb_sessions      4
       nb_commands      8
       nb_adapter       0
       nb_domain
       
#----------------Sample Protocol SNMP Section----------------------

     Protocol SNMP
       monitorCommunity     public
       controlCommunity     noAccess
       sysContact           Your name
       sysName              YourCompany.com  # Your domain name
       sysLocation          Text describing your system's location

#  Do not use tabs to precede entries in this section.

===================================================================

RELATED README FILES:
~~~~~~~~~~~~~~~~~~~~~

For additional information, see the following text files:

  DOCUPDTE.TXT (for information about documentation updates)
  LWGLWP.TXT (for information on running LAN WorkPlace and LAN
  WorkGroup on the same workstation)
  NFSV12B.TXT (for upgrade information on NetWare NFS v1.20B)
  README.TXT (for information installation and configuration)
  SWUPDATE.TXT (for information about software updates)
     
All of these files are located on the first installation diskette
and copied to the <vol>:NET directory.  The README.TXT file is also
copied to the SYS:ETC\INSTALL directory as LWG.TXT.  If the
information in the printed manuals, online help, or in the text
files does not answer your questions, contact your Novell-
authorized reseller for assistance.

