Network+ Guide to Networks,

Fourth Edition

Chapter 4
Network Protocols

Objectives

•! Identify the characteristics of TCP/IP, IPX/SPX,

NetBIOS, and AppleTalk
•! Understand how network protocols correlate to
layers of the OSI Model
•! Identify the core protocols of the TCP/IP suite and
describe their functions
•! Identify the well-known ports for key TCP/IP
services

Network+ Guide to Networks, 4e 2

 Objectives (continued)

•! Understand addressing schemes for TCP/IP, IPX/

SPX, NetBEUI, and AppleTalk
•! Describe the purpose and implementation of DNS
(Domain Name System) and WINS (Windows
Internet Naming Service)
•! Install protocols on Windows XP clients

Network+ Guide to Networks, 4e 3

Introduction to Protocols

•! Protocols vary according to purpose, speed,

transmission efficiency, utilization of resources,
ease of setup, compatibility, and ability to travel
between different LANs
•! Multiprotocol networks: networks running more
than one protocol
•! Most popular protocol suite is TCP/IP
–! Others: IPX/SPX, NetBIOS, and AppleTalk

Network+ Guide to Networks, 4e 4

 Chapter 4
Network Protocols – TCP/IP

TCP/IP (Transmission Control

Protocol/Internet Protocol)
•! Suite of specialized subprotocols
–! TCP, IP, UDP, ARP, and many others
•! De facto standard on Internet
–! Protocol of choice for LANs and WANs
•! Protocols able to span more than one LAN are
routable
•! Can run on virtually any combination of NOSs or
network media
•! TCP/IP core protocols operate in Transport or
Network layers
Network+ Guide to Networks, 4e 6
 The TCP/IP Core Protocols: TCP
(Transmission Control Protocol)
•! Provides reliable data delivery services
–! Operates in Transport layer
–! Connection-oriented
–! Ensures reliable data delivery through sequencing
and checksums
–! Provides flow control
•! Port hosts address where an application makes
itself available to incoming or outgoing data

Network+ Guide to Networks, 4e 7

The TCP/IP Core Protocols:

TCP (continued)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 8
 The TCP/IP Core Protocols:
TCP (continued)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 9

The TCP/IP Core Protocols:

TCP (continued)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 10
 The TCP/IP Core Protocols:
TCP (continued)

Port number at source node

– identifies application that
produced the TCP segment
(e.g. 21 FTP; 80 http; 110
POP3)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 11

The TCP/IP Core Protocols:

TCP (continued)

Port number at destination

node – identifies application
that will receive the TCP
segment (e.g. 21 FTP; 80
http; 110 POP3)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 12
 The TCP/IP Core Protocols:
TCP (continued)

We send our message in

segments. Because the segments
may not arrive in the proper order,
we assign segment numbers so
that we can reassemble our
message at the receiver.
Figure 4-1: A TCP segment
Network+ Guide to Networks, 4e 13

The TCP/IP Core Protocols:

TCP (continued)

ACK – Is sent to the sending

node to confirm receipt of
the data. If sender or source
doesn’t receive, data is
resent.
Figure 4-1: A TCP segment
Network+ Guide to Networks, 4e 14
 The TCP/IP Core Protocols:
TCP (continued)

Length of TCP header (4 bits)

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 15

The TCP/IP Core Protocols:

TCP (continued)

A 6-bit field reserved for future use

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 16
 The TCP/IP Core Protocols:
TCP (continued)
If set to “1” indicates that
URGent pointer field
contains information

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 17

The TCP/IP Core Protocols:

TCP (continued)
“1” – Acknowledgement field contain information
“0” – Ignore acknowledgement field

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 18
 The TCP/IP Core Protocols:
TCP (continued)
PSH or PuSH - If set to “1”
indicates that data should be sent
to application without buffering

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 19

The TCP/IP Core Protocols:

TCP (continued)

If set to “1” – sender is

requesting connection ReSeT

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 20
 The TCP/IP Core Protocols:
TCP (continued)

If set to “1” – sender is requesting

