Prof. Michael P. Harris, CCNA CCAI
ITNW 1454 – Implementing & Supporting Servers
Chapter 6
Networking Protocols
Implementing & Supporting Servers - Chapter 6
Networking Protocols
Chapter Overview
In this chapter, we discussed the positive and negative features of the major protocols used
today, including which protocols function with what operating systems. Here are some key
points to remember.
Learning Objectives
Objective 2.3: Differentiate between the following network protocols in terms of routing,
addressing schemes, interoperability, and naming conventions:
 TCP/IP
 IPX/SPX
 NetBEUI
AppleTalk
Lecture Notes
TCP/IP
TCP/IP is a suite of protocols that allows nodes to communicate with each other in a network
environment without regard to the type of machine or operating system on that machine.
This suite contains two core protocols, IP and TCP. IP is a connectionless protocol used for
transport at the Network layer of the OSI Model. IP manages logical addressing and routing
functions for packet delivery. TCP is a connection-oriented Transport layer protocol that
manages reliable delivery of packets. Error checking, sequencing, and retransmission of lost
or corrupt packets are functions of TCP. The original developers of TCP/IP were the military
and academic institutions. Logical addressing in TCP/IP is necessary to route packets
between networks or internetworks. IP provides fragmentation services, packet timeout
services, and many options for transporting packets. The two most important fields in the IP
header are the source and the destination address fields. An IP packet header and the data
cannot exceed 65,535 bytes. When a node sends an IP packet, it compares the destination
address to its own address, determines the network identifier and either forwards the packet
to the router interface or attempts to deliver it on its own segment. Two protocols are used
to support routing services: RIP and OSPF. RIP is a distance vector routing protocol, meaning
that routing decisions are made on a number of criteria, including hop count, congestion,
speed of network, and other criteria. Friendly names are supported for nodes running
TCP/IP. DNS supports friendly names to IP address resolution services on the network.
Jerry K. Ainsworth, Kristine A. Kriegel, SYSTEM ADMINISTRATION
EMCParadigm ©2004
Page 1 of 3
ISBN: 0-7638-1972-7
Prof. Michael P. Harris, CCNA CCAI
ITNW 1454 – Implementing & Supporting Servers
Chapter 6
Networking Protocols
IPX/SPX
IPX/SPX is a Novell proprietary protocol used with all versions of Novell’s NetWare Products.
It was designed to support client-server architecture, using remote procedure calls to request
service and respond with service. It can also be used as a peer-to-peer network protocol.
Like TCP/IP, IPX/SPX supports two core protocols: IPX and SPX. IPX is a connectionless
protocol that manages a session between nodes, including error control and retransmission of
missing or corrupt packet, providing reliable delivery of data. SAP notifies the network when
a service is available. Done via a broadcast, this notification can congest bandwidth when the
network is busy. It may be necessary to filter SAP announcements at routers. NCP handles
requests for services between the client (workstation) and the server. This service protocol is
very reliable, but it can create large amounts of traffic. To form a logical address when using
IPX/SPX, the administrator must add a network identifier in a hexadecimal format. The
network identifier is 8 bits long. Once the network identifier is available, the node will
combine the network identifier and its own MAC address to form a unique node address.
IPX/SPX uses socket numbers to uniquely identify APIs and client requests to those APIs.
Often socket numbers are reserved by the NetWare operating system. Like TCP/IP, the two
most important fields in the IPX header are the source and destination node addresses. IPX
also includes individual fields for source and destination network, and source and network
socket. An IPX header will contain approximately 28 bytes of information plus the payload.
IPX routing employs two protocols: RIP for IPX and NLSP. RIP is a distance vector protocol,
making routing decisions solely on the number of hops to the destination network. NLSP is a
link state protocol, more efficient, and capable of making routing decisions on hop count
combined with bandwidth utilization, speed of network, and other criteria. IPX/SPX does not
require any specific naming conversations for workstations (clients), but requires that server
names use alphanumeric characters and do not exceed 64 characters length (old NetWare
versions are limited to 47 characters).
AppleTalk
AppleTalk is the protocol of Macintosh computers, originally designed for peer-to-peer
networks. Although a later version of AppleTalk supports internetworks and routing, it
remains best suited for smaller networks. Logical addresses in AppleTalk are formed when
the node attaches to the network. The address is an 8-bit or 16-bit number that will be
stored and used again. AppleTalk also uses network numbers to identify segments. The zones
divide the network into logical groupings for file sharing, printing, and other services. Nodes
using AppleTalk will broadcast their friendly name when attaching to the network. NBP will
cache the name and supply it to any node requesting a service.
NetBEUI
NetBEUI is an efficient, nonroutable protocol that is useful for small networks where Internet
connectivity is not needed. No configuration is needed for NetBEUI. All nodes using NetBEUI
must have a name. NetBIOS supports friendly names for NetBEUI. No Network layer services
are available with NetBEUI and NetBIOS, so these protocols are usually paired with other
routable protocols such as TCP/IP or IPX/SPX.
Jerry K. Ainsworth, Kristine A. Kriegel, SYSTEM ADMINISTRATION
EMCParadigm ©2004
Page 2 of 3
ISBN: 0-7638-1972-7
Prof. Michael P. Harris, CCNA CCAI
ITNW 1454 – Implementing & Supporting Servers
Chapter 6
Networking Protocols
Interoperability
TCP/IP is a versatile protocol that supports global connectivity without regard to operating
system. All major operating systems contain a TCP/IP protocol stack, including Microsoft
operating systems, NetWare server versions 5.X and 6.X, Linux, and UNIX. If an organization
allows Internet connectivity for users, the TCP/IP protocol must be implemented. IPX/SPX
does not support access to Internet sources, but it is robust network protocol. Many
operating systems include support for IPX/SPX. AppleTalk is native only to the Macintosh
computer; Microsoft includes AppleTalk compatible services with many of its operating
systems. NetBEUI is native to the IBM LAN Manager and Microsoft Windows products.
Because NetBEUI is nonroutable, it is suitable only for very small peer networks. Macintosh
has no provision for NetBEUI.
Jerry K. Ainsworth, Kristine A. Kriegel, SYSTEM ADMINISTRATION
EMCParadigm ©2004
Page 3 of 3
ISBN: 0-7638-1972-7