WARNING: This site is intended for online use only; mass-downloading of pages degrades the server and is prohibited.
If you attempt to use tools to mass-download the site, you may be blocked permanently by automated software.
If you want to read this CertiGuide offline, please use one of the links on the left to purchase a convenient PDF copy. Thank you.

Like this CertiGuide? Get it in PDF format!
Click Here!

Custom Search






Table Of Contents  CertiGuide to A+ (A+ 4 Real)
 9  Chapter 14: Networks
      9  What is a Network?
           9  Protocol Standards

Previous Topic/Section
Name Resolution Using the Hosts File
Previous Page
Pages in Current Topic/Section
1
Next Page
Clients
Next Topic/Section

TCP Ports

We have covered IP addresses, but what about the TCP part? TCP stands for Transmission Control Protocol, and is the method by which application data is broken down, transmitted, and reassembled across a network.

Remote systems need to connect to each other regardless of underlying hardware or operating system. This is the whole reason for the TCP/IP suite. We have seen how TCP/IP allows machines to find each other by the use of addresses, but since each machine is generally set up to accomplish more than just one task, it’s not enough to send packets to a specific machine and rely on it to figure out what to do with them. A “hint” as to the purpose of the packet has to be provided in the packet, to let the target system know what the user wants to do.

The way this hint is provided is that specific port numbers, ranged between 1 and 65535, are assigned to specific tasks such as sending e-mail, and the packet specifies the port number (function) desired as well as the destination IP address of the remote system. When a packet is sent, IP delivers the data from the client to the correct server (as determined by the destination IP address) and the port number is used to make the connection to the particular service in need.

This delivery of data is accomplished by means of applications on each side of the network connection – one on the client side, and one on the server side. These programs themselves are generally referred to as clients (for the client-machine side) and servers (as you might expect, for the server-machine side). Typically, each particular service has its own client and server program components.

When the software for a service is installed on a server, it is configured to communicate on a specific port number. For most common network utilities, these port numbers are standardized across TCP/IP implementations and operating systems and will be the same on all systems (unless the administrator changes them, which is usually not recommended unless done for security reasons). For example, when you receive your email, you are calling the service POP3 (Post Office Protocol Version 3) via port number 110. When you retrieve your email, your client computer running e-mail client software creates a session and a socket connection to the server’s port 110.

A socket is a software object (not a hardware socket) that is specific to your computer system, which knows how to communicate with a corresponding socket on a server computer that is also running TCP/IP.

Communications can occur regardless of the specific computer or operating systems in use, as long as both the client and server computers follow the same standard for location of ports (such as 110 for email).

Table 35 highlights some of the most important “well known services” (protocols) and the ports at which to find them. There are many more TCP/IP application protocols available, to serve different specialized purposes.


Table 35: Well-Known TCP/IP Protocols and Port Assignments

Acronym

Protocol Name

Port #

FTP

File Transfer Protocol

21

TFTP

Trivial File Transfer Protocol

69

HTTP

Hypertext Transfer Protocol for the World Wide Web (WWW)

80

POP3

Post Office Protocol Version 3

110

IMAP4

Internet Message Access Protocol Version 4

143

SMTP

Simple Mail Transfer Protocol

25

NNTP

Network News Transfer Protocol

119

NTP

Network Time Protocol

123

Telnet

Telnet

23

DNS

Domain Naming System

53


Previous Topic/Section
Name Resolution Using the Hosts File
Previous Page
Pages in Current Topic/Section
1
Next Page
Clients
Next Topic/Section

If you find CertiGuide.com useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider buying an inexpensive PDF equivalent of the CertiGuide to A+ (A+ 4 Real) from StudyExam4Less.com. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

CertiGuide to A+ (A+ 4 Real) (http://www.CertiGuide.com/apfr/) on CertiGuide.com
Version 1.0 - Version Date: March 29, 2005

Adapted with permission from a work created by Tcat Houser et al.
CertiGuide.com Version Copyright 2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.