Networks

This section is not covered in Exam 220–604.

This section covers a detailed study of fundamental aspects of networks. We will also review the basic concepts already covered in the A+ Essentials Study Guide.

Before you install or configure network adapters and drivers and connect to a network, you must be familiar with different networking topologies, standards, protocols, services, and connectivity technologies. This section provides some basic information about networking fundamentals.

Networking protocols provide ways for computers to communicate with each other through the networking media. In this section, we will discuss the features of different networking protocols, as well as their advantages and limitations.

The Transmission Control Protocol/Internet Protocol (TCP/IP) is a set of several protocols. It is the most widely used protocol suite in private networks as well as on the Internet. Unlike the AppleTalk and IPX/SPX protocols, TCP/IP is not proprietary to any organization but is a public protocol suite. Needless to say, it is a fully routable protocol. The routing functionality is provided by a number of routing protocols such as RIP and OSPF. The TCP/IP protocol suite is supported by all major network and desktop operating systems. Some of the well-known protocols and their functions are discussed later in this section.

The following are some of the main configuration settings on a typical computer:

IP address

An IP address is a unique address used to identify a computer or a host on the network. This address is made up of 32-bit numbers written in dotted decimal notation in the w.x.y.z format. Each eight bits are known as an octet or a byte. A part of the IP address is known as the network address or network ID and the rest of it is known as the host address or host ID. These parts are based on the class of IP addresses used on the network. All computers on a particular network must have the same number as the network address, while the host address must be unique on the entire network.

Subnet mask

Every IP address is accompanied by a subnet mask. It is used to help identify the part of the network where the host is located. Like the IP address, the subnet mask is a 32-bit binary number that distinguishes the network ID from the host ID.

Default gateway

A default gateway allows computers on a network segment to communicate with computers on another segment. The default gateway for all computers on a particular segment is the IP address of the router interface that is connected to the local segment. If a computer is not configured with the IP address of a default gateway, it cannot communicate with computers on a different network segment.

DNS address

The IP address of a DNS server is configured on TCP/IP hosts so that all name resolution queries are sent to the designated DNS server. Most network and desktop operating systems allow you to configure multiple DNS servers.

WINS address

The IP address of a WINS server is configured to resolve NetBIOS name resolution queries. As with the DNS address, you can configure more than one WINS server address on a TCP/IP host.

Static IP addressing

When static IP addressing is used, network administrators manually configure all TCP/IP settings on a computer. This method is useful only on very small networks.

Automatic IP Addressing

TCP/IP hosts can be configured to obtain IP address configuration automatically from a Dynamic Host Configuration Protocol (DHCP) server. This is the default configuration on most desktop and server operating systems.

DNS stands for Domain Name System. The DNS service is used to translate fully qualified domain names (FQDN) to their respective IP addresses. Large corporate networks and all hosts on the Internet use FQDN notation to identify computers on the network. A fully qualified domain name can consist of a maximum of 63 characters including the dots. An example of a fully qualified domain name is www.us.books.oreilly.com.

DNS servers on a network run the DNS service and are responsible for resolving DNS queries for their clients. They can do it either by themselves or by having the queries resolved though referring to another DNS server. DNS clients are configured to use one or more DNS servers when configuring their TCP/IP properties.

Ethernet networking and cabling technologies are defined in IEEE 802.3 standards. There are several variations in this standard—depending on speed, length, topology, and cabling—used in implementing networks. The following sections provide a brief summary of the standards tested on the A+ exam.

A WAN consists of two or more interconnected connect LANs. Usually a third party, a telephone company, or an ISP is involved in providing a connectivity solution to the organization that needs to set up a WAN. A WAN can be set up using a dial-up telephone line for low-bandwidth requirements or may be set up using a high-bandwidth dedicated line. It is also possible to tunnel the WAN connection through the Internet. The following sections describe various technologies used for WAN connectivity.

DSL is a family of technologies that uses ordinary analog telephone lines to provide digital data transmissions. It uses different frequencies for voice and data signals; the same telephone line can simultaneously be used for phone and data transfer. It is commonly used for high-speed Internet access from homes and offices. Different DSL technologies are collectively noted as xDSL and support data transfer speeds from 128 Kbps to 24 Mbps, as discussed in the following list:

Table 5-13 provides a summary of different DSL variations and their data transfer speeds.

Wireless networks rely on radio frequencies to communicate instead of the network cabling used for normal computer networks. Radio frequencies create electromagnetic (EM) fields, which become the medium to transfer signals from one computer to another. As you go away from the hub, or from the main equipment generating the radio frequency of the wireless network, the strength of the EM field reduces and the signal becomes weak.

Wireless networks defined in IEEE 802.11 standards use radio frequencies with spread spectrum technology. The two spread spectrum technologies are as follows:

The most popular of the IEEE 802.11 wireless network standards are 802.11b, 802.11a, and 802.11g. Table 5-15 gives a brief comparison of the characteristics of different 802.11 standards.

Infrared technology employs electromagnetic radiations using wavelengths that are longer than the visible light but shorter than radio frequency. Common examples of Infrared devices are the remote controls used in TVs and audio systems. The following are some of the key characteristics of IrDA wireless communication technology:

This section covers fundamental concepts of installing and configuring network adapters and drivers as well as configuring their properties on a Windows desktop. It also discusses some troubleshooting utilities and diagnostic procedures to resolve common network connectivity problems.

The first step in establishing network connectivity for a computer is to obtain a network connection from the network administrator. The network administrator provides an available port on the network hub or switch where the new desktop can be connected. From the desktop technician, the connection is available in the form of a UTP or STP network cable attached to a male RJ-45 connector. This cable is attached to the female RJ-45 socket on the network adapter installed on the desktop.

Most new desktops come equipped with built-in network adapters. In newer computers, the network interface is integrated with the motherboard. But you might have to install, replace, or upgrade network adapters in some old desktops. For example, you might be asked to replace a 10 Mbps network adapter with a 10/100 Mbps fast network adapter. When installing a network adapter, you will need to make sure of the following:

Most new network adapters are PnP. PnP adapters are automatically detected and configured by most operating systems. This configuration includes setting aside system resources such as IRQ, I/O, and DMA for the adapter as well as installation of an appropriate driver.

