NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              INETCFG.NLM for NetWare 4.X
DOCUMENT ID:        TID200021
DOCUMENT REVISION:  A
DATE:               03DEC93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         INET40.EXE

NOVELL PRODUCT and VERSION:
NetWare MultiProtocol Router PLUS 2.1

ABSTRACT:

This contains a version of the INETCFG.NLM for use with NetWare 4.0 and
NetWare 4.01.

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SYMPTOM

     Some problems occur when using INETCFG to BIND protocols to certain
     drivers.

     The type of problem varies depending on the protocol being bound:

          AppleTalk:     The driver appears to support only the AppleTalk
                         phase I protocol, when in fact it supports phase II
                         also.

          IPX:           No frame type choice appears on the BIND screen.  The
                         driver LOAD command does not include a FRAME=
                         parameter, forcing the user to enter it each time the
                         system is initialized.

          TCP/IP:        No immediately obvious problem occurs.  The driver
                         LOAD command does not include a FRAME= parameter,
                         forcing the user to enter it each time the system is
                         initialized.


SOLUTION

     This ETF remedies this situation by prompting the user to indicate a
     media type (e.g. Ethernet, Token-Ring, FDDI, etc.) when no frame type
     information is available. INETCFG knows which frame types are appropriate
     for a given media and is then able to continue correctly.  The user is
     prompted whenever he creates a BIND to a driver of the type described
     above.


     Self-Extracting File Name:  INET40.EXE     Revision:  A

     Files Included    Size      Date

     \
       INET40.TXT            (This File)
      INETCFG.NLM     172224   12-01-93


     Installation Instructions:

          1.   LOGIN to the server as ADMIN or SUPERVISOR

          2.   CD to the \SYSTEM directory

          3.   Check and record the version of the existing INETCFG.NLM

                    VERSION INETCFG.NLM

               It should be version 3.00a or earlier. 
  
          4.   Flag the existing INETCFG.NLM

                    FLAG INETCFG.NLM +RW

          5.   Rename INETCFG.NLM

                    REN INETCFG.NLM INETCFG.OLD

          6.   Copy the INETCFG.NLM from this PTF and flag it RO

                    FLAG INETCFG.NLM RO
            
          7.   Unload INETCFG (if loaded) and reload it. Now, when trying to
               bind protocol to board, the frame type is requested.

          8.   Check the version of INETCFG.NLM again.  It should be 3.00b
               after Step 6.


Patch History:

     Some LAN drivers are distributed without an .LDI file. (An .LDI file
     contains a description of the driver load line parameters.) INETCFG reads
     .LDI files to find out, among other things, which frame types are valid
     for a driver. If a driver lacks an .LDI file, INETCFG relies on an
     internal list to get frame type information, but this list could not
     possibly contain every LAN driver used with NetWare.

     For those drivers which do not appear on this internal list and which
     lack an .LDI file, INETCFG has no frame type information and hence does
     not correctly create LOAD commands. This problem has been noted with the
     Compaq NetFlex drivers (CPQETHER.LAN and CPQTOKEN.LAN), the SMC 8013
     driver and the 3COM 3C509 driver, but will occur for any driver lacking
     an .LDI file.


ÿ