Support HomeSearch Intel(R)
EtherExpress™ 16 Family
TCP/IP Configuration Notes

This document applies to the EtherExpress™ 16, 16/TP, 16C, FLASH, FLASH TP, FLASHC, MCA, and MCA/TP adapters. It contains general information notes and also examples for PCNFS and PC/TCP with the EtherExpress driver. 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.

Are The EtherExpress Cards TCP/IP Compatible?

Intel does not sell TCP/IP software, however, TCP/IP software may be purchased from several different vendors. Intel provides NDIS and ODI drivers that work with most TCP/IP software. First, determine if the TCP/IP software is NDIS or ODI compliant and then find the section below that applies.

NDIS General:

Intel's EtherExpress 16 NDIS adapter driver conforms to Microsoft's NDIS Specification v2.0.1. If the TCP/IP software is NDIS compliant, use the NDIS drivers. These drivers are on the EtherExpress diskette in the following subdirectories:

NDIS\EXP16.DOS (for DOS)
NDIS\EXP16.OS2 (for OS/2)

The following section should be added to the existing PROTOCOL.INI file. A sample PROTCOL.INI is located in the NDSI subdirectory.

[EXP16]
IOADDRESS = 0x300
DRIVERNAME = EXP16$

NOTE: The IOADDRESS must be modified to match the I/O Address of the card. The EXP16$ must be in capital letters.

NOTE: For more information on NDIS, see the NDIS.TXT readme file.

NDIS And BANYAN Vines:

The version of TCP/IP supplied with Banyan Vines 4.X does not support NDIS drivers. To use TCP/IP with an NDIS driver, you will need to purchase a version of TCP/IP that supports NDIS. We recommend you call your Banyan support representative for more information.

ODI General:

The ODI driver conforms to Novell's ODI Specification. If the TCP/IP software is ODI compliant, use the ODI drivers. These drivers are on the diskette in the following subdirectory.

NETWARE.ODI\EXP16ODI.COM (for DOS)
NETWARE.ODI\EXP16ODI.SYS (for OS/2)

ODI Drivers use a NET.CFG file that works similar to the Protocol.ini file.

An EXAMPLE of the ODI NET.CFG from a Lan WorkPlace for DOS set up follows:

	         Link Support
	           Buffers 8 1586
	           MemPool 4096

	        Protocol IPX
	           Bind EXP16ODI   <-- Bind 1, if using IPXODI v2.x or later

	        Protocol TCP/IP
	           Bind EXP16ODI   <-- delete this line if using IPXODI v2.x or
	   later
	           ip_address xxx

	        Link Driver EXP16ODI
	           Port 300
	           Frame Ethernet_802.3     <-- Order of frames here is important
	           Frame Ethernet_II
	           Protocol IPX 0 Ethernet_802.3
	

NOTE: The Port parameter must be modified to match the I/O Address of the card.

Packet Drivers:

We provide a packet driver for EtherExpress card via that conforms to the FTP packet driver specification v1.07. If the TCP/IP packages allow to yous packet drivers, use the packet drivers in the PACKET subdirectory.

NOTE: For more information on packet drivers, see the PACKET.TXT readme file.

Document #6321 EtherExpress 16 Family: Driver Installation with FTP PC/TCP

NOTE: For more information on using the NDIS driver with FTP PC/TCP, see the PCTCP.TXT readme file.

SUN'S PCNFS WITH NDIS: document 6320

NOTE: For more information on using the NDIS driver with SUN PCNFS, see the PCNFS.TXT readme file.

PLEASE NOTE:
This product is no longer being manufactured by Intel. THESE DOCUMENTS ARE PROVIDED FOR HISTORICAL REFERENCE PURPOSES ONLY AND ARE SUBJECT TO THE TERMS SET FORTH IN THE "LEGAL" INFORMATION" LINK BELOW. For information on currently available Intel products, please see www.intel.com and/or developer.intel.com




* Legal Information and Privacy Policy © 2000 Intel Corporation