B.1.1. Windows 95/98

B.1.2. Windows NT

The installation for Windows NT is very similar to the installation for Windows 9x (depending on what version of NT you are running). It is important that you have installed all of the Windows NT service releases. Some of these service releases fix problems that have had an adverse effect on Cascade Connect in the past. Please contact Cogent if you need assistance installing TCP/IP for Windows NT.

B.1.3. Data Server TCP/IP Setup

Before the data server TCP/IP layer can run you must start the network manager and an appropriate network card driver. The network manager is either /bin/Net or /bin/Net32 and the drivers are /bin/Net.XXXXX or /bin/Net32.XXXXX. The 32 denotes a 32-bit driver and the XXXXX is the name of the driver that works with your network card. Make sure the correct driver is started and working properly before attempting to configure TCP/IP.

It is a good idea to use the /etc/hosts file to list the IP addresses and names for each computer. This file will need to be modified to ensure that you have listed the IP address and name of each computer involved in TCP/IP networking. The following is an example of an /etc/hosts file:

    #IP address     fullname            name
    127.0.0.1       localhost           local
    1.1.1.1         andrew.cogent.ca    andrew
    1.1.1.2         robert.cogent.ca    bob
    1.1.1.10        mark.cogent.ca      mark

If your LAN does not have a TCP/IP name data server then each computer (data server and Windows) must have an identical copy of the hosts file. Once the hosts file information has been configured, the TCP/IP protocol can be started.

Using the example above and assuming that we have given the data server node the IP address 1.1.1.1 andrew.cogent.ca, the following commands would be issued (as a root level user):

    Socket andrew &
    ifconfig en1 up 255.255.255.0
    portmap &
    inetd &

The name andrew is a name used to save you typing the whole address name. The en1 from the ifconfig line indicates that we are binding to logical network number one. We assume the data server supports multiple networks, so check the options on your Net.XXXXX driver to see which card and network you are binding to. If you are running a large network you should also check which netmask is being used (in the example above it is given as 255.255.255.0). Different classes of IP address have slightly different netmask addresses so check with your LAN administrator.

You can now test the interface using the command netstat -ain which shows all TCP/IP connections and the number of messages sent out on each. It is then possible to use ping and Telnet to ensure that the computer can see other nodes. This testing of the connection using ping and Telnet is detailed in Testing.

Once the startup procedure for TCP/IP is confirmed as working, you should put the appropriate lines into a script which can be called from your /etc/config/sysinit.node file.

For more information on the setup and configuration of TCP/IP refer to the documentation that came with the TCP/IP run-time for your operating system.