SYNchronization of sequence numbers
between the two communicating nodes.

Used at beginning of communication between

two nodes to establish a TCP connection.

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 21

The TCP/IP Core Protocols:

TCP (continued)
If set to “1” indicates that this is the last
segment is a sequence and the connection
should be closed or terminated.

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 22
 The TCP/IP Core Protocols:
TCP (continued)
Used for flow control – indicates
how many bytes can be sent
while waiting for an ACK

Example: Server indicates window size of 4000 bytes. Clients

has sent 1000 bytes, 250 of which have been ACK by server
– other 750 waiting in buffer at server. Client can still send
3250Amore
Figure 4-1: TCPbytes while waiting for ACK for the 750 in buffer.
segment
Network+ Guide to Networks, 4e 23

The TCP/IP Core Protocols:

TCP (continued)

Error checking: We use a shared mathematical

algorithm on our data to calculate the checksum –
if it does not match this field, our data has been
corrupted or alerted. In such cases, we discard the
corrupt data and request that it be resent.

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 24
 The TCP/IP Core Protocols:
TCP (continued)

Indicates a location in the data

field where urgent data resides

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 25

The TCP/IP Core Protocols:

TCP (continued)
Special options, for example
maximum segment size.

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 26
 The TCP/IP Core Protocols:
TCP (continued)
Filler information to ensure
that total TCP header size
is a multiple of 32 bits.

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 27

The TCP/IP Core Protocols:

TCP (continued)

This is our data! The size of the field

depends on how data we have, TCP
segment size, network type, limitations
of the IP datagram, etc

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 28
 The TCP/IP Core Protocols:
TCP (continued)

Figure 4-2: TCP segment data

Network+ Guide to Networks, 4e 29

The TCP/IP Core Protocols:

TCP (continued)

Figure 4-3: Establishing a TCP connection

Network+ Guide to Networks, 4e 30
 The TCP/IP Core Protocols:
TCP (continued)

Figure 4-2: TCP segment data

Network+ Guide to Networks, 4e 31

UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 32

 UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 33

UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 34

 UDP versus TCP

64 bits; simple

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 35

UDP versus TCP (continued)

minimum 160 bits=20 bytes; complex

Figure 4-1: A TCP segment
Network+ Guide to Networks, 4e 36
 UDP versus TCP (continued):
What’s missing?

Figure 4-1: A TCP segment

Network+ Guide to Networks, 4e 37

UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 38

 UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 39

UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 40

 UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 41

UDP (User Datagram Protocol)

Figure 4-4: A UDP segment

Network+ Guide to Networks, 4e 42

 IP (Internet Protocol)

•! Provides information about how and where data

should be delivered
–! Data’s source and destination addresses
–! Network layer protocol
–! Enables TCP/IP to internetwork
–! Unreliable, connectionless protocol
•! IP datagram: packet, in context of TCP/IP
–! Envelope for data

Network+ Guide to Networks, 4e 43

IP (continued)

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 44
 IP (continued)

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 45

IP (continued)

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 46
 IP (continued)

Version of the protocol –

IPv4 or IPv6

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 47

IP (continued)

Internet Header Length – the

number of 4-byte (32-bit)
blocks in the IP header

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 48
 IP (continued)

A field that informs a router what level of priority it

should use to process an incoming packet. Useful for
time-sensitive applications such as video and voice.
Figure 4-5: An IP datagram
Network+ Guide to Networks, 4e 49

IP (continued)

Total length of the IP datagram,

including header and data. Shown in
bytes – cannot exceed 65,535 bytes.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 50
 IP (continued)

Identifies the message to which a

datagram belongs. This is required for
reassembly of fragmented messages.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 51

IP (continued)

Indicates whether message is

fragmented and if so, whether this is
the last datagram of the fragment.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 52
 IP (continued)

Indicates where this fragment belongs

in the sequence of fragments.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 53

IP (continued)

TTL or Time To Live – Indicates how long a datagram

can remain on the network before it is discarded.
Usually represented by the number of hops – router
to router forwarding. Typical values are 32 or 64.
Figure 4-5: An IP datagram
Network+ Guide to Networks, 4e 54
 IP (continued)

