Short-Term Networking And Security Programs

When a workstation can “see the network” but can’t reach a server, the problem is usually not magic-it’s layering. One device might be building the wrong frame on the way out (Ethernet layer), while another might be answering on the wrong IP network (IP addressing), or a firewall might be blocking the wrong transport (TCP versus UDP). To troubleshoot fast, you need a clean mental map: OSI Layers for how data moves, then TCP/IP addressing for where it goes.

This chapter builds that foundation for the short-term training programs in networking and security: you will connect the OSI model review to practical TCP/IP essentials like TCP vs UDP, IP/ICMP/ARP, IP address classes, and subnetting principles. You’ll also align your thinking with the Course I - Introduction to LAN/ WAN Technologies Duration: 5 days focus on designing, administering, installing, configuring, managing, and supervising local and wide area data networks-because correct addressing and correct layer behavior are the first gates for every later topic (routing, VLANs, WAN services, and security controls).

Learning Objectives

• Match common troubleshooting symptoms to the correct OSI layer and TCP/IP component.
• Correctly interpret TCP vs UDP, and identify when ICMP, ARP, or IP is the relevant piece.
• Calculate a subnet using IP address classes and subnet masking principles.

How It Works

OSI model review (seven layers, one job: move data)

OSI model - a reference model that splits network communication into seven layers, from physical signals up to application communication.

You don’t need to memorize every detail to use it. You use it to decide “which part is responsible” when something breaks.

Here’s the practical way to use the OSI model in daily work:

• Layer 1 (Physical) - sends raw bits over cabling or fiber. If you have a bad cable, link lights may fail.
• Layer 2 (Data Link) - moves frames on a local network and uses MAC addresses (Media Access Control addresses). Ethernet and switching live here.
• Layer 3 (Network) - routes packets across networks using IP addresses.
• Layer 4 (Transport) - provides end-to-end delivery using TCP (Transmission Control Protocol) or UDP (User Datagram Protocol).
• Higher layers handle session, presentation, and application behavior.

A quick differentiator you can apply immediately: if a switch learns the wrong MAC address and sends traffic to the wrong port, the failure shows up as a Layer 2 problem-long before you ever reach IP subnetting.

Practical takeaway: Ask yourself, “Where is the evidence?” Link lights, ARP tables, routing tables, and application logs each point to different layers.

---

Network components and network types (what’s actually in the path)

Network components - the physical and logical building blocks that create a working network path (like NICs, cabling, switches, routers, and end systems).

In a LAN/WAN project, the path matters as much as the protocols.

Network types - common categories of networks based on coverage and design, such as LAN (Local Area Network) for a building and WAN (Wide Area Network) for multiple sites.

Course I - Introduction to LAN/ WAN Technologies Duration: 5 days stresses that you must visualize local and wide area data networks together, because addressing and routing decisions made for LANs often affect WAN reachability.

---

TCP/IP essentials (what talks, how it talks, and how it finds addresses)

TCP (Transmission Control Protocol) - a transport protocol that provides reliable delivery with acknowledgments and ordered data.

UDP (User Datagram Protocol) - a transport protocol that sends data without reliability guarantees (no built-in ordering or acknowledgments).

IP (Internet Protocol) - the network protocol that delivers packets based on IP addressing and routing.

ICMP (Internet Control Message Protocol) - a control protocol used for diagnostics and error reporting (for example, “destination unreachable” messages).

ARP (Address Resolution Protocol) - the mechanism that maps an IP address to a MAC address on the local network.

A useful rule of thumb for troubleshooting:

• If you can’t reach a host at all, suspect IP and routing/subnetting.
• If you can reach the network but not the host, suspect ARP and local reachability.
• If a ping fails, ICMP behavior is often involved.
• If you can reach a server but a specific service won’t connect, suspect TCP vs UDP and port behavior.

Also note the Course Outline emphasis on Transport Layer Protocols, TCP, UDP, IP, ICMP, ARP, RARP, IP Addressing, IP Address Classes, Subnetting Principles, Default and subnet masking. Even if RARP (Reverse Address Resolution Protocol) is rarely used today, the point remains: address discovery mechanisms matter when the “sender knows the IP but not the MAC.”

...