Installing TCP/IP in Windows 98
Preparing to Install TCP/IP
Now that you have a little background in how
TCP/IP works, you're almost ready to install, configure, and begin using TCP/IP
on your Windows 98 workstation. Before you begin the installation procedure,
however, you need to gather together the information you must provide when you
configure TCP/IP. In particular, you need to know the following information:
- Network address and domain. If you
set up a new TCP/IP network that you intend to eventually connect to the Internet,
you must register with InterNIC for a unique domain name and network IP address.
Even if you do not plan at this time to connect the network to the Internet,
you still should acquire a unique domain name and network address from InterNIC
for future compatibility.
- IP address. Determine whether your
workstation will use static IP addressing or will obtain an IP address from
a DHCP server. If you require a static address, contact your system administrator
for an address, or if you are the administrator, assign an available address
for the workstation. If you plan to use DHCP to acquire an IP address dynamically,
or you dynamically acquire an IP address from a PPP dial-up router, you do
not need to know the IP address of the DHCP server or router.
- Subnet mask. You must know the appropriate
subnet mask for your subnet. If yours is a standard, full class C network
with fewer than 254 hosts, your subnet mask should be 255.255.255.0. If you're
not sure what your subnet mask should be, contact your system administrator.
- WINS. Determine whether your network
provides one or more WINS servers for name resolution. If so, you need to
know the IP address of the primary WINS server, as well as the IP address
of a secondary WINS server if you choose to use a secondary server. If your
workstation uses DHCP, however, you need not know the IP addresses of the
WINS servers — DHCP automatically resolves them. If your network uses
NetBIOS over TCP/IP, you might need a scope ID. If you're not sure, check
with your system administrator.
- Default gateway(s). If your subnet
is connected to other networks or to the Internet, you need to know the IP
address of the gateway (router) through which IP routing is accomplished.
If your network has access to multiple gateways, you can specify multiple
gateways to provide fault tolerance and alternative routing.
- Domain name resolution. You must know
the domain name of your network, as well as the host name you use. The host
name defaults to the computer name assigned to the computer at startup, which
you specify through the Identification property page for your Network settings.
If you use DNS for name resolution, you must know the IP addresses of the
DNS servers you use.
- Bindings. You must know which clients
and services use the TCP/IP protocol. If you dial into a server for TCP/IP
access (such as dialing into an Internet service provider or an NT Server)
to gain Internet access, you do not need to bind TCP/IP to any clients or
services. If you use TCP/IP as your only protocol and want to dial into a
server to access files and other shared resources, or you want to share your
resources, you must bind TCP/IP to the appropriate client and service, such
as Client for Microsoft Networks and the File and Printer Sharing for Microsoft
Networks (or corresponding client and service for NetWare networks). If you
use TCP/IP over a LAN, and no other protocol provides sharing services, you
need to bind TCP/IP to your network client and sharing service.
Tip
If you are configuring TCP/IP for use only with Dial-Up Networking, you do
not have to worry about configuring any TCP/IP settings through the Network
object in the Control Panel. You set these values through the Dial-Up Networking
connection properties.
Installing TCP/IP in Windows 98
Before you can begin taking advantage of TCP/IP,
you naturally have to install it. Of all network protocols, TCP/IP is the most
complex to install and configure owing to its many settings and options. This
section explains those settings and options, beginning with the installation
process.
Note
If you have not read the previous section of this chapter, you should do so
to learn what items of information you need before you install and configure
TCP/IP.
Installing Microsoft TCP/IP
Microsoft TCP/IP installs like any other network
transport protocol — through the Control Panel. To install TCP/IP, open
the Control Panel and choose the Network object. From the Configuration property
page, choose the Add button. Windows 98 displays a Select Network Component
Type dialog box from which you can choose the type of network component you
want to install. Select Protocol from the supplied list, then choose Add. Windows
98 displays a Select Network Protocol dialog box similar to the one shown in
Figure 26.1. From the Manufacturers list, select Microsoft. Then, from the Network
Protocols list, select TCP/IP.
After you choose OK, Windows 98 adds the TCP/IP
protocol to your PC, copying files as necessary from the Windows 98 distribution
disks or CD. After it copies the files, the TCP/IP protocol appears in the installed
components list on the Configuration property page. If you have more than one
adapter, Windows 98 adds TCP/IP to each one. If your workstation contains a
network adapter, for example, and you also use the Dial-Up Adapter for remote
access, Windows 98 binds TCP/IP to both adapters. If you need TCP/IP on only
one adapter, select the instance of the TCP/IP protocol that you don't need,
then choose Remove.
