CompTIA Network+: Troubleshooting Cabling, Interfaces, & Network Services

Introduction

Network troubleshooting involves identifying and resolving problems that affect connectivity, performance and availability. Network issues can originate from physical cabling, network interfaces, hardware, switches, routing configurations or incorrect IP settings.

A structured troubleshooting approach helps administrators identify the root cause without making unnecessary changes.

This article covers the main topics from the course:

1. Common cabling issues
2. Interface issues
3. Hardware and Power over Ethernet (PoE)
4. Common switching issues
5. Route selection problems
6. DHCP address pool considerations
7. Default gateway issues
8. IP addressing conflicts
9. Incorrect subnet masks

1. Common Cabling Issues

Cabling provides the physical connection between network devices. Incorrect cable selection, poor termination or physical damage can cause slow connections, intermittent connectivity and complete network failure.

Cable selection

Choosing the correct cable type is important for maintaining network speed, reliability and signal quality.

When selecting a cable, consider:

• Required transmission speed.
• Supported distance.
• The environment in which the cable will operate.
• The potential for electromagnetic interference (EMI).
• Compatibility with connected network devices.

Shielded cables may be appropriate in environments with significant electromagnetic interference. Shielding helps protect signals from external electrical noise when the cable and installation are suitable.

Common cabling faults

Incorrect cable type: A cable may not support the required speed or operating conditions, creating a bottleneck.

Damaged cable: Physical damage can interrupt connectivity or cause intermittent faults.

Poor termination: Incorrectly terminated connectors or inconsistent wiring can prevent reliable communication.

Incorrect transmitter and receiver wiring: The transmitting and receiving conductors must be connected appropriately for the equipment and cable type.

Electromagnetic interference: Electrical equipment or other sources of interference can affect signal integrity, especially when the cabling installation is unsuitable for the environment.

Troubleshooting approach

1. Inspect the cable for damage.
2. Check that both ends are connected securely.
3. Confirm that the cable type is suitable.
4. Inspect connector termination and wiring.
5. Test the cable using an appropriate cable tester.
6. Replace a suspected faulty cable and retest the connection.
7. Document the results.

Example: A workstation repeatedly loses its network connection. Inspection reveals a damaged Ethernet cable. Replacing it restores a stable connection.

Exam tip: When a problem affects one device and the physical connection is suspect, check the cable and connector before assuming the switch or router has failed.

2. Interface Issues

A network interface connects a device to the network. Interfaces can be physical, such as Ethernet ports, or logical, such as virtual interfaces.

Problems with an interface can affect connectivity, performance and the ability to communicate with other devices.

Important interface statistics

Network operating systems and monitoring tools provide interface counters that help identify faults.

Metric	Meaning	Possible indication
Dropped packets	Packets discarded before successful delivery	Congestion, insufficient resources or configuration issues
CRC errors	Frames that fail a cyclic redundancy check	Possible cabling, interference or physical-layer problems
Runts	Frames smaller than the permitted minimum Ethernet frame size	Possible collisions or physical-layer issues, depending on the environment
Giants	Frames larger than the permitted maximum frame size	Oversized frames, configuration problems or equipment issues
Overruns	Data that cannot be processed quickly enough by the receiving interface or system	Resource or processing limitations

These counters provide clues rather than automatic proof of a particular fault. Compare counter values over time and correlate them with other evidence.

Interface status

An interface may be unavailable because it is:

• Administratively down: Disabled through configuration.
• Suspended or blocked: Prevented from forwarding traffic by a device state or network policy.
• Physically down: Unable to establish a physical link.
• Operational but experiencing errors: The link is active, but communication is unreliable.

Troubleshooting steps

1. Check the interface's administrative and operational status.
2. Review interface counters and error logs.
3. Inspect the cable and connected port.
4. Confirm interface speed and duplex settings where applicable.
5. Check drivers and configuration.
6. Use operating-system tools or network-management software to gather further evidence.

Hardware failure is possible, but configuration errors, cabling problems and driver issues should also be investigated.

Exam tip: CRC errors, dropped packets, runts and giants are useful clues. Learn what each counter measures and avoid treating any one counter as conclusive evidence of a specific fault.

3. Hardware Issues and Power over Ethernet

Hardware problems can affect connectivity, network performance and device availability.

One important technology is Power over Ethernet (PoE), which allows compatible Ethernet equipment to receive electrical power and data over the same cable.

Devices that use PoE

Examples include:

• Voice over IP (VoIP) phones.
• Wireless access points.
• IP security cameras.
• Compatible Internet of Things (IoT) devices.

