home | O'Reilly's CD bookshelfs | FreeBSD | Linux | Cisco | Cisco Exam    

TCP/IP Network Administration

TCP/IP Network AdministrationSearch this book
Previous: 2.8 Summary Chapter 3 Next: 3.2 The Host Table

3. Network Services

Some network servers provide essential computer-to-computer services. These differ from application services in that they are not directly accessed by end users. Instead, these services are used by networked computers to simplify the installation, configuration, and operation of the network.

The functions performed by the servers covered in this chapter are varied:

  • Name service for converting IP addresses to hostnames

  • Configuration servers that simplify the installation of networked hosts by handling part or all of the TCP/IP configuration

  • Electronic mail services for moving mail through the network from the sender to the recipient

  • File servers that allow client computers to transparently share files

  • Print servers that allow printers to be centrally maintained and shared by all users

Servers on a TCP/IP network should not be confused with traditional PC LAN servers. Every UNIX host on your network can be both a server and a client. The hosts on a TCP/IP network are "peers." All systems are equal. The network is not dependent on any one server. All of the services discussed in this chapter can be installed on one or several systems on your network.

We begin with a discussion of name service. It is an essential service that you will certainly use on your network.

3.1 Names and Addresses

The Internet Protocol document [1] defines names, addresses, and routes as follows:

A name indicates what we seek. An address indicates where it is.
A route indicates how to get there.

Names, addresses, and routes all require the network administrator's attention. Routes and addresses are covered in the previous chapter. This section discusses names and how they are disseminated throughout the network. Every network interface attached to a TCP/IP network is identified by a unique 32-bit IP address. A name (called a hostname ) can be assigned to any device that has an IP address. Names are assigned to devices because, compared to numeric Internet addresses, names are easier to remember and type correctly. The network software doesn't require names, but they do make it easier for humans to use the network.

[1] RFC 791, Internet Protocol , Jon Postel, ISI, 1981, page 7.

In most cases, hostnames and numeric addresses can be used interchangeably. A user wishing to telnet to the workstation at IP address can enter:



or use the hostname associated with that address and enter the equivalent command:


telnet peanut.nuts.com

Whether a command is entered with an address or a hostname, the network connection always takes place based on the IP address. The system converts the hostname to an address before the network connection is made. The network administrator is responsible for assigning names and addresses and storing them in the database used for the conversion.

Translating names into addresses isn't simply a "local" issue. The command telnet peanut.nuts.com is expected to work correctly on every host that's connected to the network. If peanut.nuts.com is connected to the Internet, hosts all over the world should be able to translate the name peanut.nuts.com into the proper address. Therefore, some facility must exist for disseminating the hostname information to all hosts on the network.

There are two common methods for translating names into addresses. The older method simply looks up the hostname in a table called the host table . [2] The newer technique uses a distributed database system called Domain Name Service (DNS) to translate names to addresses. We'll examine the host table first.

[2] Sun's Network Information Service (NIS) is an improved technique for accessing the host table. NIS is discussed in a later section.