Network Considerations | I |
Network Primer |
While a protocol section might look like the following:
[NETMANAGE] DRIVERNAME=NETMNG$ BINDINGS=EtherLinkII
These two protocol.ini file sections describe a hardware driver characteristic for a 3COM EtherLink II hardware card and specifies that the NetManage protocol stack should bind with the EtherLink II driver.
The setup information for ODI drivers is contained in a file called net.cfg that must be in the Novell directory (the driver must be there too). This file contains sections describing the driver characteristics and the protocols that may be operating over the driver. For example, a driver characteristic section might look like the following:
Link Support
Buffers 8 1589
MemPool 4096
Protocol IPX
Bind EXP16ODI
Protocol
Bind EXP16ODI
ip_address 198.178.246.101
Link Driver EXP16ODI
Port 300
Frame Ethernet_802.3
Frame Ethernet_II
Protocol IPX Ethernet_802.3
This net.cfg file describes a hardware driver characteristic for an Intel EtherExpress 16C hardware card and specifies that the IPX and TCP/IP protocol stacks should bind with the EtherExpress driver.
TCP/IP Protocol Stack |
A protocol stack is a group of interacting programs that implement the various functions of the network communication protocol. They are usually arranged in a hierarchy of low to higher level functions, so the collection is called a stack.
Windows 95 and Windows NT supply a TCP/IP protocol stack and you can obtain TCP/IP software for Windows for Workgroups from Microsoft. On Windows 3.1, you may need to install Newt or Trumpet. Novell sells an optional package for NetWare called LAN Workplace for DOS/Windows that includes a TCP/IP stack.
