Upgrading and Repairing PCs (17th Edition)

2017-07-07 02:10:07

You've bought or built your cables, bought your NICs and hub, and located your Windows CD-ROM. Now it's time to make your network a reality!

In this section is a detailed checklist of the hardware and software you need to build your network.

First, start with the number of computers you plan to network together. You need the items discussed in the following sections to set up your network.

Network Adapter

You need a network adapter for every computer on the network that doesn't have a network port or wireless network adapter already included; if the computer has a built-in network port or wireless network adapter, be sure it will work with your network.

Traditionally, network adapters are also called network interface cards (NICs), but the widespread use of USB devices and built-in ports makes this term less accurate. To simplify technical support, use the same model of NIC for each computer in your network (if possible). If you are creating a Windows Server or Novell NetWare network with a dedicated server, you should buy server-optimized NICs for the server and less-expensive client NICs for the client PCs. However, you should still purchase the same brand to simplify support issues. Some vendors use the same driver for both their server and client NICs, further simplifying your support issue.

For the best performance, I recommend that you use PCI-based NICs for desktop computers or PC Card CardBus NICs for notebook computers with CardBus slots (CardBus and PCI slots have a 32-bit wide data bus, whereas typical PC Card slots have a 16-bit data bus). USB devices are more convenient, but USB 1.1 devices are much slower than 10/100 Ethernet. USB 2.0 devices are a satisfactory substitute for 10/100 Ethernet but require that both the computer and the device be USB 2.0compliant to achieve the 480Mbps speed of USB 2.0. If either the device or the computer is only USB 1.1compliant, the connection is limited to 12Mbps.

You should record the brand name and model number of the network adapters you are using, as well as the driver version or source. Use Table 18.11 in the "Recording Information About Your Network" section, later in this chapter, as a template for storing this information.

Table 18.11. Network Hardware Worksheet
Network Type: ___________________	Number of Stations: ___________________	Internet Sharing: ___________________
Computer Location/ID: ___________________	Brand Name/Model: ___________________	NIC Brand/Model: ___________________	Speed: ___________________
Driver: ___________________	Cable Type/Wiring Standard: ___________________	Cable Length: ___________________
Hub/Switch Location/ID: ___________________	Hub/Switch Brand/Model: ___________________	Hub/Switch Speed: ___________________
No. Ports: ___________________	Hub or Switch: ___________________
Router Location/ID: ___________________	Router Brand/Model: ___________________	Router Speed: ___________________
No. Ports: ___________________	Router IP Address: ___________________	Router Password: ___________________

Installing the Network Adapter

Before you can connect computers to the network, you must install network adapters. If the network adapter is an internal card, follow this procedure:

Open the case and locate an open expansion slot that matches the type of NIC you purchased (preferably PCI).

Using a screwdriver, remove the screw securing the slot cover at the rear of the case.

Insert the card gently, ensuring that the edge connector is seated solidly in the slot.

Fasten down the card with the same screw that held the slot cover.

	See Figures 20.26 and 20.27 in Chapter 20, "Building or Upgrading Systems," p. 1256, for an example of installing an add-on card.

Tip

If you are a realist like me, you might not want to close the case until you are certain the NIC is working (see the next section, "Testing Your Network Adapters and Connections").

A NIC uses the same hardware configuration settings most other expansion cards use:

An IRQ

An I/O port address range

Note

Some older network cards might require an upper memory block range for RAM buffers. Cards used on diskless workstations use a boot ROM, which also requires an upper memory block range. See your network card's documentation to find out whether this issue applies to you.

If you are using Windows 9x or newer with a PnP (Plug and Play) BIOS and a PnP NIC, the computer and Windows configure your card for you in most cases. In a few cases, you might need to adjust PnP settings in the BIOS, and in a rare case you might even need to remove your other PnP cards and put the NIC in first if your system doesn't recognize it after you restart the system.

	For general BIOS information, see Chapter 5, "BIOS," p. 411, or see your system manual for details about your computer's BIOS.

If you install the card in a non-PnP system or under Windows NT, be sure the card comes with configuration software or manual switch settings for hardware configuration. A pure PnP card can't be installed on a system that lacks PnP support.

