Like this CertiGuide? Get it in PDF format!
Click Here!
Use coupon code "certiguide" to save 20%!
(Expires 2004/12/31)

NEW! Network+ N11-003 2005 Beta Exam Study Guide - Just $9!
Get It Here!

Custom Search







Table Of Contents  CertiGuide to Network+
 9  Chapter 0101:  TCP/IP

Previous Topic/Section
IP Default Gateway
Previous Page
Pages in Current Topic/Section
1
2
Next Page
VIII  Services and Applications
Next Topic/Section

VII  Ports
(Page 1 of 2)

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’ve seen how TCP/IP allows machines to find each other by the use of addresses. 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 are assigned to specific tasks, like sending e-mail, and the packet specifies the port number (function) desired as well as the destination 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 application programs 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 installed to communicate on a specific port number. For most common network utilities, these port numbers are standardized across TCP/IP, and will be the same on all systems (unless the admin changes them, which is not recommended unless you’re an advanced administrator). For example, when you receive your email, you are calling the service POP3 (Post Office Protocol Version 3) via Port number 110. When you get your email, your client computer running e-mail client software creates a session, and a socket connection attached 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).


Previous Topic/Section
IP Default Gateway
Previous Page
Pages in Current Topic/Section
1
2
Next Page
VIII  Services and Applications
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 Network+ from StudyExam4Less.com. (Use coupon code "certiguide" by December 31, 2004 to save 20%!) Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

CertiGuide for Network+ (http://www.CertiGuide.com/netplus/) on CertiGuide.com
Version 1.0 - Version Date: November 7, 2004

Adapted with permission from a work created by Tcat Houser and Helen O’Boyle.
CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.