Network ports explained TCP UDP common port numbers IT support tutorial

Network Ports Explained: TCP, UDP and Common Port Numbers for IT Support

Learn what network ports are, the difference between TCP and UDP, and common port numbers every IT support professional should know.

Network Ports Explained Tcp Udp is a core networking skill for IT support, help desk, junior system administrators, and anyone preparing for a networking career. This tutorial explains the topic in clear language with practical examples.

In this guide:
  • Simple explanation for beginners
  • Real IT support examples
  • Useful commands to practice
  • Troubleshooting checklist
  • Safety and documentation tips

What are network ports?

A network port identifies a specific service or application on a device. IP addresses help find the device, while ports help find the service running on that device.

TCP vs UDP

TCP is connection-oriented and reliable, often used for web, email, and file transfer. UDP is faster and connectionless, often used for DNS, voice, video, and gaming.

Common port numbers

HTTP uses port 80, HTTPS uses 443, DNS commonly uses 53, SSH uses 22, RDP uses 3389, SMTP uses 25 or 587, and SMB commonly uses 445.

Why ports matter in troubleshooting

If a website, remote desktop, VPN, or email service fails, the issue may be a blocked port, closed service, firewall rule, or wrong destination address.

Security note

Open ports increase exposure. Only allow required ports, restrict access by source IP where possible, and avoid exposing management services directly to the internet.

Useful commands to practice

netstat -ano
ss -tulpen
Test-NetConnection example.com -Port 443
nc -vz example.com 443
nmap -Pn example.com

Quick IT support checklist

  • Identify whether the issue affects one device, one network, or all users.
  • Check IP address, gateway, DNS, and physical/wireless connection.
  • Test local connectivity before testing internet connectivity.
  • Collect screenshots or command outputs before changing settings.
  • Make one change at a time and verify the result.

Final thoughts

Networking becomes much easier when you understand the basics and follow a structured troubleshooting process. Practice these examples in a safe lab before using them in production environments.

Educational note: This tutorial is for learning purposes. Test carefully, follow your organisation’s change process, and avoid making production changes without approval.

Leave a Reply

Your email address will not be published. Required fields are marked *