How to Troubleshoot Network Switch Issues: 4 Common Failures and Fixes

Updated October 2026. First published April 2025.

How a network switch works

A switch connects the wired devices in a building. It learns which device (MAC address) is on which port by watching traffic, stores that in its MAC address table, and then sends each frame only to the port where the destination lives. When it sees a destination it has not learned yet, it floods the frame to all ports in that VLAN until the device answers.

Managed switches add VLANs (separate networks on the same hardware), PoE to power phones, cameras and access points, link aggregation and monitoring. Each of those features is also something that can be misconfigured.

Before you start

• Find out exactly what is affected: one device, one desk, one floor, or everyone?
• Ask what changed recently: moves, new equipment, a firmware update, a power event.
• Have the port map or labels to hand so you know which switch port feeds which jack.

1. Port and link failures

Symptoms: a device shows "no network cable" or "unidentified network", the port light is off or amber, or the connection drops in and out.

1. Check the link lights on both the device and the switch port.
2. Swap the patch cable at each end. Patch cords fail far more often than wall cabling.
3. Move the device to a known-good port. If it works, the original port, jack or cable run is the problem.
4. On a managed switch, check the port status: is it administratively disabled, or shut down by port security or a loop-protection feature (err-disabled)?
5. Look at the port's error counters. Rising CRC or input errors point to a bad cable, jack or termination.
6. Test the cable run end to end with a cable tester. Re-terminate or replace it if it fails.

2. Power and hardware failures

Symptoms: the whole switch or a block of ports goes dark, the switch reboots by itself, fans are loud or silent, or PoE devices (phones, cameras, access points) keep restarting.

1. Check the power source: UPS status, outlet, power cord and any redundant power supply.
2. Check the closet temperature and airflow. Overheating causes random reboots.
3. Check the PoE budget. If you have added cameras or new access points, the switch may not have enough PoE power for all of them.
4. Review the switch logs for power, temperature or fan alarms.
5. Power-cycle the switch only after warning users, and save the configuration first.
6. If faults continue, replace the power supply or the switch. Keep a configuration backup so a replacement can go in quickly.

3. VLAN failures

Symptoms: a device gets the wrong IP address or none at all, phones register but computers do not, or two groups of devices cannot reach each other.

1. Confirm which VLAN the port is in, and compare it with what the device needs.
2. Check the trunk links between switches carry every VLAN that needs to pass.
3. Make sure the native VLAN matches on both ends of a trunk.
4. Check that the voice VLAN is set on ports with IP phones.
5. Confirm DHCP is available on that VLAN (a DHCP scope or helper address on the router or firewall).
6. Check routing or firewall rules between VLANs if devices on different VLANs need to talk.

4. Compatibility and negotiation problems

Symptoms: the link is up but slow, file transfers stall, video calls stutter, or a link runs at 100 Mbps instead of 1 Gbps.

1. Check speed and duplex on both ends. Both should auto-negotiate, or both should be set to the same fixed values. A duplex mismatch causes slow, error-filled links.
2. A gigabit port stuck at 100 Mbps often means a damaged pair in the cable or jack. Test the cable.
3. Check that fiber modules (SFPs) match the fiber type, wavelength and speed on both ends, and are supported by the switch.
4. Look for loops: a cable plugged into two wall jacks can flood the network. Make sure spanning tree is enabled.
5. Update switch firmware if the vendor lists a fix for the problem you see.

When to call for onsite help

• A switch or power supply keeps failing after the basic checks.
• The problem involves multiple switches, VLANs or a recent configuration change you cannot roll back.
• You suspect someone plugged in an unauthorized device or changed settings.
• Your IT team or MSP is remote and needs hands on site.

DC Metro IT Help sends technicians to sites across Washington DC, Maryland and Northern Virginia to work with your IT team or NOC on the phone: checking links, swapping hardware, re-terminating cable and documenting what we found. See smart hands services.

Frequently asked questions