Networking Fundamentals and IP Addressing

At its simplest, a network is just two or more devices connected so they can share information. That information travels in small chunks called packets. Think of a packet as a digital envelope: it has a sender address, a destination address, and some content inside. The rules that govern how these envelopes are addressed, sent, and received are called protocols. The most important protocol for addressing is the Internet Protocol, or IP.

Every device on an IP network gets a unique identifier called an IP address. There are two main versions in use today: IPv4 and IPv6. IPv4 addresses are 32-bit numbers, which means there are about 4.3 billion possible addresses. You see them written as four decimal numbers separated by dots, like 192.168.1.1. IPv6 was created because the world ran out of IPv4 addresses. IPv6 addresses are 128-bit numbers, giving a mind-bogglingly huge number of addresses. They are written as eight groups of hexadecimal digits, like 2001:0db8:85a3:0000:0000:8a2e:0370:7334.

An IP address alone is not enough. Every IP address also has a subnet mask. The subnet mask tells the device which part of the address refers to the network and which part refers to the specific device (called the host) on that network. For example, if your IP address is 192.168.1.10 and your subnet mask is 255.255.255.0, the first three numbers (192.168.1) identify your network, and the last number (10) identifies your specific device. This is called classful addressing, and it is how routers decide where to send packets.

A router is a device that connects different networks together. When you send data to a website, your computer checks its own subnet mask. If the destination IP is on a different network, your computer sends the packet to its default gateway — which is almost always a router. The router then looks at the destination IP, consults its routing table (a list of known networks and the best path to reach them), and forwards the packet towards its destination. This process happens at every router along the path until the packet reaches the destination network.

To make IP addressing more flexible, network engineers use subnetting. Subnetting means taking one large network and dividing it into smaller, more manageable subnetworks (subnets). For example, a company might have a single block of IP addresses but divide it into separate subnets for the sales department, the engineering department, and the guest Wi-Fi. Each subnet is isolated from the others for security and performance, and routers (or layer 3 switches) control traffic between them.

Another critical concept is the difference between public and private IP addresses. Public IP addresses are unique across the entire internet and are assigned by the Internet Assigned Numbers Authority (IANA). Private IP addresses are reserved for use inside private networks and are not routable on the public internet. The most common private IP ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. When a device with a private address needs to reach the internet, a router performs Network Address Translation (NAT). NAT changes the private source IP address to the router's public IP address, so the response can find its way back.

Dynamic Host Configuration Protocol (DHCP) automates IP address assignment. When a device joins a network, it broadcasts a DHCP discover message. A DHCP server responds with an offer of an IP address, subnet mask, default gateway, and DNS server addresses. The device accepts the offer, and the server records the lease so it does not give the same address to two devices. This eliminates the need for manual configuration and prevents address conflicts.

Finally, the Domain Name System (DNS) translates human-readable domain names (like www.example.com) into IP addresses. When you type a website name into your browser, your computer queries a DNS server. The DNS server looks up the IP address associated with that domain and returns it to your computer, which then uses that IP to establish a connection. Without DNS, you would have to remember numbers for every website you visit.

An IT professional at a medium-sized company receives a ticket that users in the finance department cannot access the company's cloud-based accounting software. The IT professional starts by asking a simple question: can anyone access the software? If yes, then the problem is isolated. If no, the problem is broader.

The IT professional first checks whether the finance department's devices have valid IP addresses. They open a command prompt on a user's computer and run 'ipconfig' (Windows) or 'ifconfig' (Linux/macOS). This shows the current IP address, subnet mask, default gateway, and DNS servers. If the IP address starts with 169.254.x.x, it means the device could not reach a DHCP server and has assigned itself an Automatic Private IP Addressing (APIPA) address. That points to a DHCP server problem.

Next, the IT professional tries to ping the default gateway. The ping command sends a small packet to the gateway and waits for a reply. If the gateway does not respond, the issue is likely a physical cable, a faulty switch port, or a misconfigured network interface. If the gateway responds, the problem is further upstream.

The IT professional then pings a known public DNS server, like 8.8.8.8 (Google DNS). If that works but ping to www.example.com fails, the issue is DNS resolution. The IT professional checks the DNS server settings on the device and may try flushing the DNS cache using 'ipconfig /flushdns'. If the problem persists, they check the company's internal DNS server.

If the devices have IP addresses in a different subnet than expected (for example, a device in finance shows an address from the engineering subnet), it suggests a DHCP scope misconfiguration. The IT professional logs into the DHCP server, checks the scope settings, and ensures the finance department's devices are assigned addresses from the correct pool.

In a more complex scenario, the IT professional checks the routing table on the core router. They run 'tracert' (Windows) or 'traceroute' (Linux) to the destination IP to see where packets stop being forwarded. This step-by-step path reveals if a router along the way is misconfigured or down.

The IT professional also checks for IP address conflicts. If two devices have the same IP address, one or both will lose connectivity. They can look in the DHCP server logs for duplicate lease assignments or use a network scanning tool to see which devices are responding to which IPs.

Finally, if the problem is isolated to a single subnet, the IT professional checks the subnet mask. A wrong subnet mask can cause a device to think a destination is local when it is actually remote, causing the packet to never reach the router.