Back to course

Basic Troubleshooting Methodology (The OSI Approach)

Networking Fundamentals: The 0 to Hero Guide

Lesson 49: Basic Troubleshooting Methodology (The OSI Approach)

Effective troubleshooting requires a logical, systematic approach. The OSI model provides the perfect framework: start at the bottom (Physical) and work your way up (Application).

The Bottom-Up Approach

1. Layer 1: Physical (Is it plugged in?)

  • Check: Is the network cable securely plugged in? Are the lights on the NIC and the switch port active (Link Light)? Is the port speed correct?
  • Tools: Visual inspection, cable tester.

2. Layer 2: Data Link (Local Address Issues)

  • Check: Can the device talk to other devices on the same segment? Check the switch connection.
  • Tools: Check MAC address tables, check for broadcast storms, look for an APIPA address (169.254.x.x).

3. Layer 3: Network (Routing Issues)

  • Check: Can you ping your local Default Gateway? Can you ping an IP address on a remote network (e.g., 8.8.8.8)? Is your IP address and subnet mask correct?
  • Tools: ping, ipconfig /all, traceroute.

4. Layer 4: Transport (Port Issues)

  • Check: Is the application running? Is the firewall blocking the required port (e.g., is TCP 80 open)?
  • Tools: Port scanners, firewall logs.

5. Layer 5-7: Application, Presentation, Session (Service Issues)

  • Check: Is DNS resolving correctly? Can you access the resource using the IP address instead of the hostname (bypassing DNS)? Are the client application settings correct?
  • Tools: nslookup, checking application logs.

Golden Rule: Rule out the simplest physical problems before spending hours on complex software issues.