images/contents.gifimages/index.gifimages/prev1.gifimages/next1.gif

Configuring 16-bit Transport Software for a New Installation

This section assumes you have just completed manual installation instructions for Novell's NetWare Client for DOS/Windows, Novell's LAN WorkPlace 5 for DOS/Windows, or the Novell software that came with your network hardware. (If you followed a different installation procedure, then you should proceed instead to the section, Miscellaneous DOS Configuration Tips for AspeNet Servers .)

1. You are now ready to modify your AUTOEXEC.BAT file. Place the following lines at the end of your AUTOEXEC.BAT file (substituting the name of your adapter driver for the NE2000 driver shown below). The following example is for systems using both TCP/IP and IPX protocols. If you are only using one network protocol, include only the one you want:

C:\NWCLIENT\LSL
C:\NWCLIENT\NE2000
C:\NWCLIENT\IPXODI /A
C:\NWCLIENT\TCPIP
SET PATH=C:\NWCLIENT;%PATH%

2. The CONFIG.SYS file does not require any modification.

3. You are now ready to create the special configuration file, NET.CFG. Create this file in the C:\NWCLIENT directory. Following are three examples for an Ethernet installation, one for using IPX only, one for using TCP/IP only, and one for using both IPX and TCP/IP.

Copy one of the examples shown below, only replacing the NE2000 reference with the name of your adapter driver, altering the hardware settings to match your installation, and, if using TCP/IP, filling in correct values for your TCP/IP addressing information.

Note: the section header lines must be left-justified and the parameter lines within each section must have at least one space or tab character at the beginning of the line. Also, if your adapter driver file was NE2000.COM, the driver name given on the “Link Driver ...” section header would be “NE2000”. Most ODI drivers follow this same naming convention. Consult the documentation that came with your network driver if necessary.


images/net00090000.gif Sample NET.CFG for using IPX only:

Link Support
Max Boards 4
Max Stacks 4

Link Driver NE2000
int 5
port 300
frame Ethernet_802.2

Protocol IPX
IPX Sockets 36

Note: If you are using a token-ring network, your frame should be Token-Ring_SNAP” or “Token-Ring”.


Note: Other possible Ethernet frames are: “Ethernet_802.3”, “Ethernet_II”, or Ethernet_SNAP”.

images/net00090000.gif Sample NET.CFG for using TCP/IP only:

Link Support
Buffers 32 638
MemPool 40K
Max Boards 4
Max Stacks 4

Link Driver NE2000
int 5
port 300
frame Ethernet_II

Protocol TCPIP
ip_address 204.250.100.1
ip_netmask 255.255.255.0
ip_router 0.0.0.0
tcp_window 598
tcp_sockets 32

Note: If you are using a token-ring network, your frame should be Token-Ring_SNAP”.


Note: If you have no IP router on your LAN connecting it with other LAN segments, you may omit the “ip_router” line or leave the value of “0.0.0.0”.

Note: Obtain correct IP address, router, and net-mask values from your network administrator. If you don't have a network administrator and your new LAN is going to remain isolated from other networks, use the values as shown in the example above. This will configure the server machine as node 1 on network 204.250.100; the workstations on your network would need to be configured with the same network number and a node number between 2 and 254, inclusive. Each workstation must use a unique node number; duplicating node numbers will cause your network to malfunction.

images/net00090000.gif Sample NET.CFG for using IPX and TCP/IP:

Link Support
Buffers 32 638
MemPool 40K
Max Boards 4
Max Stacks 4

Link Driver NE2000
int 5
port 300
frame Ethernet_802.3
frame Ethernet_II

Protocol TCPIP
ip_address 204.250.100.1
ip_netmask 255.255.255.0
ip_router 0.0.0.0
tcp_window 598
tcp_sockets 32

Protocol IPX
IPX Sockets 36

Note: The first “Frame” parameter in the “Link Driver” section will be used by IPX. Other possible Ethernet frames are: “Ethernet_802.2”, “Ethernet_II”, or “Ethernet_SNAP”.


Note: The “Frame Ethernet_II” parameter will be used by TCP/IP. If you are using a token-ring network, replace “Ethernet_II” with “Token-Ring_SNAP”. There are no other choices.


Note: If you plan to have IPX use the same frame type as TCP/IP, you can omit the first “Frame” parameter, leaving only “Frame Ethernet_II” or “Frame Token-Ring_SNAP”.


Note: If you have no IP router on your LAN connecting it with other LAN segments, you may omit the “ip_router” line or leave the value of “0.0.0.0”.



Note: Obtain correct IP address, router, and net-mask values from your network administrator. If you don't have a network administrator and your new LAN is going to remain isolated from other networks, use the values as shown in the example above. This will configure the server machine as node 1 on network 204.250.100; the workstations on your network would need to be configured with the
same network number and a node number between 2 and 254, inclusive. Each workstation must use a unique node number; duplicating node numbers will cause your network to malfunction.

4. Remove any diskettes from your machine's A: drive and reboot the machine. Watch the messages displayed by each network software module as it loads. If everything is working, you will receive no error messages and only a single warning; when TCPIP.EXE loads, it will issue the following warning message:

WARNING: LSL buffer size too small (minimum: 1500 bytes).

You may ignore this warning; it is expected. If other errors occur, you may have mis-typed something in the NET.CFG file, or your hardware may not match the settings indicated in the NET.CFG file.

5. If you need additional information or examples regarding system configuration, please see the section entitled, TCP/IP and MCP/IPX Configuration Reference . You may also call Aspen Research Technical Support at 1-970-945-2921. Otherwise, proceed to the section, Miscellaneous DOS Configuration Tips for AspeNet Servers .