Windows cannot connect to the printer, what to do
This message is a heading, not a diagnosis. Underneath it sits a code, 0x0000011b, 0x00000002, 0x00000709, 0x00000771 and others, and the code decides the fix. The failures share a shape though: one PC (the host) shares the printer, another (the client) connects to it, and the break can be at the host, the client, the network path, or the trust between them. Work the shared checks first, then follow the code.
The fix, in order
- Note the exact code in the message. Write down the 0x code before closing the dialog. It separates authentication refusals from missing drivers from stale registrations, and each has a different ladder on this site.
- Confirm the host PC is on, awake, and reachable. A shared printer dies with its host: if the host is asleep, off, or renamed, every client gets this message. From the client, type \\HOSTNAME in Explorer's address bar; if the host's shares do not appear, fix reachability (network, firewall, discovery) before touching printers.
- Restart the Print Spooler on both machines. Host and client both run the service, and a stalled spooler at either end presents as a connection failure at the other.
- Verify the share and its permissions. On the host, Printer properties, Sharing: the printer is shared, and the Security tab includes the people who need to print. A share recreated by an update or a driver reinstall sometimes loses its audience.
- Install the driver locally, then connect. Download the driver for the exact model from the manufacturer's site and install it on the client first. Connecting afterwards skips the fragile driver download from the host, the step where the 0x00000002 variant of this message is born.
- Add the printer by IP address. For network printers, bypass sharing entirely: Add device, The printer that I want is not listed, Add a printer using an IP address, and enter the printer's own address. If that prints, the printer and network are fine and the sharing layer was the fault.
If it still happens
When this message appears for a whole office at once, look at the host and at recent updates before individual PCs. The 2021 PrintNightmare servicing changes made patch-level mismatches between host and clients the classic mass cause, cured by bringing every machine current rather than by per-PC repairs.
Common questions
Why did the shared printer stop working overnight? The usual overnight events are the host PC sleeping, rebooting for updates, or receiving an update the clients have not yet matched. The message appears at the client, but the change happened at the host or in the update state.
Do I need the host PC's password to connect? With password-protected sharing on, yes: Windows expects credentials valid on the host. On home networks the simpler durable setup is a printer with its own network connection, added by IP, which removes the host from the path entirely.
Related errors