The transport layer protocol that will

receive the datagram e.g. TCP or UDP
Figure 4-5: An IP datagram
Network+ Guide to Networks, 4e 55

IP (continued)

Error checking for IP

header corruption.
Figure 4-5: An IP datagram
Network+ Guide to Networks, 4e 56
 IP (continued)

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 57

IP (continued)

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 58
 IP (continued)

Optional routing and

timing information.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 59

IP (continued)

Filler information to ensure

that total TCP header size
is a multiple of 32 bits.

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 60
 IP (continued)

Our original data plus header

information from the Transport
Layer (TCP or UDP).

Figure 4-5: An IP datagram

Network+ Guide to Networks, 4e 61

IP (continued)

Figure 4-6: IP datagram data

Network+ Guide to Networks, 4e 62
 ICMP (Internet Control
Message Protocol)
•! Network layer protocol that reports on success or
failure of data delivery
–! Indicates when part of network congested
–! Indicates when data fails to reach destination
–! Indicates when data discarded because allotted time
for delivery (TTL) expired
–! Cannot correct errors it detects

Network+ Guide to Networks, 4e 63

IGMP (Internet Group

Management Protocol)
•! Network layer protocol that manages multicasting
–! Transmission method allowing one node to send
data to defined group of nodes
•! Point-to-multipoint method
•! Teleconferencing or videoconferencing over Internet
•! Routers use IGMP to determine which nodes
belong to multicast group and to transmit data to all
nodes in that group

Network+ Guide to Networks, 4e 64

 ARP (Address Resolution Protocol)

•! Network layer protocol

–! Obtains MAC (physical) address of host
•! Creates database that maps MAC address to host’s IP
(logical) address
•! ARP table or cache: local database containing
recognized MAC-to-IP address mappings
–! Dynamic ARP table entries created when client
makes ARP request that cannot be satisfied by data
already in ARP table
–! Static ARP table entries entered manually using
ARP utility
Network+ Guide to Networks, 4e 65

Network+ Guide to Networks, 4e 66

 RARP (Reverse Address
Resolution Protocol)
•! Allows client to broadcast MAC address and
receive IP address in reply
–! If device doesn’t know own IP address, cannot use
ARP
•! RARP server maintains table of MAC addresses
and associated IP addresses

Network+ Guide to Networks, 4e 67

Chapter 4
Network Protocols – IP Addressing
 Addressing in TCP/IP

•! IP core protocol responsible for logical addressing

–! IP Address: unique 32-bit number
•! Divided into four octets separated by periods
•! 0 reserved as placeholder referring to entire group of
computers on a network
•! 255 reserved for broadcast transmissions

Network+ Guide to Networks, 4e 69

IP Address Format

•! Every host in an IP network needs an IP address

•! IPCONFIG (Windows NT/2000/XP) to see what an
IP address looks like
 IP Address Format
•! An IP address
consists of 4
numbers, each
between 0 and 255
•! Each number is
separated by a
period
•! No IP address may
be all 0’s or all 255’s
•! Called dotted
decimal format

Dotted Decimal Format

•! Dotted decimal format is just convenient for us

•! Real IP addresses are expressed as a series of 0s
and 1s in binary format
•! Each number in dotted decimal format is shorthand
for a series of eight 0s and 1s (or bits) ranging from
00000000 to 11111111 (in decimal from 0 to 255)
called an octet
 Converting IP Addresses

•! IP addresses are converted between dotted

decimal format and binary format by converting
each of the octets individually

Converting Binary to Decimal

•! In the chart below the binary number 10010011 is
converted to decimal
 Converting Decimal to Binary
•! In the chart below the decimal number 49 is
converted to a binary number

Converting IP Addresses

11000101.10101001.01011110.01010010

197 . 169 . 94 . 82
 Addressing in TCP/IP (continued)

Figure 4-8: IP addresses and their classes

Network+ Guide to Networks, 4e 77

Addressing in TCP/IP (continued)

Network Beginning Number of Maximum Addressable

