- by x32x01 ||
🚨 Imagine you're a network administrator responsible for a company with 500 employees. Suddenly, all devices lose access to the main server and the internet at the same time.
What's the first thing you should check?
Instead of troubleshooting every computer individually, look for a common point of failure in the network infrastructure. A core switch failure, gateway outage, routing issue, or network configuration change could affect hundreds of devices simultaneously.
Here's how to investigate the problem step by step.
Ask these questions:
Check:
Look for interfaces that are down, administratively disabled, or showing unexpected errors.
From an affected device, ping its default gateway.
If there's no response, investigate:
On Cisco routers, run:
Check whether:
DHCP: Check whether devices are receiving valid IP addresses, subnet masks, and default gateways.
DNS: Verify that internal servers and external domains resolve correctly.
Useful Windows commands:
If existing devices still have valid IP configurations but new devices cannot connect, investigate DHCP first.
Look for:
A good troubleshooting order is:
Reducing the time needed to identify the root cause means less downtime, faster recovery, and fewer unnecessary troubleshooting steps.
What's the first thing you should check?
Instead of troubleshooting every computer individually, look for a common point of failure in the network infrastructure. A core switch failure, gateway outage, routing issue, or network configuration change could affect hundreds of devices simultaneously.
Here's how to investigate the problem step by step.
🔍 1. Identify the Scope of the Failure
First, determine which devices and network segments are affected.Ask these questions:
- Are all devices offline, or only specific departments?
- Are multiple VLANs affected?
- Can devices communicate within the same VLAN?
- Is the problem limited to internet access or internal servers as well?
🔌 2. Check the Core Switch
The core switch connects major parts of the network. If it fails, hundreds of connected devices may lose access to critical services.Check:
- Core switch power and operational status.
- Uplink connections to access switches.
- Interface errors and packet drops.
- Recent link failures.
Bash:
show interfaces status
show ip interface brief 🌐 3. Verify the Default Gateway
The default gateway allows devices to communicate with networks outside their local subnet.From an affected device, ping its default gateway.
If there's no response, investigate:
- Router interface status.
- VLAN configuration.
- Switch access and trunk ports.
- SVI (Switch Virtual Interface) status.
🔄 4. Check the Routing Table
If devices can reach their local gateway but cannot access remote networks, investigate routing.On Cisco routers, run:
Bash:
show ip route Check whether:
- Required routes are available.
- The default route is present.
- Routing protocols are working correctly.
- Recent routing changes affected network reachability.
🖥️ 5. Verify DHCP and DNS Services
DHCP and DNS failures can cause different connectivity problems.DHCP: Check whether devices are receiving valid IP addresses, subnet masks, and default gateways.
DNS: Verify that internal servers and external domains resolve correctly.
Useful Windows commands:
Bash:
ipconfig /all
ipconfig /renew
nslookup example.com 📊 6. Review Logs and Network Monitoring
Check network device logs and monitoring alerts around the exact time the outage started.Look for:
- Interface or uplink failures.
- Core switch or router crashes.
- High CPU or memory usage.
- STP topology changes.
- Configuration changes.
- Power or hardware failures.
⚡ The Most Important Troubleshooting Principle
When hundreds of devices lose connectivity at the same time, start with shared network infrastructure, not individual computers.A good troubleshooting order is:
- Identify the affected network segments.
- Check core switches and uplinks.
- Verify default gateways and VLAN interfaces.
- Investigate routing.
- Check DHCP and DNS.
- Review logs and recent configuration changes.
Reducing the time needed to identify the root cause means less downtime, faster recovery, and fewer unnecessary troubleshooting steps.