A network protocol is the language a network adapter uses to communicate with other devices. Adapters must be configured with a common protocol before they can communicate. Windows 98 includes two native network protocols: TCP/IP, and IPX/SPX.
TCP/IP is the core transmission protocol for the Internet. It has evolved into a powerful and flexible protocol but requires more configuration than other protocols. It should be installed as the primary network protocol when Internet access is required.
IPX/SPX was developed by Novell for communication on Netware networks and is also used by some PC games.
The Transmission Control Protocol/Internet Protocol (TCP/IP) specification defines the core transmission protocol for the Internet. TCP/IP has evolved into a powerful and flexible protocol but requires more configuration than other protocols. It should be installed as the secondary network protocol when Internet access is required.
This section provides an overview of the installation and configuration of TCP/IP as the primary protocol on a peer-to-peer LAN.
IP Address Assignment
TCP/IP uses IP addresses to identify network clients. The addresses can be assigned dynamically when clients sign on to the network or can be configured statically. Dynamic assignment offers several advantages for large installations. For small networks, static IP addressing's advantages include faster bootup, improved network security, compatibility with network devices that require static addresses, and the ability to identify clients by their IP addresses.
IP addresses consist of four octets. IP addresses 192.168.0.xxx are a block of 256 Class C addresses reserved for private Intranets. The first three octets specify the NetID and the fourth is the ComputerID. The LAN adapter of the Internet gateway is commonly assigned 192.168.0.1 with subnet mask 255.255.255.0. The subnet specify's which portion of the IP address is used for the network ID and which portion designates a computer on the network. The client IP's can be derived from the hub and port number with the same convention used for Computer Names.
This figure shows the recommended relationship between IP addresses and the Computer Names. The first 15 ComputerID's, 1-15, are reserved for network devices. Thereafter each hub is allotted 16 ComputerID's starting at 16 for hub 1, 32 for hub 2, etc. where Clienthp'sComputerID is equal to 16*hub# + port#.
Some Internet gateways, e.g. the Cisco Pix firewall, are configured to provide dynamic host configuration protocol (DHCP) services that support dynamic IP addresses. This service must be disabled before static IP addresses can be assigned.
TCP/IP Configuration
The TCP/IP protocol must be installed on each client that will access the Internet.
The Connection tab of the Network dialog box with NetBEUI and TCP/IP protocols installed.
IE float bugIf DHCP is disabled the Internet gateway address must be specified for all clients in TCP/IP properties using the Network tool in Control Panel. Clients are assigned Class C IP addresses of the form: 192.168.0.ComputerID, where the ComputerID is equal to 16*hub# + port#. In the screen capture below Client11 is assigned the ComputerID, 16*1 + 1 = 17.
The IP Address tab of the TCP/IP Properties dialog box with static IP address assignment.
IE float bugWINS Resolution is disabled with static addressing.
The WINS Configuration tab of the TCP/IP Properties dialog box.
IE float bugIn this network the Internet gateway is at 192.168.0.1.
The Gateway tab of the TCP/IP Properties dialog box showing an Internet gateway at 192.168.0.1.
IE float bugClients resolve Internet domain names to IP addresses, e.g. familysearch.org -> 32.96.111.5, via a domain name server (DNS). DNS service is provided by your ISP, ours provides primary and secondary DNS hosts.
The DNS Configuration tab of the TCP/IP Properties dialog box with two DNS Servers configured.
IE float bugNetBIOS over TCP/IP should be enabled if access to local shares is desired and NetBEUI will not be installed.
The NetBIOS tab of the TCP/IP Properties dialog box.
IE float bugIn the Advanced tab, verify that TCP/IP is not the default protocol.
The Advanced tab of the TCP/IP Properties dialog box.
TCP/IP Bindings
The Bindings tab shows which services use the TCP/IP protocol. File and printer sharing and the client for microsoft networks should not be bound to TCP/IP.
The Bindings tab of the TCP/IP Properties dialog box.
IE float bugTCP/IP should be bound to the LAN< adapter.
The Bindings tab of the Ethernet Adapter Properties dialog box.
IE float bugThe proper binding tree is illustrated below:
Binding Tree showing TCP/IP bound to the Local Network Adapter but not to the Client for Microsoft Networks.
IE float bugThe TCP receive window size (aka. DefaultRCVWindow) can be optimized on each client for DSL with the tcprw32k.reg registry update. More details on this modification and other DSL configuration options are at Navas Cable Modem/DSL Tuning Guide.
Winipcfg
The Windows IP Configuration utility can be used to display TCP/IP configuration parameters. Enter Run… > winipcfg and click the More Info» button to open the window in the capture below. Client21 is at 192.168.0.19 and is connected to the Internet gateway at 192.168.0.1. The blank DHCP Server entry indicates that DHCP services have been disabled on the local network.
The IP Configuration window showing current TCP/IP adapter parameters.