Class Octet Networks Hosts per Network
A 1-126 126 16,777,214
B 128-191 >16,000 65,534
C 192-223 >2,000,000 254

Network+ Guide to Networks, 4e 78

 Addressing in TCP/IP (continued)

•! Many Internet addresses go unused

–! Cannot be reassigned because they are reserved
–! IP version 6 (IPv6) will incorporate new addressing
scheme
•! Some IP addresses reserved for special functions
–! 127 reserved for a device communicating with itself
•! Loopback test
•! ipconfig: Windows XP command to view IP
information
–! ifconfig on Unix and Linux

Network+ Guide to Networks, 4e 79

Binary and Dotted Decimal Notation

•! Most common way of expressing IP addresses

–! Decimal number between 0 and 255 represents
each binary octet
–! Separated by period
•! Each number in dotted decimal address has binary
equivalent

Network+ Guide to Networks, 4e 80

 Subnet Mask
•! Every device on TCP/IP-based network identified by
subnet mask
–! 32-bit number that, when combined with device’s IP
address, informs rest of network about segment or
network to which a device is attached
•! Subnetting: subdividing single class of networks into
multiple, smaller logical networks or segments

Network+ Guide to Networks, 4e 81

Addressing in TCP/IP (continued)

Network Class Beginning Octet Default Subnet Mask

A 1-126 255.0.0.0
B 128-191 255.255.0.0
C 192-223 255.255.255.0

Network+ Guide to Networks, 4e 82

 Assigning IP Addresses

•! Nodes on a network must have unique IP

addresses
•! Static IP address: manually assigned
–! Can easily result in duplication of addresses
•! Most network administrators rely on network
service to automatically assign IP addresses

Network+ Guide to Networks, 4e 83

BOOTP (Bootstrap Protocol)

•! Uses central list of IP addresses and associated

devices’ MAC addresses to assign IP addresses to
clients dynamically
–! Dynamic IP addresses
–! Application layer protocol
–! Client broadcasts MAC address, BOOTP server
replies with:
•! Client’s IP address
•! IP address of server
•! Host name of server
•! IP address of a default router
Network+ Guide to Networks, 4e 84
 DHCP (Dynamic Host Configuration
Protocol)
•! Automated means of assigning unique IP address
to every device on a network
–! Application layer protocol
–! Reduces time and planning spent on IP address
management
–! Reduces potential for errors in assigning IP
addresses
–! Enables users to move workstations and printers
without having to change TCP/IP configuration
–! Makes IP addressing transparent for mobile users

Network+ Guide to Networks, 4e 85

DHCP (continued)

Figure 4-11: The DHCP leasing process

Network+ Guide to Networks, 4e 86
 APIPA (Automatic Private
IP Addressing)
•! Provides computer with IP address automatically
–! For Windows 98, Me, 2000, XP client and
Windows 2003 server
–! For situations where DHCP server unreachable
–! Assigns computer’s network adapter IP address from
predefined pool of addresses
•! 169.254.0.0 through 169.254.255.255
–! Computer can only communicate with other nodes
using addresses in APIPA range

Network+ Guide to Networks, 4e 87

Addressing in IPv6

•! IPv6 slated to replace current IP protocol, IPv4

–! More efficient header, better security, better
prioritization
–! Billions of additional IP addresses
•! Differences:
–! Address size
–! Representation
–! Distinguishes among different types of network
interfaces
–! Format Prefix

Network+ Guide to Networks, 4e 88

 Chapter 4
Network Protocols – Sockets
and Ports

Sockets and Ports

•! Every process on a machine assigned a port

number 0 to 65535
•! Process’s port number plus host machine’s IP
address equals process’s socket
–! Ensures data transmitted to correct application
•! Well Known Ports: in range 0 to 1023
–! Assigned to processes that only the OS or system
administrator can access

Network+ Guide to Networks, 4e 90

 Sockets and Ports (continued)

•! Registered Ports: in range 1024 to 49151

–! Accessible to network users and processes that do
not have special administrative privileges
•! Dynamic and/or Private Ports: in range 49152
through 65535
–! Open for use without restriction

