Network services issues

This objective covers troubleshooting network services and logical configurations (Layers 2 and 3). When a user reports that they cannot access a server, or when an entire network block suddenly slows to a crawl, the issue often stems from a misconfigured IP parameter, an exhausted address pool, or a Spanning Tree Protocol breakdown.

Let’s look at how to diagnose and resolve these common logical network failures.

1. Switching & Layer 2 Issues

Spanning Tree Protocol (STP) Failures

When an STP malfunction occurs, it can cause catastrophic network failure. You must be able to spot these four core STP anomalies:

• Network Loops / Broadcast Storms: If STP fails to block a redundant link, broadcast frames (such as DHCP discovery or ARP requests) will circulate endlessly in the loop. Because Layer 2 frames do not have a Time-to-Live (TTL) counter to kill them, they multiply exponentially.
  • Symptom: Switch link lights flash frantically, CPU utilization hits 100% across all switches, and the entire local network crashes within seconds.
• Incorrect Root Bridge Selection: The Root Bridge is the master switch that controls the STP topology tree. By default, switches elect the Root Bridge based on the lowest MAC address. If you leave settings at default, an ancient, slow backup switch sitting in a closet might win the election.
  • Symptom: Network traffic takes inefficient, winding paths through weak hardware to cross the room.
  • Fix: Manually lower the Bridge Priority value on your core backbone switch to force it to win the election explicitly.
• Misconfigured Port Roles & States: STP assigns roles (Root Port, Designated Port, Blocking Port) and moves interfaces through states (Blocking, Listening, Learning, Forwarding). If an administrator forces a port to skip these states using a feature like PortFast on an interface that is actually hooked to another switch, it creates an instantaneous loop before STP can catch it.

Incorrect VLAN Assignment

• The Scenario: A new computer is plugged into an office wall jack. It receives an IP address, but it cannot reach the local database server or print to the departmental printer.
• The Root Cause: The switch port interface has been accidentally left assigned to the wrong VLAN database ID (e.g., it’s stuck on the Guest VLAN instead of the Corporate Data VLAN).
• The Trap: The physical link light is solid green, and the cable is fine, but the device is logically trapped in the wrong broadcast domain.

2. Route Selection & Routing Table Issues

A router relies on its routing table to pass packets between subnets. If the table is incomplete, packets get dropped.

• Missing Routes in the Routing Table: If a router doesn’t have an explicit entry for a destination network block, it doesn’t guess—it drops the packet. This often happens if a dynamic routing protocol (such as OSPF) loses neighbor adjacency, or if a manually configured static route contains a typo in the target subnet address.
• Misconfigured Default Routes: A default route (0.0.0.0/0) is the fallback rule that tells a router where to send traffic if the destination IP matches nothing else in the routing table (i.e., sending traffic out to the public Internet). If the default route points to the wrong upstream next-hop router interface, all public internet traffic from the office will be sent into a black hole.

3. Dynamic IP & Infrastructure Issues

Address Pool Exhaustion

• The Scenario: Monday morning arrives, employees log in, and suddenly the last 15 workers to enter the building cannot connect to anything. Their laptops show an “Autoconfiguration” IP address starting with 169.254.x.x.
• The Root Cause: Your DHCP scope has run completely out of available IP addresses to lease. This happens if your scope is too small (e.g., a /24 subnet with only 100 addresses allocated), or if your Lease Time is set too long on a network with high turnover, such as a coffee shop or a public guest Wi-Fi network where departed users hold onto leases for days.

4. Misconfigured Endpoint IP Parameters

When typing static IP parameters manually into a server or router interface, a single-digit error will instantly sever connectivity.

Incorrect Default Gateway

• Symptom: The host can ping and communicate with other local computers sitting right next to it on the same switch, but it cannot reach the Internet, another office branch, or a separate internal VLAN.
• The Reason: The host has been configured with an incorrect or non-existent default gateway IP address. The computer knows how to talk locally via MAC addresses, but when it needs to send a packet outside its own network boundary, it doesn’t know which local router interface handles the exit path.

Incorrect IP Address & Duplicates

• Incorrect IP Address: If a technician types an IP address belonging to a different subnet entirely (e.g., placing 192.168.2.50 on a network where everyone else is running 192.168.1.x), the host will be completely isolated, unable to communicate locally or remotely because its software calculations don’t match the local wire traffic.
• Duplicate IP Address: Two devices on the same local network are accidentally configured with the same IP address.
  • Symptom: Intermittent, erratic connectivity drops for both devices. As they send out ARP replies, the local switch gets confused, constantly bouncing traffic back and forth between the two physical switch ports depending on which device talked last.

Incorrect Subnet Mask

• What it does: The subnet mask defines the boundary between the network portion and the host portion of an IP address.
• The Result: If a machine is configured with an incorrect mask (e.g., typing /24 instead of /16), it will perform its internal binary calculation incorrectly. It might believe a remote internet server is actually sitting on its local switch, trying to communicate with it using local ARP requests instead of forwarding the packet to its default gateway router, causing immediate connection timeouts.

Network Services Troubleshooting Matrix

Problem / Symptom	Logical Root Cause	Core Exam Identifier / Clue
100% Switch CPU / Flashing Lights	STP Failure / Loop	Broadcast storm caused by unblocked redundant links.
169.254.x.x (APIPA Address)	DHCP Scope Depletion	Address pool exhaustion or a dead DHCP server.
Can ping locally, but not remotely	Default Gateway Fault	The host’s gateway IP is missing, misconfigured, or dead.
Erratic, bouncing network drops	Duplicate IP Address	Two physical machines fighting over the same IP layer.
Host sends ARPs for remote sites	Incorrect Subnet Mask	The client’s bit-boundary calculation misidentifies remote IPs as local.