USB and PC Card/CardBus network adapters are automatically detected and installed when connected because USB ports and PC Card/CardBus slots are hot-swap connections.

And, if you are using an older network adapter with Windows XP, you might need to download drivers from the adapter vendors' websites. Even if you have drivers for your current version of Windows, getting the latest driver release will help you avoid setup and installation problems.

Testing Your Network Adapters and Connections

The configuration software disk or CD-ROM included with the network adapter usually features diagnostic software. Some diagnostics should be performed before the card is connected to the network and should be run from a command prompt.

After the network adapter passes these tests, connect the network adapter to the network. With an Ethernet network using UTP cable, run the cable from the card to the hub or switch, turn on the computer and hub, and watch for signal lights to light up on the NIC's back bracket (if so equipped) and on the hub or switch. Hubs and switches use green LEDs to indicate the presence of a computer on a particular RJ-45 port. Connect a second computer with NIC installed to the hub or switch. Then, run the diagnostics program on both computers to send and receive data. For other types of networks, see the diagnostics provided with the network hardware for testing details.

Cables and Connections Between Computers

Depending on the network architecture you choose, you might need to run cables. If you are installing a 100BASE-TX, or 1000BASE-TX Ethernet network (both of which use UTP cables), you need cables that are long enough to reach comfortably between each computer's network port and the network's hub or switch. Use Table 18.11 in the "Recording Information About Your Network" section, later in this chapter, as a template for storing this information.

Because HomePNA networks are based on your existing telephone line, the patch cord included with the NIC is usually long enough to connect with your existing RJ-11 telephone jack. The HomePNA NIC has two jacks: one for the connection to the telephone line and the other to enable you to connect your telephone to the NIC. Be sure you use the correct jack for each cable; otherwise, your network won't work. HomePNA enables you to use your telephone system for voice and networking at the same time.

Wireless network NICs use an external antenna to make the connection between computers. In some cases, the antenna is built in to the NIC, whereas in other cases the antenna is attached to the NIC or needs to be extended from a storage position inside the NIC.

Hub/Switch/Access Point

UTP Ethernet networks require a hub or switch if more than two computers will be networked (you can use a crossover cable between two computers only). Wireless Ethernet networks also require an access point if more than two computers will be networked, or if the network will be used to share an Internet connection.

For a UTP-based Ethernet network, buy a hub or switch (preferred) of the correct speed with at least enough RJ-45 ports for each computer on the network. For a wireless Ethernet network, you will need at least one access point, depending on the range of your wireless network. Most IEEE 802.11b/Wi-Fi network access points have a range of 150 feet indoors (and up to 300 feet outdoors), which should be adequate for most homes and many small businesses. You can add more access points if you need a wider area of coverage.

If you are going to use the network to share Internet access, you can save money if you buy a router that contains a switch for a wired Ethernet network or a wireless access point that contains a router for a wireless Ethernet network.

Use Table 18.11 in the "Recording Information About Your Network" section as a template for storing this information. Table 18.11 also provides a space for recording whether you plan to use the network for Internet sharing.

Gateways for Non-Ethernet Networks

If you plan to share Internet access through a non-Ethernet network such as HomePNA or HomePlug and you don't want to use a software-sharing solution such as Microsoft Internet Connection Sharing, you must install a gateway or router between the broadband device (such as a cable or DSL modem) and your network. Some gateway/router devices can also act as print servers; in addition, some, such as those from 2Wire, support HomePNA, Ethernet, or Wi-Fi networks.

Recording Information About Your Network

Networks are terrific when they work, but they're a potential nightmare when they fail. By keeping careful notes about network configuration, you can reinstall network drivers, set up new computers on the network, and handle other network crises without breaking a sweat.

Use the worksheet shown in Table 18.11 as a guide for recording information about your network hardware.

Installing Networking Software

To access network resources with a PCwhether it is connected to a client/server or peer-to-peer networkyou must install network client software on the computer. The network client can be part of the operating system or a separate product, but it is this software that enables the system to use the network interface adapter to communicate with other machines.

On a properly configured network workstation, accessing network resources is no different from accessing local ones (except that they might be slightly slower). You can open a file on a network drive just as you would open the same file on your local hard disk. This is because the network client software is completely integrated into every level of the computer's operating system.