PoE can simplify installation because a separate power connection may not be necessary at the device location.

Troubleshooting PoE

If a device does not power on, check:

1. Whether the switch port supports PoE.
2. Whether PoE is enabled and the port is operating correctly.
3. Whether the switch has sufficient available power.
4. Whether the device's power requirements are compatible with the switch.
5. Whether the cable is suitable and correctly terminated.
6. Whether the cable length is within the supported limits.
7. Whether device or switch configuration, firmware or logs indicate a problem.

The course notes identify Category 5e or better cabling and a maximum Ethernet cabling distance of 100 metres as relevant considerations. Actual PoE compatibility and power delivery depend on the equipment, standard, cable and installation.

Total power budget

A PoE switch has a finite power budget. Even if individual ports support PoE, the switch may be unable to supply power to every connected device simultaneously if the total demand exceeds its available capacity.

For example, if several new wireless access points are installed and some fail to power on, check the switch's overall PoE power budget as well as the individual port settings.

Transceivers

Transceivers enable network devices to transmit and receive signals over a particular medium, such as fibre-optic cable.

When troubleshooting a suspected transceiver problem:

• Check compatibility with the switch and cable type.
• Inspect the transceiver and connectors for damage or contamination.
• Confirm that the device is seated correctly.
• Check relevant power, configuration and firmware settings.
• Review interface status and logs.

Exam tip: A PoE problem is not always a faulty cable. Check port capability, power settings, the total switch power budget and device requirements.

4. Common Switching Issues

Switches connect devices within a local area network (LAN). Incorrect switch configurations can prevent communication, create loops or reduce network performance.

Bad switch ports

A faulty or misconfigured port can prevent a device from connecting correctly.

Check:

• Port status.
• Cable condition.
• Interface counters.
• Port configuration.
• Whether the problem follows the device, cable or port when a controlled substitution test is performed.

Bottlenecks

A bottleneck occurs when a component or link limits overall network performance.

Possible causes include insufficient link capacity, congestion or a heavily utilised interface.

Review utilisation statistics and determine where traffic is being delayed or constrained.

VLAN mismatches

A virtual LAN (VLAN) logically separates devices into different broadcast domains.

A VLAN mismatch can occur when a switch port is assigned to the wrong VLAN or when connected switches have inconsistent trunk settings.

Symptoms may include devices being unable to reach resources that should be accessible within the intended network.

Check:

• VLAN assignments.
• Access-port configuration.
• Trunk configuration and allowed VLANs.
• VLAN consistency between connected switches.
• The relevant routing configuration if communication between VLANs is required.

Spanning Tree Protocol loops

Spanning Tree Protocol (STP) helps prevent Layer 2 switching loops in networks with redundant links.

A switching loop can cause broadcast storms, excessive traffic and unstable network operation.

When investigating a suspected loop, review STP status, topology changes, switch logs and port states. Do not randomly disconnect links without understanding the network's redundancy and impact.

Access control list misconfiguration

An access control list (ACL) permits or denies traffic according to configured rules.

An incorrect ACL can block legitimate communication even when physical connectivity and IP addressing are correct.

Check the rules against the intended source, destination, protocol and traffic direction. Review logs and counters where available.

Exam tip: If devices are physically connected but cannot communicate as expected, investigate VLAN configuration, STP, ACLs and port status before concluding that hardware has failed.

5. Route Selection Problems

Routing determines how packets travel between different IP networks. Incorrect or outdated routes can cause traffic to take an inefficient path or fail to reach its destination.

Static routes

A static route is configured manually by an administrator.

Static routes should be reviewed regularly to confirm that their destinations, next hops and interfaces remain valid.

A route may become ineffective if the network changes or the next-hop device is no longer reachable.

Default route

The IPv4 default route is written as:

0.0.0.0/0

It matches destinations when no more specific route is selected. In an IPv6 network, the corresponding default route is:

::/0

A default route commonly directs traffic towards an upstream router or internet gateway.

An incorrect default route can prevent access to external networks or send traffic along an unintended path.

How routers select routes

Three important concepts are:

Longest prefix match: The router generally selects the route with the most specific matching destination prefix.

Administrative distance: Where a routing device has competing routes to the same destination from different sources, administrative distance helps it assess which source is preferred. The precise rules depend on the routing platform.

Metric: A routing protocol or routing process may use a metric to compare paths. The meaning and calculation of the metric depend on the protocol.

These concepts serve different purposes. Administrative distance helps compare route sources, metrics compare routes according to the relevant routing protocol or process, and longest prefix match selects the most specific matching destination prefix.

