Manual Installation of Novell's 16-bit TCP/IP Transport Software

1. Place the TCPIP diskette in the server's A: drive.

2. Set your current drive and directory to the directory containing your existing Novell network software, such as the LSL.COM file.

Note: The remainder of these instructions will assume that the directory being used is C:\NWCLIENT. Modify the examples if your directory is different.

3. From the TCP16 diskette, copy the file TCPIP.EXE to the C:\NWCLIENT directory. Also copy the files PING.EXE and PING.MSG.

C> COPY A:\TCPIP.EXE C:\NWCLIENT
C> COPY A:\PING.EXE C:\NWCLIENT
C> COPY A:\PING.MSG C:\NWCLIENT

4. You are now ready to modify the batch file you use to load the Novell network software. Depending on how your original server installation was performed, that file may be AUTOEXEC.BAT, STARTNET.BAT, or some other batch file. The batch file you are looking for will contain commands to load LSL.COM, an ODI-compliant network driver (like NE2000.COM), and IPXODI.COM. Assuming the file was AUTOEXEC.BAT in the C:\ directory, you would issue the following command at the DOS prompt:

C:> EDIT C:\AUTOEXEC.BAT

5. Using the DOS editor, make the following changes:

If you will no longer be using the IPX network protocol, remove the line containing the text, “IPXODI.COM”. If you will be using IPX and TCP/IP together, then leave that line unchanged.

Add a new line to invoke the executable file TCPIP.EXE. Your batch file should now contain lines similar to the following:

C:\NWCLIENT\LSL.COM
C:\NWCLIENT\NE2000.COM
C:\NWCLIENT\IPXODI.COM /A
C:\NWCLIENT\TCPIP.EXE

6. Use the “Save” option on the editor's “File” menu to save the modified batch file to your hard disk. Then exit the editor (choose the “Exit” option from the File” menu).

7. You are now ready to modify your AUTOEXEC.BAT file. Using the editor, place the following line in your AUTOEXEC.BAT file if it is not already there:

SET PATH=C:\NWCLIENT;%PATH%

8. Note that the CONFIG.SYS file does not require any modification.

9. You must now edit the NET.CFG file, which will probably be in the same directory as LSL.COM. The contents of NET.CFG are organized into sections identified by a section header line. Section headers do not have any leading spaces before the first word on the line. All parameter lines within a section must have at least one space or tab at the beginning of the line. Text appearing after a semi-colon (';') is regarded as a comment. Upper-case and lower-case letters are treated the same.

Look for a section entitled, “Link Support.” If you find it, modify its parameter lines until they look exactly like the example below. If you do not find it, add the following section to the beginning of the file exactly as shown below:

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

Find the section entitled, “Link Driver.” Then look for a “Frame” parameter line.

If you do not find such a line, and you plan to continue using the IPX network protocol simultaneously with TCP/IP, then you must add the following two lines as the last parameters in the section:

Link Driver NE2000
. . .
. . .
Frame Ethernet_802.2
;(or Frame Token-Ring)
Frame Ethernet_II
;(or Frame Token-Ring_SNAP)

If you do find a “Frame” parameter line but it does not say “Frame Ethernet_II” (or “Token-Ring_SNAP” for token-ring network hardware), then you must add the following line as the last parameter in the section:

Link Driver NE2000
. . .
. . .
Frame Ethernet_II
;(or Frame Token-Ring_SNAP)

Note: If your adapter driver file was NE2000.COM, the driver name given on the Link Driver” section header would be “NE2000”, as shown above. Most ODI drivers follow this same naming convention.

At the end of the file, Add the following section as shown below, altering only the IP information to match your site's network addressing scheme:

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 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.

10. Use the “Save” option on the editor's “File” menu to save the modified NET.CFG file to your hard disk. Then exit the editor (choose the “Exit” option from the “File” menu).

11. 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).

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 driver settings in the NET.CFG file.

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