                       3.1x servers

  NETWARE 3.1X SERVER INSTALLATION NOTES:
  FOR THE INTEL EtherExpress(tm) 16 FAMILY OF NETWORK ADAPTERS
  ============================================================

  This document applies to the EtherExpress(tm) 16, 16/TP, 16C, MCA,
  and MCA/TP.  It contains notes for installing the NetWare 3.11 server
  driver and troubleshooting tips.  It does not explain how to
  configure an EtherExpress board.  For instructions about configuring
  the board, see either the Expert's Guide or the Complete Guide for
  your board.

  This document is also available on FaxBACK.  Document #6316.
 

  INTRODUCTION:
  -------------
  Before you begin, you need the I/O address and IRQ of the
  EtherExpress adapter.  You can get this information by typing CONFIG
  at the NetWare colon prompt.

  You must install NetWare and configure the hard disk before you can
  load the EtherExpress driver.  For information on how to install
  NetWare 3.1x refer to the NetWare installation manual.


  PROCEDURE:
  ----------
  1. From the DOS prompt on the server, copy the EtherExpress driver
     (\NETWARE.3\EXP16.LAN) to the DOS partition of the server's hard
     drive.

  2. Start NetWare by typing SERVER or the name of your startup batch
     file.

  3. Load the driver.  At the server's colon prompt, type:

     LOAD C:\EXP16 PORT=xxx INT=y

     WHERE: xxx is the I/O address of the EtherExpress card and y is the
     interrupt (IRQ) in Hex.  (Softset and the System Configuration
     utility display the IRQ in decimal. IRQ10 = A in Hex.  IRQ11 = B in
     Hex.)

     Be sure to include the path to where the driver is located.

     Novell provides several other parameters you can include in the LOAD
     statement, but they are not required.  For more information on those
     parameters and when you should use them, see the NetWare Installation
     manual.

  4. Bind the driver.  At the server's colon prompt, type:

     BIND IPX TO EXP16 NET=xx

     WHERE: xx is the external network number. 

     At this point you should be able to log into the server from a 
     workstation.


  TO MAKE THIS PERMANENT:
  -----------------------
  Using Novell's INSTALL program, edit the AUTOEXEC.NCF file to add the
  LOAD and BIND statements for the EtherExpress adapter.


  TROUBLE LOADING THE DRIVER:
  ---------------------------
  If you have problems loading a driver, remove the driver statements
  from the AUTOEXEC.NCF file and enter them manually with no
  parameters.  From the Colon prompt, type:

	LOAD C:\EXP16

  NetWare will prompt you for the interrupt and port address.  Add
  parameters back one at a time.  If you receive any error messages,
  check the NetWare System Messages manual for an explanation.

  Do the same for the BIND statement.  Type:

	BIND IPX TO EXP16 


  INSTALLING MULTIPLE ETHEREXPRESS CARDS:
  ---------------------------------------
  If you have multiple network cards in a single server, each card must
  have a different NETwork number, a different PORT address, and a
  different INTerrupt.  You may also want to name each board.  For
  example:

	LOAD C:\EXP16 PORT=300 INT=3 NAME=LAN_A
	BIND IPX TO LAN_A NET=1
	LOAD C:\EXP16 PORT=350 INT=5 NAME=LAN_B
	BIND IPX TO LAN_B NET=2

  Do not confuse the NETwork number with the internal IPX number.  See
  the NetWare Installation manual for more information.


  INSTALLING ONE ETHEREXPRESS CARD WITH MULTIPLE FRAME TYPES:
  -----------------------------------------------------------
  When binding multiple frame types to one card, enter a LOAD statement
  for each frame type.  Each LOAD statement will use the same PORT
  address and INTerrupt, but a different NETwork number.  You may also
  want to name each LAN.  For example:

	LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.3 NAME=LAN8032
	BIND IPX TO LAN8023 NET=1
	LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_II NAME=LANII
	BIND IPX TO LANII NET=2
  
  Do not confuse the NETwork number with the internal IPX number.  See
  the NetWare Installation manual for more information.


  IF WORKSTATIONS CANNOT ATTACH TO THE FILESERVER:
  ------------------------------------------------ 
  On the server:
  - Make sure the volume sys: is mounted.
  - Make sure you BIND the EtherExpress driver.

  If both of these have been checked and workstations still cannot
  attach to the file server then verify that the EtherExpress in the
  server and workstation(s) are working and that they can communicate
  with each other:

  1. Down the file server and reboot with DOS.  Run the SOFTSET/MCADIAGS
     on-board and on-network diagnotics.  If these pass, set the file
     server up as a responder in SOFTSET/MCADIAGS diagnostics.
  2. Reboot the workstation(s) without loading ipx/netx and run the
     SOFTSET/MCADIAGS on-board and on-network diagnostics.  During the
     on-network diagnostics, the server (set up as a responder) should
     count and echo the packets sent by the workstation.
  3. Rerun the workstation and set it up as a responder and try the
     on-network diagnostics from the server machine.  
  4. If on-network diagnostics fail, there is likely a cable, connector,
     hub or concentrator problem.

     If the on-network diagnostics pass, the boards tested can
     communicate.  This indicates there could be a problem with the
     drivers.  Bring the server machine back up as a server.  Reload the
     drivers in the workstation.  If the workstation still cannot connect
     to the server, there is likely a problem with the configuration of
     the drivers.  Verify that the server and workstation drivers load
     properly.  You can do this by loading them one at a time, rather than
     in a batch file, and watch for error messages.


  NOTE: "Responder not found" is NOT an error.  This message will be
        displayed IF YOU ARE NOT RUNNING THE SOFTSET/MCADIAGS RESPONDER
        ON ANOTHER MACHINE with an EtherExpress card or if the card
        cannot actually communicate with the responder card.  If you do
        not have a responder running or if the two cards cannot
        communicate, the diags will try to send packets back to itself.

  TCP/IP:
  -------
  If you are using NetWare's TCP/IP NLM, you must load an ethernet type
  II frame and bind the EtherExpress to TCPIP.  For example:

	LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.3 NAME=LAN_IPX
	BIND IPX TO LAN_IPX NET=1
	LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_II NAME=LAN_IP
	LOAD TCPIP
	BIND IP TO LAN_IP ADDR=xxx.xxx.xxx.xxx 

    WHERE: xxx.xxx.xxx.xxx is your internet address.

  You may also have MASK and GATE parameters on the BIND IP line.  See
  NetWare's documentation for more information.