Troubleshooting tools

• ping tests basic IP reachability.
• traceroute or tracert helps identify the path packets take towards a destination.
• Platform-specific show commands display routing tables, interfaces and routing information.

Example: A server can reach devices on its local subnet but cannot reach an external network. Checking the routing table reveals an incorrect default route. Correcting the route restores the expected path.

Exam tip: Understand the difference between a default route, administrative distance, route metrics and longest prefix match.

6. Address Pool Considerations

Dynamic Host Configuration Protocol (DHCP) automatically assigns IP configuration to client devices.

A DHCP scope or address pool defines the addresses available for assignment within a particular network.

Address pool exhaustion

Address pool exhaustion occurs when the DHCP server has no available addresses left to lease to additional clients.

Possible symptoms include devices failing to obtain a usable IP address or being unable to communicate normally on the network.

Potential causes include:

• Too many devices using the available pool.
• Leases remaining active for longer than necessary.
• A pool that is too small for the number of clients.
• Unexpected devices connecting to the network.
• DHCP scope or exclusion misconfiguration.

Troubleshooting steps

1. Check the client's IP configuration.
2. Inspect DHCP scope utilisation and available addresses.
3. Review active leases and lease durations.
4. Investigate unexpected clients or reservations.
5. Check scope size and exclusion settings.
6. Expand or redesign the pool where appropriate.
7. Consider additional subnets or scopes if the network design supports them.

The course notes also mention reducing the number of connected devices when appropriate.

Private IPv4 addresses can be reused across separate private networks, but a single subnet still has a finite number of usable addresses. IPv6 provides a much larger address space, although correct addressing and DHCP or other address-configuration mechanisms remain important.

Exam tip: If multiple new devices cannot obtain valid network configuration, investigate DHCP availability and scope exhaustion before assuming that all the devices have failed.

7. Default Gateway Issues

A default gateway is the device or routing interface that forwards traffic from a local network towards destinations outside that network when no more specific route applies.

It is usually a router or Layer 3 device.

Common symptoms

• Local devices can communicate, but external networks are unreachable.
• Internet access fails even though the device has a valid local IP address.
• Traffic cannot reach a different subnet.
• Several devices in the same network experience similar external-connectivity problems.

Common causes

• Incorrect or missing default gateway configuration.
• Gateway device failure.
• Incorrect client IP settings.
• Physical connectivity problems.
• Router or interface configuration errors.
• Driver or operating-system networking problems.

Troubleshooting process

1. Check the client's IP address, subnet mask and default gateway.
2. Verify that the gateway address belongs to the expected local subnet.
3. Check the device's physical or wireless connection.
4. Test connectivity to the gateway.
5. Inspect the router's interface and routing status.
6. Compare the configuration with a working device.
7. Apply an authorised corrective action and test again.

If a client can communicate with local devices but cannot reach other networks, the gateway is an important point to investigate.

The course also mentions resetting TCP/IP, updating drivers or firmware, disabling interfering software and using a safe-boot approach to isolate software-related problems. These should be considered when the evidence points towards a client configuration or software issue, rather than applied indiscriminately.

Exam tip: A default gateway is needed to reach destinations outside the local IP subnet. It is not normally required for communication between devices in the same subnet.

8. IP Addressing Conflicts

An IP addressing conflict occurs when two devices are assigned the same IP address within the same network where that address must be unique.

Duplicate assignments can result in intermittent connectivity, failed communication or operating-system warnings.

Common causes

• Two devices manually configured with the same static IP address.
• DHCP scope misconfiguration.
• A static address falling inside the DHCP allocation range without a suitable reservation or exclusion.
• Incorrect documentation or coordination between administrators.

Troubleshooting steps

1. Check the affected device's IP configuration.
2. Review DHCP leases and reservations.
3. Compare the configuration with the IP address management records.
4. Identify whether a static assignment overlaps with the DHCP pool.
5. Use appropriate network tools to gather evidence about the conflicting address.
6. Correct the conflicting assignment.
7. Renew the DHCP lease where appropriate.
8. Verify that connectivity has returned.

Pinging an address may provide useful evidence, but it does not conclusively identify a duplicate IP address in every situation. Check DHCP records, device configurations and relevant network logs as well.

Prevention

• Maintain accurate IP address documentation.
• Exclude static addresses from dynamic DHCP allocation where appropriate.
• Use DHCP reservations when suitable for the network design.
• Coordinate manual IP assignments between administrators.
• Review scopes and configuration changes regularly.

Exam tip: A duplicate IP address is different from an incorrect subnet mask. A duplicate means the same address has been assigned to multiple devices; a mask error means a device may interpret network boundaries incorrectly.

9. Incorrect Subnet Mask

A subnet mask identifies which bits of an IPv4 address represent the network portion and which represent the host portion.

For example:

• IP address: 192.168.1.25
• Subnet mask: 255.255.255.0
• CIDR notation: /24
• Network address: 192.168.1.0

With a /24 mask, the first 24 bits identify the network and the remaining 8 bits identify the host portion.

How an incorrect mask causes problems

Devices use their IP address and subnet mask to determine whether a destination is local or must be reached through a router.

If a device has the wrong mask, it may make an incorrect decision about where a destination resides.

This can prevent communication even when devices are connected to the same switch. Physical connection alone does not guarantee that their IP configurations are compatible.

Troubleshooting steps

1. Inspect the device's IP address and subnet mask.
2. Compare them with network documentation.
3. Check the settings on a correctly configured device in the same subnet.
4. Confirm the intended subnet and network boundary.
5. Correct the mask through the appropriate configuration mechanism.
6. Retest local and remote connectivity.

DHCP can reduce client-side configuration errors by supplying the correct IP address, mask, gateway and other settings. However, incorrect DHCP scope configuration can distribute incorrect settings to many devices.

Exam tip: If two devices share the same physical switch but cannot communicate, check their IP addresses and subnet masks as well as VLAN membership.

10. Troubleshooting Tools and Their Uses

Tool or method	Main purpose
Cable tester	Checks cable wiring and physical continuity, depending on the tester
Interface counters	Identifies errors, drops and other interface statistics
Device logs	Reveals interface, switching, power or configuration events
ping	Tests IP reachability and response time
traceroute / tracert	Helps identify the route towards a destination
Routing table commands	Displays routes and next-hop information
DHCP lease inspection	Helps identify scope exhaustion and assignment problems
IP configuration tools	Shows the device's address, subnet mask and gateway

No single tool proves every cause. Combine test results with user reports, configuration records and the observed symptoms.

11. Integrated Troubleshooting Scenario

Scenario: Several employees can access local shared resources but cannot reach external websites. One employee also reports intermittent connectivity.

Step 1: Identify the scope

Determine whether the external-connectivity problem affects one user, several users or the entire subnet. Check whether internal resources remain accessible.

Step 2: Check physical connectivity

Inspect relevant cables, switch ports and interface status. Review interface counters for errors or dropped packets.

Step 3: Validate IP configuration

Check IP addresses, subnet masks and default gateways. Review DHCP leases if devices appear to have incorrect or missing configuration.

Step 4: Investigate routing

If local connectivity works, inspect the default gateway and routing table. Use ping and traceroute to gather further evidence.

Step 5: Check switching configuration

If only a subset of devices is affected, review VLAN assignments, port configuration and applicable ACLs.

Step 6: Apply the appropriate fix

Use the evidence to identify the cause. Assess the impact before changing shared infrastructure, and escalate if the required action is outside your authority.

Step 7: Verify and document

Test local and external connectivity, confirm that the intermittent problem has stopped, check that other services still work and document the resolution.

This scenario illustrates why effective troubleshooting considers physical connections, interfaces, switching, addressing and routing rather than assuming every connectivity problem has the same cause.

12. Final Exam Revision Checklist

Before taking the CompTIA Network+ N10-009 test on this topic, ensure that you can explain:

• Common cable faults, cable selection and electromagnetic interference.
• Interface counters, including CRC errors, runts, giants and overruns.
• Administrative interface states and physical link problems.
• PoE requirements, port settings and switch power budgets.
• Switch faults, bottlenecks, VLAN mismatches, STP loops and ACL errors.
• The purpose of a default route and how routers select paths.
• Administrative distance, metrics and longest prefix match.
• DHCP address pool exhaustion and possible remedies.
• The purpose of a default gateway and how to troubleshoot it.
• The causes and resolution of duplicate IP addresses.
• How an incorrect subnet mask affects local and remote communication.
• How to use ping, traceroute, interface statistics, logs and configuration tools.

Quick memory guide

Physical layer: Cable, connector, interference and link status.

Interface and hardware: Counters, port configuration, drivers, transceivers and PoE.

Switching: VLANs, STP, ACLs, ports and bottlenecks.

Routing: Route tables, default routes, metrics and administrative distance.

IP services: DHCP pools, default gateways, IP conflicts and subnet masks.

Final principle: Follow a logical troubleshooting process, test your theories, assess the impact of changes, verify the result and document what you learned.

These notes are based on the course material provided, with practical examples added to support revision.