Cables, Wi-Fi and IP Addressing Faults
Where you are: Module 9 — Network Troubleshooting · Lesson 9.2 · Based on Chapter 9 (§9.2–9.3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Carry out the physical and data link checks for a wired connection, using substitution to prove a suspect part.
- Troubleshoot a Wi-Fi connection in a logical order.
- Read an IP configuration and judge whether the address, subnet mask, default gateway and DNS server are valid.
- Diagnose a 169.254.x.x address, an IP address conflict, an unreachable gateway and a "gateway works, internet doesn't" fault.
Watch: Cables, Wi-Fi and IP Addressing Faults
The video works up the bottom three layers of the OSI model. It shows the physical checks, the order for Wi-Fi faults, the four values to read in ipconfig, and two fictional cases: a desktop that receives a 169.254 address after a power cut, and an office where the gateway answers but the internet does not. Keep these questions in mind:
- What does an address beginning 169.254 tell you, and what does it not tell you?
- Why is a missing default gateway such a strong clue?
- If the router replies to a ping but a public address does not, where is the fault?
Layers 1 and 2: the physical checks
Start with what you can see and touch. The book's checks for wired connections are:
- Cables and connectors. Look at both ends; unplug and reseat them firmly.
- Link lights. Most network ports have a small light that shows a physical link. Check the light on the computer and on the switch port. No light usually means no link.
- A different cable. This is substitution: swap the suspect cable for one known to work. If the problem disappears, the old cable was faulty.
- A different switch port. Ports fail too. Moving to a known-good port tests the port itself.
These checks take a couple of minutes and settle the bottom of the stack before you spend time on settings.
Wi-Fi: the same layers, without the cable
A wireless connection still has a physical layer (the radio signal) and a data link layer (the association with an access point, the device that provides the Wi-Fi network). Work through the book's checks in order:
- Is wireless enabled? Check the Wi-Fi switch or setting, and that airplane mode is off.
- Is the correct network selected? A neighbour's network with a similar name, or a guest network with no access to internal systems, is an easy mistake.
- Is the signal strong? Move closer to the access point and test again. If it works close by and fails further away, the problem is distance or obstacles, not the computer.
- Forget and rejoin. Remove the saved network and join it again, typing the correct password carefully. This clears a stale saved password or profile.
- Look for interference. Microwave ovens, thick walls and crowded neighbouring networks can all weaken or disrupt the signal.
Layer 3: reading the IP configuration
Once the link is working, run ipconfig on Windows (the book's appendix lists ifconfig on macOS and ip addr on Linux) and check four values:
| Value | What it means | Example |
|---|---|---|
| IP address | The device's own address on the network | 192.168.1.37 |
| Subnet mask | Which addresses count as local | 255.255.255.0 |
| Default gateway | The router that carries traffic to other networks | 192.168.1.1 |
| DNS server | The server that turns names into addresses | shown by ipconfig /all |
Note that plain ipconfig on Windows does not list DNS servers; use ipconfig /all for the full configuration.
Most networks hand these values out automatically using DHCP (Dynamic Host Configuration Protocol), usually from the router. When something goes wrong at layer 3, the book's table tells you what each symptom means:
| Symptom | Likely cause | Action |
|---|---|---|
| Address 169.254.x.x | No response from the DHCP server | Check the router and cable; ipconfig /release then /renew |
| "IP address conflict" | Two devices with the same address | Renew the address; correct static assignments |
| Cannot ping the gateway | Local link or configuration fault | Check the cable, Wi-Fi and IP settings |
| Gateway reachable, internet not | Router, modem or ISP fault | Power-cycle the modem and router; check the provider's status |
A few points deserve emphasis:
- 169.254.x.x means the computer asked for an address and no DHCP server answered, so it gave itself one. You will usually see no default gateway at all. The fault is between the computer and the DHCP service: the cable, the Wi-Fi association, or the router itself.
- Conflicts most often happen when someone types a fixed (static) address by hand that the DHCP server also hands out. Find and correct the static assignment, rather than renewing repeatedly.
- Gateway unreachable keeps the fault inside your own network. Gateway reachable but no internet moves it outside: the router's connection, the modem or the provider. Power-cycle in order (modem, wait, then router), as you learnt in Module 5.
Beyond the book (2026 note): The 169.254.0.0/16 range is reserved for IPv4 link-local addresses, which a host may configure for itself when no routable address is available (RFC 3927). Microsoft's documentation calls this Automatic Private IP Addressing, or APIPA (ipconfig, Microsoft Learn). The same page explains that /release discards the adapter's current DHCP configuration, so never run it on a computer you are controlling remotely: you would cut your own connection. Current equivalents for renewing an address: on macOS, System Settings > Network, select the service, Details > TCP/IP > Renew DHCP Lease (Apple Support); on Windows 11, IP settings live under Settings > Network & internet, then Wi-Fi (Manage known networks) or Ethernet, then Edit next to IP assignment, where Microsoft recommends Automatic (DHCP) (Microsoft Support). On Linux, ip route show lists the routing table, including the default route (the gateway) (ip-route(8), man7.org).
Worked example
(Fictional scenario.) After an overnight power cut, one desktop PC in a small office has no internet at 08:30. Colleagues' laptops work normally.
- Identify. One device only, so the shared equipment is probably fine. The PC is wired and gets its address automatically.
- Theory and test, layer 1. The cable is seated and the link lights on the PC and switch are on. Layer 1 is cleared.
- Test, layer 3.
ipconfigshows Autoconfiguration IPv4 Address 169.254.23.7, subnet mask 255.255.0.0 and a blank default gateway. The computer asked for an address and nobody answered. - Theory refined. When power returned, the router and the PC started at the same time. The PC asked for an address while the router was still starting, gave up and assigned itself a link-local address.
- Plan and implement. As the book advises:
ipconfig /release, thenipconfig /renew. One change only. - Verify. The PC now has 192.168.1.42 with gateway 192.168.1.1. A ping to the gateway gets replies, and the user opens their email and usual websites.
- Document. The ticket records the cause and the fix, and notes that a small UPS (uninterruptible power supply) for the network equipment would prevent a repeat, an idea you will see again in the Module 14 case studies.
Try it
Use your own computer or a lab machine. This activity only reads settings; do not release or change anything.
- Run
ipconfig /all(Windows), or open your network details on macOS or runip addrandip route showon Linux. - Record your IP address, subnet mask, default gateway and DNS server.
- Decide whether each value is valid: is the address in the same range as the gateway? Is there a gateway at all? Does the address begin 169.254?
- Ping your default gateway and record the result.
- If you use Wi-Fi, walk the five Wi-Fi checks and write one sentence on each about your own connection (for example, the name of the network and the signal strength where you sit).
You have finished when you have recorded all four values, written a valid/invalid judgement for each with a reason, and noted the gateway ping result.
Knowledge check
ipconfig shows 169.254.10.4 and no default gateway. What is the most likely cause?
A laptop's Wi-Fi works beside the access point but drops at the far end of the building. What has this test shown?
A computer can ping its default gateway but cannot ping a public address. Where does the fault most likely lie?
Which value does plain ipconfig on Windows NOT show, so that you need ipconfig /all?
Answers explained
- c — a 169.254 address is self-assigned when no DHCP server answers, which is also why there is no gateway; DNS, websites and browser caches sit higher in the stack and cannot cause it.
- a — changing only the distance and seeing the result change isolates the signal; a conflict, DNS or provider fault would not depend on where you stand.
- d — a reachable gateway proves the local link and configuration work, so the fault is beyond it; the cable and Wi-Fi password are clearly working, and keyboard layout is irrelevant.
- b — plain
ipconfigshows the address, mask and gateway; DNS servers appear only in the/alloutput.
Key takeaways
- Settle layer 1 first: cables, connectors, link lights, and substitution of cables and ports.
- For Wi-Fi: enabled, correct network, strong signal, forget and rejoin, then interference.
- At layer 3, read four values: address, mask, gateway and DNS server.
- 169.254 means no DHCP response; gateway unreachable is local; gateway reachable with no internet points beyond your network.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §9.2–9.3; §5.3 (power-cycling order); §7.3 and Appendix C (commands)
- RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
- ipconfig — Microsoft Learn
- Renew your IP address from the DHCP server on Mac — Apple Support
- Essential Network Settings and Tasks in Windows — Microsoft Support
- ip-route(8) — man7.org
