Ports and Protocols for A+

This A+ topic package covers technician-level recognition and practical matching of common network protocols and their default ports, the behavioral differences between TCP and UDP for support scenarios, the concept of well-known/registered/ephemeral port ranges, and awareness of secure protocol variants versus legacy insecure ones.

Start first lesson

5 lessons in this topic

TCP vs UDP Behavior

Differentiate connection-oriented and connectionless transport behavior and choose the better fit for common support scenarios.

Common TCP Ports

Match common TCP-based services to their default ports and recognize them in support scenarios.

Common UDP Ports

Match common UDP-based services to their default ports and identify the likely service from a symptom or scenario.

Secure Protocol Variants

Recognize insecure legacy protocols and choose the appropriate secure alternative in technician-level situations.

Port Ranges & Matching

Interpret well-known, registered, and dynamic port ranges and distinguish destination service ports from temporary client ports.

Common mistakes to avoid

- Misapplying a blanket rule that TCP is "slow" and UDP is "fast". The correct factor is the application's need for reliability vs overhead. - Expecting retransmission or ordering from UDP-based services; many UDP services are designed to tolerate loss.

- Mixing up SMTP (sending) with POP3/IMAP (retrieval). - Treating Telnet and SSH as interchangeable; Telnet is insecure. - Expecting older port assignments (NetBIOS 137-139) instead of modern direct SMB on 445.

- Thinking UDP services cannot use TCP in any circumstance (some services fall back to TCP for large transfers). - Expecting guaranteed delivery from UDP-based logging or traps.

- Equating the ability to connect with suitability; an insecure protocol may connect but still be unacceptable for credentialed access.