Study guide
Transport-Layer Services
CCST Networking Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation, Official Sources, and Exam Strategy
Official Exam Profile and Source Hierarchy Registration, Delivery, Attempts, and Results Using the Six Official Topic Areas Building a Practical Study Plan Exam Strategy Without Unsupported Shortcuts Ethical Preparation and Path Forward
2 Network Standards, Models, and Common Protocols
Network Building Blocks OSI and TCP/IP Models Frames, Packets, Segments, and Data Flow Network Types and Scope Cloud, On-Premises, Protocols, and Ports Bandwidth, Throughput, Latency, and Jitter
3 Chapter 3: IPv4, IPv6 Addressing, and Subnet Formats
3.1 Public, Private, and Local Addressing 3.2 IPv4 Dotted Decimal and Binary Basics 3.3 Subnet Masks, CIDR, and Prefix Lengths 3.4 Subnet Logic, Host Ranges, and Gateways 3.5 IPv6 Address and Prefix Formats 3.6 MAC vs IP in Addressing Troubleshooting
4 Endpoints, Media, Cabling, and Client Connectivity
Endpoint Devices and Network Roles Network Interface Cards and Link Status Copper, Fiber, Coax, and Connector Basics Wired, Wi-Fi, and Cellular Access Methods Interference, Signal Quality, and Physical Reliability Client Connectivity Checks by Operating System
5 Infrastructure Devices, Ports, and Physical Installation
Infrastructure Device Roles Ports, Connectors, and Device Identification Cisco Device LEDs and Status Checks Network Diagrams and Cabling Instructions Power over Ethernet and Powered Devices Racks, Patch Panels, and Installation Basics
6 Switching, Routing, and Network Services
Basic Switching and MAC Learning VLANs and Local Boundaries Routing, Default Gateway, and ARP DNS, DHCP, and NAT Services Transport-Layer Services Small Network Traffic Flow
7 Troubleshooting Methodology, Ticketing, and Documentation
Help Desk Intake and Information Gathering Scope, Impact, and Prioritization Reproduce, Isolate, and Escalate Ticket Quality and Operational Documentation User Communication and Change History Physical, Data Link, and Network Layer Triage
8 Diagnostic Commands, Packet Capture, and Device Data
Command-Line Triage and Ping Path and Client Configuration Commands DNS and Socket Diagnostics Wireshark Capture and Save Device Access and Data Collection Basic Cisco Show Commands
9 Security, Firewalls, Wireless, and Safe Defaults
Firewall Filtering and Traffic Policy Least Privilege, AAA, Passwords, and MFA Wireless Security, WPA2, WPA3, and WPAx Guest Networks, Segmentation, and Shared Devices Common Threats and Safe User Practices Secure Home Router Baseline
10 Integrated Small Network Build and Repair Labs
Lab 1: Build a Basic Office LAN Lab 2: Repair No Internet After an Office Move Lab 3: Wireless Clients Cannot Reach Local Resources Lab 4: DHCP, DNS, and Default Gateway Symptoms Lab 5: Switch, Router, and Service Boundaries Lab 6: Escalation, Documentation, and Handoff
11 CCST to CCNA Career Path and Operational Readiness
Entry-Level Networking Roles and Expectations CCST vs CCNA and the Cisco Roadmap NetAcad 70-Hour Path and Study Plan Lab Habits for Real Operational Readiness Ethical Preparation, Portfolio, and Logbook Exam Scheduling Calendar and Readiness Check
12 Final Review, Exam Day, and Remediation Plan
Final Review Map to Official Objectives 50-Minute Exam Day Timing Unsupported Facts and Ethical Preparation Retake Planning Before the First Attempt Post-Fail Remediation Workflow Post-Pass Next Steps and Validity
Transport-Layer Services
Key Takeaways Explain This Topic AI
The transport layer (Layer 4) uses TCP and UDP to deliver data to the correct application on a host.
TCP is connection-oriented: it uses a three-way handshake (SYN, SYN-ACK, ACK), sequencing, acknowledgments, retransmission, and flow control.
UDP is connectionless with no handshake or built-in retransmission, giving lower overhead for DNS, DHCP, voice, and streaming.
A socket is uniquely identified by source IP, source port, destination IP, destination port, and protocol (the 5-tuple).
Know the key well-known ports: HTTP 80, HTTPS 443, DNS 53, SSH 22, and that ping uses ICMP, not a port.
Last updated: June 2026
TCP and UDP
IP gets a packet from host to host, but a host runs many applications at once, so it needs a way to deliver data to the right one. That is the transport layer (Layer 4) , and the two protocols a technician sees most are TCP and UDP . Both use port numbers ; their delivery behavior differs sharply.
TCP — Transmission Control Protocol
TCP is connection-oriented and reliable . Before any application data flows, the two sides complete the three-way handshake :
- Client -> Server: SYN (synchronize, propose a sequence number)
- Server -> Client: SYN-ACK (acknowledge and propose its own)
- Client -> Server: ACK (acknowledge; session open)
After that, TCP numbers every byte, acknowledges what it receives, retransmits anything lost, reorders out-of-sequence data, and uses flow control (a sliding window) so a fast sender does not overwhelm a slow receiver. This costs overhead but guarantees a complete, ordered byte stream — ideal for web pages, file transfer, email submission, and remote administration.
UDP — User Datagram Protocol
UDP is connectionless . It fires datagrams with no handshake, no acknowledgments, and no retransmission. That is not 'unreliable' as a flaw — it simply pushes reliability up to the application when needed. The payoff is low overhead and low latency, which suits DNS queries, DHCP , voice and video, and real-time streaming, where a late retransmission would be worse than a small loss.
- Feature TCP UDP
- Connection setup Three-way handshake None
- Reliability Acks + retransmission None (app handles it)
- Ordering Guaranteed Not guaranteed
- Overhead Higher Lower
- Typical use Web, file transfer, email, SSH DNS, DHCP, VoIP, streaming
Ports, Sockets, and Troubleshooting
A port number identifies the application endpoint on a host. A server listens on a fixed well-known port ; the client opens a temporary, OS-chosen ephemeral port (commonly 49152-65535) for its side. A full conversation — a socket — is identified by the 5-tuple : source IP, source port, destination IP, destination port, and protocol. Firewalls, NAT/PAT tables, and packet captures all key on this 5-tuple to keep flows separate.
Well-known ports to memorize
- Service Protocol Port
- HTTP TCP 80
- HTTPS TCP 443
- DNS UDP (TCP for large/zone) 53
- SSH TCP 22
- Telnet TCP 23
- DHCP UDP 67 (server) / 68 (client)
- SMTP TCP 25
- FTP TCP 20 / 21
- ping (ICMP) ICMP — no port n/a
At CCST depth, learn the concepts more than a giant list, but know that ping uses ICMP, not TCP or UDP , so a firewall can block ping while allowing web traffic — or vice versa.
When one application fails
A ticket that says "the Internet works but app X is broken" usually is not a general network outage. Likely causes: a blocked destination port, wrong server address, expired TLS certificate, a proxy, a name-resolution issue, or a server outage. Narrow it with precise questions:
Does the client have an IP, and can it ping the gateway?
Can it resolve the server's name?
Does only one application or one port fail?
Is the failure on TCP, UDP, or both?
A packet capture that shows repeated TCP SYN packets with no SYN-ACK reply points to a blocked port or a server that is not listening — not a cabling fault.
Common traps
Thinking ports replace IP addresses; IP reaches the host, the port reaches the process.
Assuming DNS is TCP — it is primarily UDP 53.
Forgetting ICMP has no port number.
Believing UDP guarantees order or delivery — it guarantees neither.
- Handshake, Teardown, and Reading a Capture
- How a TCP session opens and closes
The three-way handshake (SYN, SYN-ACK, ACK) opens a session; a graceful close uses FIN and ACK exchanges, while an abrupt abort uses a RST (reset) . Reading these flags tells you a lot in a capture:
Repeated SYN with no SYN-ACK -> nothing is listening on that port, or a firewall silently dropped the request.
Immediate RST after a SYN -> a device actively refused the connection (port closed or policy deny).
Handshake completes but data stalls -> likely an application, certificate, or path-MTU issue, not a connect problem.
This is why 'can the client even open a TCP connection to the server's port?' is such a powerful diagnostic question — it separates network-path faults from application faults.
Port ranges you should recognize
- Range Name Used by
- 0-1023 Well-known Servers (HTTP 80, HTTPS 443, SSH 22, DNS 53)
- 1024-49151 Registered Many vendor applications
- 49152-65535 Dynamic / ephemeral Client source ports
A server's port is fixed and predictable; the client's source port is random and temporary. That asymmetry is exactly what PAT exploits to share one public address.
A precise troubleshooting narrative
Suppose a user can browse most sites but one internal web app times out. The link, DHCP, gateway, and DNS all check out, and ping to the app server succeeds. A capture shows the client sending SYN to TCP 443 with no reply. ICMP (ping) works but TCP 443 does not, which points to a port-level block — a firewall rule, a service that is down, or the wrong port — rather than a connectivity failure. Reporting it as 'TCP 443 to server X returns no SYN-ACK while ICMP succeeds' gives an engineer an immediately actionable lead.
Why this matters for CCST
The 100-150 exam expects you to explain TCP versus UDP behavior, identify common ports and protocols, and interpret simple diagnostic output. You will not write firewall rules, but you must be able to say which layer a symptom lives at: physical, IP, transport, or application. The transport layer is the hinge between 'the network is reachable' and 'this specific application works.'