In most cases, the network client software is part of the operating system. Windows 9x, NT, 2000, and XP, for example, include all the software you need to participate in a peer-to-peer Windows network or to connect to Windows NT, Windows 2000, Windows Server 2003, and Novell NetWare servers. To connect to a network using DOS or Windows 3.1, however, you must install a separate client software package.

When you install a NIC under Windows 95 or Windows 98, the following network protocols are installed by default:

NetBEUI

TCP/IP

IPX/SPX

Windows Me, Windows 2000, and Windows XP use TCP/IP by default. If you need to install particular protocols or other network components, use the Networks icon in the Windows Control Panel or right-click the Network Neighborhood (Windows 9x) or My Network Places (Windows Me/2000) icon on the Windows desktop and select Properties. If you need to use NetBEUI with Windows XP, it must be manually installed from the Windows XP CD-ROM.

Configuring Your Network Software

You might have a few problems installing your NICs. They might pass their diagnostics flawlessly, but until each station on your network can speak the same language, has correct client or server software setups, and uses the same protocols, your network will not function properly.

Table 18.12 shows the minimum network software configuration you must install for Windows 9x/Me, Windows NT, Windows 2000, and Windows XP peer-to-peer networking.

Table 18.12. Minimum Network Software for Peer-to-Peer Networking
Item	Workstation	Server
Windows Network client	Yes	No
NetBEUI or TCP/IP^[*] protocol	Yes	Yes
File and print sharing for Microsoft Networks	No	Yes
NIC installed and bound to protocols and services above	Yes	Yes
Workgroup identification (same for all PCs in workgroup)	Yes	Yes
Computer name (each PC needs a unique name)	Yes	Yes

^[*] If TCP/IP is used as the standard protocol, each workstation must have a different IP addresseither manually assigned or received from a DHCP server built in to a server, router, or gateway computer or device.

Although the networking settings in Table 18.12 enable a Windows peer-to-peer network to function, you might need to add more networking components. If the computer can access a Novell NetWare client/server network running NetWare 4.x, the IPX/SPX protocol must also be installed. It also might be required for certain operations with NetWare 5. If the computer is used to access the Internet or any other TCP/IP-based network, the TCP/IP protocol must also be installed. In most cases, you can now use TCP/IP as the only network protocol because it can be used for both Internet and LAN access.

Use the Network icon in the Windows Control Panel to select your network settings. To set up your network, you'll need the operating system CDs, disks, or hard-disk image files and the network adapter drivers. (Workgroup hubs and switches require no software.)

To install a network component, follow this procedure:

1.	Open the Network icon in the Control Panel.
2.	The Configuration tab is displayed; select Add.
3.	Select from the following: Client. Select if you want to install the Microsoft or other network clients for your network. Every PC on a peer-to-peer network needs the Client for Microsoft Networks. Adapter. This should already be installed, but you can use this to install a new adapter. Protocol. For a simple, non-Internet network with versions of Windows before XP, install NetBEUI. If you want to use Internet Connection Sharing along with networking, install both TCP/IP and NetBEUI. With Windows XP, use the Network Setup Wizard to configure TCP/IP easily. Service. Install File and Printer Sharing for Microsoft Networks on any computer that will be used as a server.
4.	Click the Identification tab. Enter a unique name for each computer on the network; use the same workgroup name for all computers on the network.
5.	Click OK. Supply the Windows CD-ROM or other media as necessary to install the network components you requested.
6.	You are prompted to insert a CD or disk or browse to the appropriate files during the installation procedure, if they're not available on the Windows 9x CD-ROM or on your hard disk in the default location.

You might need to reboot your PC to complete the process, particularly if you're using Windows 9x or Me. After this is completed, you'll be ready to share resources.

After the network hardware and software installation is complete, your network is ready to use. However, if you are using Windows NT, Windows 2000, or Windows XP Professional, you must set up users and groups for security. Windows 9x, Me, and Windows XP Home use peer-to-peer access control, which can be protected with passwords if you desire.

For more information about these processes, see "Configuring Users, Groups, and Resources" in the Technical Reference section of the disc packaged with this book.