Troubleshooting Network & Printer Issues

A+ Core 1 220-1201 · Hardware and Network Troubleshooting

By Abu Anns · Last updated 20 November 2026Exam version: 220-1201 (V15, current)

This guide completes the troubleshooting domain with the two remaining objectives: network issues and printer issues. Both are heavily scenario-based on the exam, and both reward the same approach — match the symptom to the most likely cause, and pick the simplest, least disruptive fix first.

Network issues

Intermittent wireless connectivity — Wi-Fi that drops and reconnects — is usually caused by interference, a weak signal at the edge of coverage, or channel congestion. The fix is to check signal strength, move closer to the access point or add one, and check for channel overlap. Slow network speeds can come from a congested link, a duplex mismatch, a failing cable, or a device negotiating at a lower speed than it should (a gigabit NIC connecting at 100 Mbps because of a damaged cable is a classic). Limited connectivity (the system tray warning) usually means the device has a link but no valid IP configuration — most often a DHCP failure, leaving the host with an APIPA address.

Jitter is variation in the delay of packets, and it is the enemy of real-time applications: a video call with high jitter stutters even if average speed is fine. Poor VoIP quality is usually caused by jitter, latency, or packet loss on the network path, or by insufficient bandwidth. Port flapping is a switch port that rapidly goes up and down, usually caused by a faulty cable, a damaged port, or a duplex/speed mismatch. High latency is delay on the network path — normal on satellite links, but a sign of congestion or a failing device on a LAN. External interference affects wireless networks: microwaves, Bluetooth devices, neighbouring Wi-Fi networks, and even thick walls and metal shelving can degrade a wireless signal. Authentication failures on a network mean the device cannot prove its identity — wrong Wi-Fi password, expired certificate, or an account problem. Intermittent internet connectivity that affects the whole site usually points to the ISP link or the edge router; if it affects one device, the problem is local to that device.

The exam also expects you to know which command-line tools help diagnose these issues, even though the tools themselves are covered in Core 2: ping tests basic connectivity, ipconfig shows the device's IP configuration, tracert shows the path packets take, and nslookup tests DNS resolution. On Core 1 the focus is on recognizing the symptom and its likely cause rather than running the commands.

Printer issues

Printer symptoms map to causes by printer type, and the exam tests this mapping directly. Lines down the printed pages on a laser printer usually mean a scratched drum or a damaged fuser roller; on an inkjet they can mean a clogged printhead. Garbled print — random characters instead of the document — almost always means the wrong printer driver is installed. Paper jams are caused by worn rollers, damaged paper, overfilled trays, or debris in the paper path; always pull jammed paper in the direction of the paper path to avoid tearing it. Faded prints on a laser mean low toner or a failing fuser; on an inkjet, low ink or clogged nozzles. Paper not feeding is usually worn or dirty pickup rollers. Multipage misfeed (several sheets pulled at once) is caused by worn separation pads or humid, stuck-together paper. Multiple prints pending in queue usually means one stuck job is blocking the rest — clear the queue and restart the print spooler.

Speckling on printed pages (random dots) on a laser printer can mean toner leaking from a damaged cartridge or a dirty drum. Double or echo images (a faint repeat of the image further down the page) on a laser printer mean the fuser is not heating properly and toner is not fully bonding — or a damaged drum is retaining the image. A grinding noise means something mechanical is failing — gears, rollers, or a foreign object in the paper path. Finishing issues affect multifunction devices with staplers or hole punches: staple jams and hole punch blockages are usually caused by the wrong staple size or overfilled punch waste. Incorrect page orientation (landscape instead of portrait) is a settings problem — check the driver and application settings. A tray not recognized usually means the tray is not seated properly or the paper size guides are set wrong. Connectivity issues (the printer is offline or not found) can be a cable, a network, or a driver problem — check the physical connection first, then the queue and driver. A frozen print queue is fixed by clearing the queue and restarting the print spooler service.

A troubleshooting habit worth building

For both networks and printers, the exam rewards the same discipline: check the physical layer first (cables, power, paper, toner), then the configuration (drivers, settings, IP address), then the deeper causes (failing hardware, interference, firmware). The "best first step" in a scenario question is almost always the simplest check that could explain the symptom — not the most thorough or most expensive one. And when a question describes a symptom you have not seen before, work backwards from the component: which part of the system produces this symptom, and what is the simplest thing that could make that part fail?

Putting the symptoms together

Real problems rarely present a single clean symptom, and the exam's harder questions combine two or three clues. A user who reports slow printing, a printer that disappears from the network, and a blinking network light is probably describing one failing network cable, not three separate faults. A wireless network that is slow in one room, fine in the next, and drops entirely when the microwave runs is an interference and coverage problem, not a faulty access point. The skill the exam tests is pattern matching: hold the whole symptom list in mind, and ask which single cause explains all of it. When two causes could both fit, choose the simpler and more common one — CompTIA's scenarios are written from real support tickets, and in real support the common cause is common. Finally, remember to verify the fix: after replacing a cable, reseating a component, or changing a setting, confirm the symptom is actually gone before closing the ticket, and note what you did so the next technician does not repeat your work.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A user's laptop shows "limited connectivity" on Wi-Fi. The laptop can see the network but cannot reach the internet or any local server. Other devices on the same network work fine. What is the most likely cause?

Report an error

Q2.Users on VoIP calls report choppy, stuttering audio, but file downloads are fast and web browsing works fine. Which network condition is the most likely cause?

Report an error

Q3.A switch port's status light keeps rapidly turning on and off, and the connected computer's network connection drops every few seconds. What is this symptom called, and what is the most likely cause?

Report an error

Q4.A laser printer outputs pages covered in random symbols and strange characters instead of the document. The printer worked correctly yesterday. What is the most likely cause?

Report an error

Q5.A laser printer produces pages with a faint repeat of the text appearing further down the same page (a ghost or echo image). What is the most likely cause?

Report an error

Q6.A printer keeps pulling several sheets of paper at once, causing frequent misfeeds. What is the most likely cause?

Report an error

Q7.Several print jobs are stuck in the queue and no new jobs will print. The printer itself is powered on and shows no error. What should the technician do first?

Report an error

Q8.A user's Wi-Fi connection drops every time the office microwave is used. What is the most likely cause?

Report an error