Network+ Guide to Networks, 4e 91

Chapter 4
Network Protocols – DNS, Hosts,
TCP/IP Application Layer Protocols
Host Names and DNS (Domain Name
System): Domain Names
•! Every host can take a host name
•! Every host is member of a domain
–! Group of computers belonging to same organization
and has part of their IP addresses in common
–! Domain name usually associated with company or
other type of organization
•! Fully qualified host name: local host name plus
domain name
•! Domain names must be registered with an Internet
naming authority that works on behalf of ICANN

Network+ Guide to Networks, 4e 93

Host Files

•! ASCII text file called HOSTS.TXT

–! Associate host names with IP addresses
–! Growth of Internet made this arrangement impossible
to maintain

Figure 4-13: Example host file

Network+ Guide to Networks, 4e 94
 DNS (Domain Name System)
•! Hierarchical method of associating domain names
with IP addresses
–! Refers to Application layer service that accomplishes
association and organized system of computers and
databases making association possible
–! Relies on many computers around world
•! Thirteen root servers
•! Three components:
–! Resolvers
–! Name servers
–! Name space

Network+ Guide to Networks, 4e 95

DNS (continued)

Figure 4-14: Domain name resolution

Network+ Guide to Networks, 4e 96
 DNS (continued)

Figure 4-14 (continued): Domain name resolution

Network+ Guide to Networks, 4e 97

DDNS (Dynamic DNS)

•! DNS is reliable as long as host’s address is static

–! Many Internet users subscribe to type of Internet
service in which IP address changes periodically
•! In DDNS, service provider runs program on user’s
computer that notifies service provider when IP
address changes
–! DNS record update effective throughout Internet in
minutes

Network+ Guide to Networks, 4e 98

 Zeroconf (Zero Configuration)

•! Collection of protocols designed by IETF to simplify

setup of nodes on TCP/IP networks
–! Assigns IP address
–! Resolves node’s host name and IP address without
requiring DNS server
–! Discovers available services
–! Enables directly connected workstations to
communicate without relying on static IP addressing
–! IP addresses are assigned through IPv4LL (IP
version 4 Link Local)

Network+ Guide to Networks, 4e 99

Some TCP/IP
Application Layer Protocols
•! Telnet: terminal emulation protocol used to log on
to remote hosts using TCP/IP protocol suite
–! TCP connection established
–! Keystrokes on user’s machine act like keystrokes on
remotely connected machine
•! FTP (File Transfer Protocol): Application layer
protocol used to send and receive files via TCP/IP
–! Server and clients
–! FTP commands work from OS’s command prompt
–! Anonymous logons

Network+ Guide to Networks, 4e 100

 Some TCP/IP Application Layer
Protocols (continued)
•! Trivial File Transfer Protocol (TFTP): enables file
transfers between computers
–! Simpler than FTP
–! Relies on UDP at Transport layer
•! Connectionless
•! Network Time Protocol (NTP): Application layer
protocol used to synchronize clocks of computers
•! Network News Transfer Protocol (NNTP): facilitates
exchange of newsgroup messages between
multiple servers and users

Network+ Guide to Networks, 4e 101

Some TCP/IP Application Layer

Protocols (continued)
•! Packet Internet Groper (PING): utility that can verify
that TCP/IP is installed, bound to the NIC,
configured correctly, and communicating
•! Pinging:
–! Echo request and echo reply
–! Can ping either an IP address or a host name
–! Pinging loopback address, 127.0.0.1, to determine
whether workstation’s TCP/IP services are running
–! Many useful switches
•! e.g., -?, -a, -n, -r

Network+ Guide to Networks, 4e 102

 Chapter 4
Network Protocols – Legacy Protocols:
IPX/SPX, NetBIOS, NetBEUI, WINS,
AppleTalk

IPX/SPX (Internetwork Packet

Exchange/Sequenced
Packet Exchange)
•! Required to ensure interoperability of LANs running
NetWare versions 3.2 and lower
–! Replaced by TCP/IP on Netware 5.0 and higher

