Reading the clues: handshakes, resets and retransmissions
▶ Start the interactive lesson
Three tickets, three captures: • "Connection refused." • "It just times out." • "It's really slow." Sam: "Each of those leaves a different fingerprint in the capture. Learn the fingerprints and you'll know which team to call in minutes."
The TCP handshake
Every TCP connection starts with three packets: client SYN → server SYN, ACK → client ACK.
RST vs silence
SYN → RST (reset), usually within a millisecond or so: something actively said no. Most often nothing is listening on that port (service stopped, wrong port), or a firewall configured to reject.
Slow: loss or waiting?
Retransmissions and duplicate ACKs mean packets are getting lost. Duplicate ACKs are the receiver saying "I'm still waiting for an earlier piece".
Other quick clues
DNS: a response with "No such name" (NXDOMAIN) means the name doesn't exist, often a typo. No DNS reply at all means the DNS server isn't reachable.
Key points
- Full handshake = path works and the port is open. SYN→SYN,ACK time ≈ network RTT.
- RST = refused (often no service). Silence + SYN retries = dropped (often firewall/ACL/routing).
- Retransmissions + dup ACKs = loss. Zero window = slow receiver. Fast handshake, slow reply = slow server.
- DNS NXDOMAIN, unanswered ARP, ICMP unreachable/TTL exceeded and TLS alerts each point somewhere specific.
Words you'll learn
Three-way handshake (SYN, SYN-ACK, ACK) · RST (reset) · Retransmission · Duplicate ACK · Zero window · RTT (round-trip time) · NXDOMAIN (rcode 3)