Ports, TCP and UDP: refused, timed out or open?
▶ Start the interactive lesson
A ticket says "the server is down". You ping it: it replies. The app still fails. Maya smiles: "Ping proves the host is there. It says nothing about the service. Let's knock on the actual door."
Key points
- Every service listens on a port. TCP is connection-based (3-way handshake: SYN, SYN-ACK, ACK) and reliable. UDP just sends datagrams with no handshake: fast and simple, used where speed or tiny exchanges matter (DNS queries, NTP, syslog, RADIUS).
- Ports to know cold: 22 SSH, 23 Telnet, 25 SMTP, 53 DNS, 67/68 DHCP, 80 HTTP, 123 NTP, 443 HTTPS, 514 syslog, 1812/1813 RADIUS, 49 TACACS+, 3389 RDP.
- Three outcomes when you test a port: open (handshake completes), refused (the host answered "no one here", so the path is fine and the service is down), or timed out (nothing came back, so something on the path, often a firewall, dropped it, or the host is down).
- Tools: telnet IP PORT or nc -zv IP PORT for TCP, nc -zvu for UDP (UDP results are less certain on real networks), and Test-NetConnection in Windows PowerShell.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →