Epson XP-2205 connected but not printing: what to check

Place a page face down at the marked scanner-glass corner, close the cover and load A4 plain paper. Press a copy button. If a copy prints, the scanner and print path can operate independently of the computer; investigate the connection and print queue next.

If it cannot copy, inspect the ink and paper lamps and the computer status message. Follow the relevant cartridge or jam guide. A failed copy is a reason to identify the printer-side error, not proof that the printer must be replaced.

For router Wi-Fi, the upper wireless-network lamp should be steady. Load paper and press Network information once for the connection report. For fuller settings, hold it for at least five seconds for the network status sheet. Compare the reported network name with the computer’s network.

Being connected to a guest network or a separate isolated network can prevent discovery even when internet access works. If the router name or password changed, reconfigure using the linked Wi-Fi guide. Do not erase a functioning network configuration simply because a print job failed.

In Windows, search for Printers & scanners, open your XP-2200 Series printer and open its print queue. Confirm that the job was sent to this device and the intended network connection, not an old duplicate or USB-only entry.

Cancel the unwanted or stuck job; cancelling removes that queued work and you will need to send it again. If the queue is paused or offline, clear that state using the controls available in your Windows version. Restart the printer with Power after outstanding jobs are addressed, then send one small test document.

If the printer is absent or the wrong driver is selected, follow the Windows setup guide to install the exact Epson software. Epson also provides Printer Connection Checker with supported Windows software; follow its reported diagnosis if installed.

If the same failure remains, record the exact message, whether local copying works and the network-report result for Epson support. These symptoms help distinguish software, connectivity and hardware problems; the source’s quick conclusion of a serious fault is not warranted by a failed queue retry alone.