8 Common Network Faults: Diagnosis and Quick Fixes

Fault 1: Switch cannot communicate after power‑on

Symptom: The newly powered‑on switch does not connect to the network immediately; it takes several minutes for connectivity and speed to improve.

Analysis: Managed switches enable the Spanning Tree Protocol (STP) by default to prevent loops. When the switch boots, each port goes through listening, learning, and forwarding states, which takes about 3–5 minutes.

Solution: Enable PortFast on ports that connect directly to end devices so they transition to forwarding state instantly, or temporarily disable STP (with caution about possible loops).

Fault 2: Five‑port switch only provides four usable ports

Symptom: In an office with four PCs and one uplink, a 5‑port switch is used, but the port adjacent to the uplink (port 1) does not work.

Analysis: The uplink port is not a separate physical port; it is simply a regular port wired for a straight‑through connection to another switch. The switch’s ASIC is typically designed for 4, 8, 16, 24‑port configurations, so a 5‑port design wastes three internal modules.

Solution: Replace the 4‑port switch with an 8‑port model.

Fault 3: "COL" indicator constantly on or flashing, no communication

Symptom: All client PCs lose connectivity to the server; ping is intermittent, and the hub’s COL (collision) LED stays lit or flashes.

Analysis: The COL LED signals collisions. Continuous flashing indicates frequent collisions; a solid light indicates a high collision rate, often caused by a faulty hub rather than the NIC.

Solution: Replace the hub.

Fault 4: Intermittent connectivity after upgrading to Gigabit Ethernet

Symptom: A server equipped with a 1000 Mbit/s NIC experiences unstable, intermittent connections to the network, despite successful cable‑tester results.

Analysis: The issue is likely caused by sub‑par Category‑5 cabling. Gigabit (1000Base‑T) requires all four twisted‑pair conductors and stricter electrical performance; poor cable quality or bad terminations cause excessive crosstalk and signal loss.

Solution: Replace the cabling with Category‑6 (or better) components.

Fault 5: Link LED flashes constantly but network speed is extremely slow

Symptom: The server’s web pages load very slowly or not at all, ping fails, yet the switch’s Link LED blinks rapidly, indicating heavy traffic.

Analysis: The network is suffering a broadcast storm, which can be triggered by worms, mis‑configured ports, missing STP, incorrect cabling, or interference.

Solution: Update the server’s OS patches, install a network‑aware antivirus, and ensure the latest virus definitions are applied.

Fault 6: Server resource‑sharing problems

Symptom 1: In a Windows domain, a shared folder cannot be accessed despite permissions being set.

Analysis: NTFS permissions take precedence over share permissions. If they conflict, NTFS rights win.

Solution: First assign the appropriate NTFS rights, then configure share permissions accordingly (e.g., give user A "Full Control" on the folder and "Read" for Everyone).

Symptom 2: Some shared folders are invisible in "Network Neighborhood" while others appear.

Analysis: Windows distinguishes between system‑share (hidden) and user‑share. System shares end with a "$" and are not shown in Network Neighborhood.

Solution: Remove the trailing "$" from the share name to make it visible.

Fault 7: Hub and router cannot share Internet access

Symptom: Computers connected through a hub cannot reach the router or the Internet, while those directly on the router work fine.

Analysis: Possible causes include a faulty hub, incorrect cabling or cascade configuration, or a router LAN‑port failure.

Solution: Test with a known‑good Ethernet cable; if the problem persists, replace the hub.

Fault 8: IP address conflict

Symptom: Windows reports an IP address conflict with a specific MAC address, causing brief network outages.

Analysis: Two devices on the same LAN have been assigned the identical IP address, typically due to mis‑managed static assignments.

Solution: Identify the conflicting device via its MAC address (using IPCONFIG /ALL), then either change its IP or bind the legitimate IP to the correct MAC using the ARP –S command.