Network+ Guide to Networks, 4e 104

 The IPX and SPX Protocols

•! Internetwork Packet Exchange (IPX): provides

logical addressing and internetworking services
–! Operates at Network layer
–! Similar to IP
–! Connectionless
•! Sequenced Packet Exchange (SPX): Works with
IPX to ensure data received whole, in sequence,
and error free
–! Belongs to Transport layer
–! Connection-oriented

Network+ Guide to Networks, 4e 105

Addressing in IPX/SPX

•! Each node on network must be assigned unique

address
–! IPX address
•! Network address: chosen by network administrator
•! Node address: by default equal to network device’s
MAC address

Network+ Guide to Networks, 4e 106

 NetBIOS and NetBEUI
•! NetBIOS originally designed to provide Transport
and Session layer services for applications running
on small, homogenous networks
•! Microsoft added standard Transport layer
component called NetBEUI
–! Efficient on small networks
•! Consumes few network resources
•! Provides excellent error correction
–! Does not allow for good security
–! Few possible connections
–! Cannot be routed

Network+ Guide to Networks, 4e 107

Addressing in NetBEUI

•! Network administrators must assign NetBIOS name

to each workstation
•! After NetBIOS has found workstation’s NetBIOS
name, it discovers workstation’s MAC address
–! Uses this address in further communications

Network+ Guide to Networks, 4e 108

 WINS (Windows Internet
Naming Service)
•! Provides means to resolve NetBIOS names to
IP addresses
–! Used exclusively with systems using NetBIOS
•! Microsoft Windows
•! Automated service that runs on a server
•! Guarantees unique NetBIOS name used for each
computer on network
•! Clients do not have to broadcast NetBIOS names
to rest of network
–! Improves network performance

Network+ Guide to Networks, 4e 109

AppleTalk

•! Protocol suite originally designed to interconnect

Macintosh computers
–! Can be routed between network segments and
integrated with NetWare-, UNIX-, Linux-, or
Microsoft-based networks
•! AppleTalk network separated into logical groups of
computers called AppleTalk zones
–! Enable users to share file and printer resources
•! AppleTalk node ID: Unique 8- or 16-bit number that
identifies computer on an AppleTalk network

Network+ Guide to Networks, 4e 110

 Binding Protocols on a
Windows XP Workstation
•! Windows Internet Naming Service (WINS): process
of assigning one network component to work with
another
•! Core Network and Transport layer protocols
normally included with OS
–! When enabled, attempt to bind with network
interfaces on computer
•! For optimal network performance, bind only
protocols absolutely needed
•! Possible to bind multiple protocols to same network
adapter

Network+ Guide to Networks, 4e 111

Chapter 4
Network Protocols –
Summary
 Summary
•! Protocols define the standards for communication
between nodes on a network
•! TCP/IP is most popular protocol suite, because of
its low cost, open nature, ability to communicate
between dissimilar platforms, and routability
•! TCP provides reliability through checksum, flow
control, and sequencing information
•! IP provides information about how and where data
should be delivered
•! Every IP address contains two types of information:
network and host

Network+ Guide to Networks, 4e 113

Summary (continued)

•! Subnetting is implemented to control network traffic

and conserve a limited number of IP addresses
•! Dynamic IP address assignment can be achieved
using BOOTP or the more sophisticated DHCP
•! A socket is a logical address assigned to a specific
process running on a host
•! IPv6 provides several other benefits over IPv4
•! A domain is a group of hosts that share a domain
name and have part of their IP addresses in
common

Network+ Guide to Networks, 4e 114

 Summary (continued)
•! DNS is a hierarchical way of tracking domain
names and their addresses
•! IPX/SPX is a suite of protocols that reside at
different layers of the OSI Model
•! NetBEUI is a protocol that consumes few network
resources, provides error correction, and requires
little configuration
•! WINS is a service used on Windows systems to
map IP addresses to NetBIOS names
•! AppleTalk is the protocol suite originally used to
interconnect Macintosh computers

Network+ Guide to Networks, 4e 115