Introduction: Why Port Numbers Matter for CompTIA A+ and Network Troubleshooting
TCP and UDP port numbers are fundamental for network communication, troubleshooting, and firewall configuration. Firewalls use these ports to allow or block traffic. For the CompTIA A+ exam, you must memorize port numbers, associated protocols, and understand their real-world usage. Understanding how these protocols use ports within the IP, TCP, and UDP Explained: Networking Fundamentals for A+ Certification framework is essential for troubleshooting network connectivity.
Core Protocol Ports for File Transfer and Remote Access
FTP (File Transfer Protocol) - Ports 20 & 21
- Port 21 (TCP): Control/administration port for FTP commands
- Port 20 (TCP): Active data transfer port
- Usage: Transfers files between different operating systems, supports authentication (username/password) or anonymous login
SSH (Secure Shell) - Port 22 (TCP)
- Primary Function: Encrypted remote command-line administration
- Security: Provides encrypted communication link, replaced insecure Telnet
Telnet - Port 23 (TCP)
- Primary Function: Remote command-line access (unencrypted)
- Security Risk: Sends all data in clear text; organizations should disable and use SSH instead
Email and Communication Protocol Ports
SMTP (Simple Mail Transfer Protocol) - Port 25 (TCP)
- Primary Function: Sends email between mail servers and from client devices to servers
POP3 (Post Office Protocol v3) - Port 110 (TCP)
- Primary Function: Receives and downloads email to local client
IMAP4 (Internet Message Access Protocol v4) - Port 143 (TCP)
- Primary Function: Receives email with advanced features (folder management, multi-device synchronization)
Network Infrastructure Service Ports
DNS (Domain Name System) - Port 53 (UDP)
- Primary Function: Translates fully qualified domain names (e.g., www.professormesser.com) to IP addresses
- Redundancy: Multiple DNS servers ensure reliable name resolution
DHCP (Dynamic Host Configuration Protocol) - Ports 67 & 68 (UDP)
- Port 67: DHCP server
- Port 68: DHCP client
- Function: Automatically assigns IP addresses, subnet masks, default gateways, and DNS servers
- Features: IP address leasing and reservation for specific devices
Web and Windows Communication Ports
HTTP (Hypertext Transfer Protocol) - Port 80 (TCP)
- Standard web traffic: Sends unencrypted data
HTTPS (HTTP Secure) - Port 443 (TCP)
- Encrypted web traffic: Provides secure communication for web browsing (now dominant)
SMB/CIFS (Server Message Block / Common Internet File System) - Port 445 (TCP)
- Primary Function: File sharing, printer queue communication, and data transfer between Windows devices
- Note: Modern Windows uses direct SMB over port 445; older NetBIOS used ports 137 (UDP) and 139 (TCP)
Directory Services and Remote Desktop Ports
LDAP/LDAPS (Lightweight Directory Access Protocol) - Port 389 (TCP)
- Primary Function: Accesses directory services databases (e.g., Microsoft Active Directory)
- Structure: Organizes resources by organization, organizational unit, and common name
- Usage: Authentication and resource location in network directories
RDP (Remote Desktop Protocol) - Port 3389 (TCP)
- Primary Function: Remote desktop control and application sharing
- Platform Support: Primarily Windows, but clients exist for macOS, Linux, Unix, iOS
- Features: Full desktop control or single application access
For a comprehensive understanding of how these ports fit into network communication, refer to Understanding Networking Protocols: IP, TCP, and UDP Explained.
Study Tips for CompTIA A+ Port Numbers
- Memorize not just the port number but the protocol (TCP vs. UDP)
- Understand why each protocol is important and how it's used on real networks
- Focus on practical applications: firewall rules, troubleshooting, and secure vs. insecure alternatives
- For deeper foundational knowledge of how ports and protocols interact in network devices, review the Complete CCNA 200-301 Course: Network Devices & Fundamentals Explained.
- Regular use will make these port numbers second nature over time
Protocol Summary Table:
| Protocol | Port(s) | Type | Purpose | |----------|---------|------|---------| | FTP | 20, 21 | TCP | File Transfer | | SSH | 22 | TCP | Secure Remote Admin | | Telnet | 23 | TCP | Unencrypted Remote Admin | | SMTP | 25 | TCP | Email Sending | | DNS | 53 | UDP | Name Resolution | | DHCP | 67, 68 | UDP | IP Configuration | | HTTP | 80 | TCP | Web (Unencrypted) | | POP3 | 110 | TCP | Email Receiving (Download) | | IMAP4 | 143 | TCP | Email Receiving (Sync) | | LDAP | 389 | TCP | Directory Services | | HTTPS | 443 | TCP | Web (Encrypted) | | SMB | 445 | TCP | Windows File Sharing | | RDP | 3389 | TCP | Remote Desktop |
as we've discussed in a previous video the port numbers used by TCP and UDP can be very important when trying to
communicate to a service so it's useful to know what those port numbers are if you're trying to troubleshoot any type
of communications issue we might also need to know these port numbers if we're performing some type of firewall
configuration our firewalls often use TCP and UDP port numbers as one of the criteria that it uses to allow or to
block Lo Network traffic as you go through this video you'll find there are a number of port numbers that you're
required to know as part of your A+ studies you'll find that memorizing these port numbers can sometimes feel a
bit tedious but after you start using these applications configuring firewalls and troubleshooting network
communication you'll find that most of these port numbers become second nature for the purposes of your A+ studies make
sure that you understand not only the port number and the protocol associated with it but that you understand why that
particular protocol is important and how it's used on the network the first port numbers we'll
look at are port numbers TCP Port 20 and TCP Port 21 these two port numbers are commonly associated with FTP or the file
transfer protocol FTP is a generic file transfer protocol that could be used by many different operating systems to
transfer information from one device to another and different types of FTP may use one or both of these prot protocols
TCP Port 20 is often used as the active data transfer and Port 21 is often used as the administration or control Port
the FTP protocol often requires you to have some type of authentication into this system so it may ask for a username
a password or some other type of authentication Factor FTP can also be configured with an anonymous or generic
login so that anyone can log in regardless of what the username or password might be FTP is also a
full-featured protocol that not only can transfer a file but can list the files available in a particular directory we
can add delete change the file name and perform other Administration functions as
well as part of our tasks as server administrators or network administrators we are often required to connect to our
Remote device and make configuration changes at the command line to be able to do this securely across the network
we need to use a protocol that can encrypt all of this data as we're sending it from one side to the other
the most common protocol used for this function is SSH or secure shell it provides an encrypted communication link
over TCP Port 22 this is very similar to the old style tnet protocol but tnet is one that we commonly no longer see in
use because it does not provide any type of encryption if you're communicating at the command line to a server you should
always be using SSH and you'll find that it almost always is using TCP Port 22 however you may find that there is a
system in your network that is very old that does not support SSH and the only way to administer that device at the
command line is using the older tnet protocol telnet stands for telecommunications Network and it
commonly communicates over TCP Port 23 visually and functionally this works identical to SSH you have a command line
you can log into a device with your username and password you can administer that device remotely but the major
difference is that all of the communication used for tnet is in the clear there's no encryption used for
tnet and that's why most organizations will prevent anyone from using the tnet protocol and instead recommend that you
use SSH to perform this communication email continues to be one of the most popular forms of
communication across our networks and to be able to facilitate that communication we need some type of protocol that can
send mail from one server to another that protocol is the simple mail transfer protocol or SMTP SMTP commonly
uses TCP Port 25 to be able to send these email messages from one email server to another you may also find that
some devices are configured to send information to the email server initially also using this SMTP protocol
so not only are you configuring this on your mail server you may also o find that you're configuring SMTP with the
appropriate port number on your local device to be able to receive email messages we would commonly use protocols
such as IMAP or pop 3 and we'll talk about those protocols and their Associated port numbers later in this
video in these videos so far we've talked a lot about devices able to communicate with each other using IP or
Internet Protocol the Internet Protocol address is one very similar to what you would see here one 62.1 159 2461 164 but
when we're typing things into our browser we're not typing in a bunch of numbers we're typing in the name of a
website such as www.professormesser.com in order to translate this fully
qualified domain name into a usable IP address for network communication we need to perform a translation using the
domain name system or DNS DNS commonly uses UDP Port 53 as you can imagine DNS is a very popular
and important service because we almost never memorize IP addresses to be able to communicate to these devices but it's
very common to remember the fully qualified domain name for that reason it's very common to have multiple DNS
servers for redundancy so that we are always able to resolve the fully qualified domain name to the appropriate
IP address the computer on your network was probably not manually configured with a
set of IP addresses subnet masks default gateways or DNS servers this was done automatically when you turn your
computer on using the dynamic host configuration protocol or DHCP DHCP happens automatically behind
the scenes and it makes the entire process of configuring your system with these addresses completely seamless DHCP
commonly uses UDP Port 67 and UDP Port 68 on your network is a DHCP service that may be on a standalone server or
Appliance or may be integrated into a small office home office wireless router that you might have at home on this
server is a pool of available IP addresses and when a device connects to the network it requests an IP address
and configuration parameters from that pool when a device starts up it receives that IP address and it leases that IP
address for a certain amount of time when that lease is up it can choose to renew the lease or give the IP address
back and put it into the pool for someone else to use system administrators can also use DHCP to
manually configure IP addresses that will always be assigned to particular devices so if you have a printer or
server that you would like to always have the same IP address you can reserve that IP address in your DHCP server and
it will be automatically assigned with the same IP address every time that printer or server starts
up you're probably watching this video in a browser and to be able to perform that functionality you're probably using
HTT TP or https this is the hypertext transfer protocol or hypertext transfer protocol secure the standard form of
HTTP sends all of the HTTP data over a non-encrypted or in the clear communication and it often uses TCP Port
80 if you see any traffic using TCP Port 443 it's probably using the secure version of HTTP which means that all of
that web communication inside of that packet will be encrypted a large percentage of the devices you
communicate to in your browser are probably going to use https these days but you'll still find a number of web
services that are not using the encrypted version and instead are sending all of their traffic via TCP
Port 80 and the HTTP protocol if you're using an email client on your computer or your mobile device
you may be receiving emails using a number of different protocols two of the more popular Protocols are POP 3 and
IMAP POP 3 is the post office protocol version three and it commonly uses TCP Port 110 to be able to transfer data
down to your computer a newer and somewhat more functional protocol for receiving email is IMAP 4 or the
internet message access protocol version 4 IMAP commonly uses TCP Port 143 IMAP provides a number of additional features
not available in pop 3 such as the management of the inbox from multiple clients you're able to make make folders
and transfer emails into those folders and all of those updates will be synchronized across all of your
different systems and all of those updates will be synchronized across all of your different email
clients if you're using Microsoft Windows there's a process for transferring data within windows that
uses a protocol named server message block or SMB you may also see this referred to as the common internet file
system or cifs not only is this used for file trans transfers it's used to send information to printer cues and for
other processes where Windows needs to communicate information between different Windows devices older Windows
devices used an additional protocol inside of tcpip called netbios this net bios protocol used two primary port
numbers to be able to communicate UDP Port 137 used a net bios name service which is very similar to the DNS name
service that we talked about earlier and to be able to set up sessions to transfer files it uses TCP Port 139 on
most modern versions of Windows you'll find Direct connectivity between IP addresses that don't use the net bios
protocol we refer to that as direct communication or net bios less communication and it often uses TCP Port
445 most organizations will have a central database that contains all of the important information about the
devices users and and important resources available on their Network this is usually a directory of services
or a database that contains all of this information and to be able to access this database we use a standard set of
protocols one of these protocols is ldap or ldaps this stands for the lightweight directory access protocol or the
lightweight directory access protocol secure ldap commonly uses TCP port 389 this directory is usually separated into
different categories such as an organization an organizational unit or a common name for example at mess Studios
we might have a production organizational unit a support organizational unit and an engineering
organizational unit and of course within those there may be individuals using a common name such as Sam or Daniel and we
might also have a database called Tech docs using ldap we can refer to this database to find where these components
might be and in some cases even provide a additional details such as authentication for any individual users
a very common use of ldap is Microsoft's active directory infrastructure where that database is able to be referenced
using the ldap protocol if you are troubleshooting technology then you're probably very
familiar with remote control access of a separate machine these days we have users around the world and it's not very
practical for you to visit every single one of those users directly to be able to solve problems s on their computer in
those cases we'll probably use some type of remote access protocol such as RDP or remote desktop protocol this allows you
to view and share the desktop on a Remote device using TCP Port 3389 this is primarily used to access
Windows devices and to be able to control those windows devices across the network you can usually do this from a
Windows device itself or from many other operating systems as well you can use RDP to control an entire computer or to
Simply run a single application on that remote computer and although RDP is commonly associated with connecting to
Windows devices there are also many RDP clients that would allow you to connect to that Windows computer from Mac OS
Linux Unix iPhone and other operating systems as well
Memorizing both port numbers and their associated transport protocols (TCP vs. UDP) is crucial because firewall rules and troubleshooting scenarios often require knowing not just the port but the protocol type. For example, DNS uses UDP port 53 for quick queries, while HTTP uses TCP port 80 for reliable web delivery. The exam tests practical application, such as configuring firewalls or diagnosing connectivity issues, which demands understanding how each protocol’s transmission characteristics (connection-oriented TCP vs. connectionless UDP) affect network behavior.
FTP uses port 21 (TCP) for control commands—such as login, directory navigation, and file operation requests—while port 20 (TCP) handles the actual data transfer in active mode. The control connection remains open throughout the session to manage commands, while the data connection opens on-demand for file transfers. Understanding this separation helps in troubleshooting firewall rules, as both ports must be permitted for FTP to function.
Telnet transmits all data, including login credentials and commands, in unencrypted plaintext, making it vulnerable to interception via packet sniffing. SSH encrypts the entire session, ensuring confidentiality and integrity of remote administration. For security compliance and risk mitigation, organizations should disable Telnet and use SSH, which is the secure industry standard for remote command-line access.
POP3 downloads emails from the server to a single local client, often deleting them from the server afterward, which limits access to one device. IMAP4 synchronizes emails across multiple devices by storing them on the server, allowing folder management, server-side search, and read/unread status tracking. IMAP4 is ideal for users who access email from smartphones, laptops, and desktops, while POP3 suits offline or single-device environments.
Port 67 (UDP) is used by the DHCP server to receive client requests and send configuration offers, while port 68 (UDP) is used by the DHCP client to broadcast discovery messages and accept offers. During leasing, a client broadcasts a DHCPDISCOVER; the server responds with a DHCPOFFER; the client requests the offer with DHCPREQUEST; and the server acknowledges with DHCPACK, providing an IP address, subnet mask, gateway, and DNS servers for a defined lease period.
Modern SMB (Server Message Block) uses direct TCP port 445 for file and printer sharing, eliminating the need for NetBIOS over TCP/IP (ports 137 UDP and 139 TCP). This simplifies firewall rules and reduces attack surface by removing legacy NetBIOS dependencies. While older systems used NetBIOS for name resolution and session services, Windows has transitioned to SMB direct for better performance and security.
LDAP (Lightweight Directory Access Protocol) on port 389 enables access to directory services like Microsoft Active Directory, allowing authentication, user lookups, and resource location by querying objects in a hierarchical structure (organizational units, common names). RDP (Remote Desktop Protocol) on port 3389 provides remote desktop control and application sharing, primarily on Windows systems, but also supports macOS, Linux, and mobile clients for full desktop or single application sessions.
Keep this summary
Save it to LunaNotes and it becomes a real note in your library — editable, searchable, and ready to turn into flashcards or a diagram. Free to start.
Save to LunaNotesOr summarise for another video.
This summary and transcript were automatically generated using AI with the Free YouTube Transcript Summary Tool by LunaNotes.
Related summaries
Understanding Well-Known Port Numbers for Networking Services
Explore the significance of well-known port numbers in networking, including FTP, SSH, SMTP, and more.
IP, TCP, and UDP Explained: Networking Fundamentals for A+ Certification
This video from a CompTIA A+ prep course demystifies core networking protocols: IP, TCP, and UDP. Learn how these protocols work together to transport data across networks using the truck-box-road analogy, and understand the differences between connection-oriented reliable delivery and connectionless, low-overhead communication.
Understanding Networking Protocols: IP, TCP, and UDP Explained
Explore how IP, TCP, and UDP work together to efficiently transport data across networks.
Complete CCNA 200-301 Course: Network Devices & Fundamentals Explained
This introductory CCNA course video covers essential network devices including routers, switches, firewalls, servers, and clients. Learn their roles in building networks, client-server relationships, and how to prepare for the CCNA 200-301 exam with practical labs, quizzes, and flashcards.
Data Center Services: DNS, DHCP, File Sharing, and Network Infrastructure
Explore the essential services running in modern data centers, from DNS and DHCP to email servers and load balancers. This guide covers the key technologies that power enterprise networks and ensure uptime, security, and efficient resource sharing.
Most viewed summaries
A Comprehensive Guide to Using Stable Diffusion Forge UI
Explore the Stable Diffusion Forge UI, customizable settings, models, and more to enhance your image generation experience.
Kolonyalismo at Imperyalismo: Ang Kasaysayan ng Pagsakop sa Pilipinas
Tuklasin ang kasaysayan ng kolonyalismo at imperyalismo sa Pilipinas sa pamamagitan ni Ferdinand Magellan.
Mastering Inpainting with Stable Diffusion: Fix Mistakes and Enhance Your Images
Learn to fix mistakes and enhance images with Stable Diffusion's inpainting features effectively.
Pamamaraan at Patakarang Kolonyal ng mga Espanyol sa Pilipinas
Tuklasin ang mga pamamaraan at patakaran ng mga Espanyol sa Pilipinas, at ang epekto nito sa mga Pilipino.
How to Install and Configure Forge: A New Stable Diffusion Web UI
Learn to install and configure the new Forge web UI for Stable Diffusion, with tips on models and settings.
Found this summary useful?
Take it with you. One click puts it in your own LunaNotes library.
Save to LunaNotes