In case the network adapter is not PnP, you will be required to install the network driver manually (you will need to obtain the driver, which may be available either on the CD-ROM accompanying the network adapter or from the vendor's web site). On Windows XP and Windows 2000 Professional computers, you can use the Add/Remove Hardware applet in the Control Panel to add the network adapter. The Device Manager snap-in can be used to install the network adapter device driver.

On Windows XP and Windows 2000 Professional computers, you can join a workgroup or a domain during or after the installation of the operating system. In case the computer will join an existing workgroup, you will need the name of the workgroup or you can create a new one. The steps that are shown next explain how you can change the network settings on Windows XP or Windows 2000 Professional computers.

In case the computer will join an existing domain, you will need the following information from the domain administrator:

On NetWare platforms, you will need Supervisor rights in the NDS tree that you are trying to join. The following information is required when configuring a desktop to join an NDS Tree:

The directory context and tree names can sometimes be too complex for a user to remember. To get around this problem, it is a common practice to configure the user's desktop with context and tree names.

The main purpose of creating networks is to share resources. File and folder sharing is one of the fundamental tasks of a network technician. In a workgroup environment, each user is responsible for sharing files and folders on her desktop and to configure appropriate permissions for other network users. In large networks such as Windows domain or NetWare NDS tree environments, these actions are performed by administrators and supervisors respectively. In the following sections, we will look at some basic steps required to configure file and folder permissions.

File- and folder-level permissions are managed in Windows XP and Windows 2000 Professional computers using the filesystem. Disk partitions formatted with NTFS filesystem support both folder- and file-level permissions. FAT and FAT32 filesystems support only folder-level permissions. Tables 5-16 and5-17 list standard NTFS file and folder permissions respectively.

The preceding permissions can be set to Allow or Deny any user or group. By default, administrators and owners of the file or folder get Full Control permissions. Permissions can be assigned to users and groups from the Security tab of the file or folder properties window, as shown in Figure 5-16.

The following steps explain how NTFS permissions can be configured for a user or a group:

As a computer support technician, you will frequently be tasked with configuring Internet settings on desktop computers. This section covers configuration of network browsers, including enabling and disabling of scripts, configuring browsers to use a proxy server, and configuring security settings. Fundamental knowledge of these settings will help you perform these tasks correctly and conveniently.

In addition to installation, configuration, and upgrading computer-related hardware and software, troubleshooting network problems is an on-going task for most support technicians. This includes attending to regular support calls, problems caused by equipment failure, improper configuration of devices, user mistakes, and lack of preventive maintenance. This section covers identification and resolution of network problems using common diagnostic tools and utilities.

Most network equipment, operating systems, and software applications come with built-in diagnostic tools to help technicians and administrators diagnose and resolve problems. As far as networks are concerned, there are some diagnostic tools that are available on most operating systems as well as on network equipment. This section covers troubleshooting network problems using some of these common tools and utilities.

ipconfig is a command-line utility used on Microsoft Windows operating systems to diagnose TCP/IP configuration problems. It can be used to display, release, and renew the IP address configuration of Windows computers. In Windows 2000, Windows XP, and Windows Server 2003 operating systems, this utility can also release and renew a computer's IP configuration with the domain name system (DNS) servers.

The ipconfig utility is commonly used with the /all parameter to display complete TCP/IP configuration of all network adapters installed on a computer. You can also select a particular adapter to view its configuration. It can reveal one or more configuration problems, and an administrator can take necessary corrective action to resolve the problem.

Table 5-18 lists the parameters and their functions available with the ipconfig command.

On Windows XP, Windows 2000, and Windows Server 2003 operating systems, the ipconfig utility also includes the following parameters:

When troubleshooting a TCP/IP problem on a particular computer, you may verify the configuration parameters using the ipconfig /all command. For example, if the output shows the IP address and the subnet mask as 0.0.0.0, you can be sure that the TCP/IP configuration of the computer is invalid. In this case, you can use the following two commands to renew the TCP/IP configuration with a DHCP server:

C:\;>ipconfig /release
C:\;>ipconfig /renew

If a computer is not able to connect to any remote hosts, the default gateway address should be checked in the output of the ipconfig command. The default gateway enables a computer to connect to other hosts located in other network segments. This address is usually the IP address of a router interface connected to the local network segment. Similarly, on a Windows XP/2000/2003 system, if the host is unable to resolve DNS names, the ipconfig /flushdns command can be used to clear the DNS cache.

The tracert or traceroute utility is used to trace the route from one host to another in a TCP/IP network. All major operating systems and network devices support this utility in one form or another. The output format of this utility differs from one operating system to the next. It uses the Internet Control Message Protocol (ICMP) echo packets to trace the route to a specific destination host and reports back the results at every hop on the path.

The syntax of the traceroute command in different operating systems is as follows:

The traceroute utility provides very useful information when diagnosing connectivity problems. It provides the IP address of every router (hop) that it passes through and reports the time it takes from one hop to another. This is helpful in diagnosing the exact location of the network bottleneck or congestion.

It is easy to interpret the results of the tracert utility. The first column shows the hop number, which is the network device that responds to the ICMP echo request. The next three columns show the roundtrip time in milliseconds that the packet takes. The next column shows the hostname and the IP address of the responding device.

In some situations, the network is congested. This is shown as "Request Timed Out" in the output. This may be due to a misconfigured router at the seventh hop. But the trace continues to the next hop until it reaches the destination. Once the problem device is identified, you may use some other utility such as ping to pinpoint the source of the problem.

The nslookup utility is used to diagnose problems related to the domain name system (DNS) services. In other words, it is used to resolve name resolution problems. This utility can be used to perform name resolution queries against specified DNS servers or display information about currently configured DNS servers on a local host.

The nslookup utility can be executed in either noninteractive mode or interactive mode.

In order to resolve a hostname using a specific DNS server, you can use the following command instead:

C:\; >nslookup www.oreilly.com 192.168.1.5

You can also use nslookup to resolve IP addresses to hostnames as shown in the following example.

C:\; >nslookup 208.201.239.36

Cable-testing devices, or cable testers, are used to test whether the cable is working properly. Several different types of methods exist for testing cables. A small multimeter is perhaps the simplest tool for testing continuity in cables. Cable continuity verifies that wires are not broken. Copper-based media testers rely on electrical signals to test the cables. If the electrical current passes through the cable without a break, the cable is considered to be good. Electrical signals are very helpful in testing the continuity of a coaxial cable. For a UTP cable, you will need to test continuity for each individual wire.

Network problems often result due to improper configuration of network adapters, drivers, and protocols. When all of these are correctly configured, the problem may further be attributed to permissions assigned to shared network resources. Improperly configured port and protocol settings on security devices such as firewalls or proxy servers may also cause problems related to access of external networks such as the Internet. This section discusses some common issues that may cause network problems.

Every network adapter comes with a software component that provides an interface for the operating system and applications to interact with the network. While most network adapters are PnP devices, older network adapters must be correctly configured in order to enable them to interact with the system and the network. Like other devices on the computer, network adapters also use system resources such as Interrupt Request (IRQ), Input/Output Address (I/O Address), and Direct Memory Access (DMA). Older network adapters had to be manually configured to use these resources. It was not uncommon to see a large number of problems occurring due to resource conflicts. When two or more devices try to use the same resource, it results in system problems with one or both devices not able to function as expected.

If you are tasked with resolving a network problem in a system that has an old network adapter installed on it, make sure that it is correctly configured to use only free system resources. In most new computers, the PnP functionality takes care of dynamic allocation and sharing of system resources. When in doubt, you may verify resource conflicts in a system by using some built-in utility. For example, on Windows XP computers, you can use the System Information utility to detect problems caused by resource conflicts. This utility is located in the System Tools folder under Accessories. Figure 5-19 shows a sample output of the System Information utility.

If you suspect a network adapter or driver problem, you can check the Device Manager utility in Windows XP. This utility is provided as a snap-in under the Computer Management console. It makes it easy to view whether the device is functioning or not and allows you to view driver details, and update or uninstall a network driver. In case a network driver has been replaced with an incompatible driver, you can use the Roll Back Driver option to replace the driver with the one that was previously working properly. Figure 5-20 shows the Driver tab of the Network Adapter properties.

An incorrect network driver can also cause connectivity problems in a computer. Make sure that only network drivers that are fully supported by the vendor are installed. You must also verify that the operating system you are using supports the network adapter and the driver. In case the vendor updates the network adapter driver, you must first test the new version of the driver before installing it on any production server or desktop computer.

TCP/IP is the most widely used networking protocol to date. TCP/IP is in fact a suite of protocols that work together to provide connectivity solutions in most medium- to large-scale networks. If TCP/IP is the protocol used on your network, you must understand how the network adapters should be correctly configured to connect to the network and successfully access network resources.

Computers or hosts in a TCP/IP network connect to each other using IP addresses. Each network host is assigned an IP address, which should be unique in the entire network. The allocation of IP addresses can be done either statically (manually) or dynamically. Static IP address assignment is suitable only for a small network of about 10 computers. When manually assigning IP addresses, the following addresses must be configured correctly:

If any of the preceding addresses are incorrect, the computer will not be able to communicate to other computers. An incorrect or missing IP address will completely isolate the computer in the network. A missing subnet mask will not allow the computer to communicate to other computers, even in the same network segment. If the default gateway is missing or incorrect, the computer will not be able to communicate to other computers located on remote network segments.

In addition to the TCP/IP configuration settings just described, the computers must also be configured correctly for IP addresses of DNS servers and WINS servers. If the DNS server is not configured correctly or is missing, the computer will not be able to resolve hostnames to IP addresses. Figure 5-21 shows the manual TCP/IP configuration on a Windows XP computer.

The TCP/IP configuration can also be assigned automatically or dynamically using a Dynamic Host Configuration Protocol (DHCP) server. The DHCP server is configured with a pool of IP addresses called the DHCP scope. The DHCP server assigns IP addresses and other TCP/IP parameters to DHCP-enabled hosts for a limited period of time, called a lease. The DHCP clients must renew the lease before it expires. On Windows-based computers, the DHCP clients must try to renew the TCP/IP configuration with a DHCP server when 50 percent of the lease period expires. The default configuration of most Windows operating systems is to obtain TCP/IP configuration automatically from any available DHCP server.

Since the DHCP servers can be configured to service multiple network segments, it is possible that one or more DHCP scopes contain duplicate or overlapping IP address ranges. This causes the DHCP server to allocate duplicate IP addresses to network clients, which results in connectivity issues. DHCP scopes must be properly configured with the correct address scopes and correct addresses of DNS and WINS servers.

If you are tasked with resolving a TCP/IP configuration problem, you may use any of the built-in TCP/IP diagnostic utilities such as ipconfig (Windows NT/2000/XP/2003), winipcfg (Windows 95/98/Me), and ifconfig (Unix/Linux/MAC OS). These utilities are very helpful in locating the cause of the problem. A simple ping to the loopback address 127.0.0.1 also verifies that the TCP/IP protocol is correctly installed on the local computer.

As with the TCP/IP protocol, incorrectly configured network adapters are the main causes of network problems in a NetWare IPX/SPX network. It is essential to verify that all adapters are installed with correct settings and without hardware or software conflicts. The IPX/SPX configuration includes the following parameters:

If your network has a mix of NetWare and Windows servers, you might want to verify that Windows clients who wish to connect to NetWare servers have the NWLink IPX/SPX NetBIOS Compatible Transport Protocol installed. This protocol allows Windows clients to connect to NetWare servers. In Windows NT and older operating systems, the Gateway Service for NetWare (GSNW) is required to be installed on Windows servers to allow client access to Network servers. Besides this, Windows clients can directly communicate to NetWare servers using the Client Service for NetWare (CSNW).

When network connectivity is not an issue, resource access permissions can cause a number of service calls. Users who wish to access particular files, folders, or printers but do not have sufficient permissions will ultimately call helpdesk technicians to resolve the access problems. Assignment of resource access problems is mainly the responsibility of system administrators. In certain smaller networks, the network technicians may also be tasked with assigning and managing permissions to network resources such as a user's home directory.

Any user who needs to save files on a folder must have at least Write permissions on the folder. If this permission is missing or only a Read or Execute permission is assigned, the user might not be able to save her work to the designated folder.

On Windows server operating systems, administrators put users in groups and assign permissions to groups. A user can be a member of more than one group, with each group having a different level of access permissions. In such cases, user permissions are clubbed together and the highest level of permissions is granted. Similarly, share permissions and NTFS permissions can be assigned to resources. When there is a conflict between share and NTFS permissions, the most restrictive permissions are applied to a user.

Preventive maintenance of networks is performed to ensure that every component of the network works per expectations. Network administrators take all possible steps to prevent a breakdown of the network. This includes securing network connections, providing redundancy for network servers and services, restricting unauthorized access to network equipment, implementing a data backup plan, and keeping software updated with the latest service packs. The main purpose of preventive maintenance is to provide maximum uptime. This section explains the key factors behind preventive maintenance of networks.

Loose connections cause a majority of network connectivity problems. They are also the most frustrating when it comes to locating and troubleshooting problems. Network administrators and technicians must ensure that all cables, connectors, patch panels, and patch cables are of correct specifications. These must also be firmly attached to servers, workstations, printers, network hubs, switches, and routers. Cables must not be loosely attached to connectors, and the correct type of cables should be in use.

Cables are run from network hubs, switches, or routers to end stations. It is important to label each end of the cable, which makes it easy to locate a faulty cable and replace it if necessary. It is not possible to trace a faulty cable from a workstation to a hub or switch in a large network if there is no labeling system in place. If the cables are labeled, you can easily find out which cable needs to be replaced. Cables must be periodically checked for loose connectivity or wear-and-tear, and worn out cables should be replaced with new ones.

Another important aspect of securing network cables is the routing of cables. Improper routing of cables results in damaged or broken cables. Network cables should always be run in designated areas. Cables should not be running in areas where people usually walk. People can get trapped in loose cables on the floor and may fall down and get injured besides causing connectivity problems. Make sure that all cables are securely and firmly attached to computers, printers, and network devices.

Documentation always helps. A layout diagram of the network cabling is very helpful in troubleshooting network connectivity problems. It is also helpful if you need to expand the network due to the growing business requirements of the organization. It is easy to help new network technicians understand the network layout if you have appropriate network documentation.