Printer Prints From Your Phone but Not Your Computer? That Narrows It Right Down

This is one of the most quietly frustrating printer problems there is. You send a document from your laptop and nothing happens — offline, error, or just silence. Then you pull out your phone, tap Print out of habit, and the page slides out immediately. The printer is obviously working. The Wi-Fi is obviously working. So why is the computer the odd one out?

Here's the thing most advice on this misses: your phone printing isn't a strange coincidence to work around. It's the single most useful diagnostic result you could have gotten, and it eliminates most of the usual suspects in one go. Once you understand why, the list of things it can still be is short — and only one of them is the sort of thing people normally go looking for.

Why the phone test tells you so much

Your phone and your computer print in fundamentally different ways, and that difference is the whole answer. When you print from an iPhone or iPad, you're using AirPrint; from an Android phone, it's Mopria or the built-in Android print service. Both are deliberately driverless — Apple's own developer documentation describes AirPrint as printing "without the need to download or install drivers," and the Mopria Alliance describes its system as enabling direct device-to-printer communication. Both are built on IPP, the Internet Printing Protocol, and the phone finds the printer using local network discovery (Bonjour on Apple's side) and then sends the job straight at it.

What that means in practice is that your phone never touches any of the machinery that normally breaks on a computer. No printer driver. No Windows print spooler. No print queue on the PC. No "default printer" setting. No port entry saved months ago. The phone is essentially a stranger walking up to the printer and handing it a document.

So when the phone prints, you have just proven four things at once: the printer is powered on and healthy, it has paper and ink or toner, it is properly joined to your Wi-Fi, and its own internal job handling works fine. Every one of those is something people spend an afternoon on. You can cross all four off. Whatever is wrong lives strictly between your computer and the printer — either the path between them, or the print setup on that one machine.

First: are the two devices actually on the same network?

This sounds too obvious to be the answer, and it is the answer more often than anything else on this page — because modern homes quietly run several networks at once, and it isn't always visible which one you're on.

Start by reading the network name on the computer and comparing it, character for character, with the one the printer is on. Most printers with a screen will show you their network under a Wireless or Network Settings menu, and nearly every printer can print a network configuration page from its own control panel, which lists the network name and its IP address. It's worth printing that page — your printer is currently very good at printing, so use it.

Then look for the three ways a household ends up split. The first is a guest network: a laptop set up while guests were over, or a smart-TV network, can be sitting on "MyWiFi-Guest" while the printer is on "MyWiFi". The second is split bands — some routers publish 2.4GHz and 5GHz as two separately named networks, and many printers can only join the 2.4GHz one. (If your printer is a 2.4GHz-only model fighting a dual-band router, our guide on wireless printers that keep dropping off the Wi-Fi covers that case properly.) The third is a second router or a range extender running in router mode, which creates a whole separate network behind the first one, so a device on it can reach the internet but not the printer sitting on the other side.

There's a technical reason that last one is fatal rather than merely awkward. The discovery traffic that lets devices find printers on a local network is deliberately short-range: as Cisco's own documentation explains, multicast DNS uses a link-local multicast address with its time-to-live set to 1, so routers won't forward it — the printer and the device looking for it have to be on the same segment of the network. That's why your computer can browse the whole internet and still not see a printer twelve feet away.

The router setting that walls devices off from each other

If both devices genuinely are on the same network name and the computer still can't reach the printer, the next thing to check is a setting almost nobody has heard of: AP isolation, also sold as client isolation, guest isolation, or "wireless isolation" depending on the brand.

TP-Link's own explanation of it is blunt: with AP isolation on, "each device can still access the Internet, but it can't see, ping, or connect to any other device sharing that network." They list what stops working as a result, and printers are top of the list — "printer access over the local network stops working," along with file sharing and some smart-home devices that rely on local discovery. It is a genuinely good security feature, which is exactly why it exists: it's meant for guest networks, cafés, and short-term rentals, where you don't want visitors poking at each other's laptops.

The trouble is where it gets switched on. It is commonly enabled by default on the guest network of a consumer router, which is why a computer that drifted onto the guest SSID hits a wall that a phone on the main network never sees. It's also standard on the Wi-Fi in apartment buildings, condos, and offices where the building or landlord provides the internet — and in that situation the setting isn't yours to change, which matters, because you can spend a week reinstalling drivers on a problem that no amount of driver work will fix.

On your own router, look in the wireless or guest-network settings for anything named isolation. Turn it off for your main network if it's on, and move both the computer and the printer onto that main network rather than the guest one. If the Wi-Fi belongs to a building or an employer, the practical fix is usually to connect the printer to the computer directly with a USB cable, or to use the printer's own Wi-Fi Direct feature, which lets a device connect straight to the printer without going through the shared network at all.

If the computer is plugged in with a cable

A desktop on Ethernet with the printer on Wi-Fi is a very common version of this problem, and it splits two ways. On an ordinary home router, wired and wireless are the same network, and everything works — so if that's your setup, this isn't your cause. But if the wired port traces back to a different box than the Wi-Fi comes from — an older router being reused as a switch but still handing out addresses, a powerline adapter, an office setup with separate wired and wireless networks — the two devices can end up in different address ranges, with the same result as the guest-network case above.

The quick way to tell is to compare addresses. Look at the IP address on the printer's network configuration page and the one on the computer: on Windows, Settings > Network & internet > Wi-Fi or Ethernet > Properties will show it. If the printer is 192.168.1.40 and the computer is 192.168.1.55, they're neighbours and this isn't the problem. If the printer is 192.168.1.40 and the computer is 192.168.0.55 or 10.0.0.55, they are on different networks and cannot find each other, no matter what the network name says. An address starting 169.254 means the device never got an address at all.

The Windows side: which port is your PC actually aiming at?

If both devices are demonstrably on the same network and can reach each other, the fault is in the print setup on that one computer — and the piece that fails most often is the least visible one: the port, which is the saved instruction telling Windows where to send the job.

There are two kinds on a home network. A Standard TCP/IP port is pinned to a specific address — Brother's setup documentation has you type in the printer's IP address or print server name when you create one — which is fast and stable right up until the printer's address changes, at which point Windows is cheerfully printing to an address where nothing lives. That happens more than you'd think: routers hand out addresses on a lease, and a printer that was off for a week, or a router that was rebooted, can come back on a different number. A WSD port, which is what Windows and many printer installers create automatically, works the other way — it finds the printer by discovery each time, which means it survives an address change but depends on exactly the discovery traffic that guest networks, isolation, and separate subnets block. HP's own support documentation for network printers showing "Offline" or "Print error" walks you through replacing the automatically-created WSD port with a Standard TCP/IP port for this reason.

To look at it: Settings > Bluetooth & devices > Printers & scanners, click your printer, choose Printer properties, and open the Ports tab. The ticked port tells you which kind you have. If it's a Standard TCP/IP port, compare the address shown against the address on the printer's configuration page — if they don't match, that single mismatch is your entire problem. You can either correct the address on the port, or remove the printer completely (Settings > Bluetooth & devices > Printers & scanners > your printer > Remove) and add it back so Windows rediscovers it where it actually lives.

If the printer's address keeps wandering and this keeps happening, fix it once at the router by giving the printer a permanent reserved address — a DHCP reservation. That's the durable answer, and our guide on wireless printers that keep dropping off the Wi-Fi walks through setting one up. If all this started right after you changed routers or internet providers, our guide on getting a printer back on a new Wi-Fi network covers that specific sequence.

If Windows thinks your home network is "Public"

Windows assigns every network a profile, and the difference matters here. Microsoft's guidance on network printing is direct about it: to share a printer across a trusted network, "the network needs to be set as Private," with both Network discovery and File and printer sharing switched on. On a Public profile — which is what Windows tends to choose when it first meets a network, and what it can revert to after some updates — the PC deliberately keeps to itself and local discovery is shut down.

This is the decisive cause when the printer isn't on the network by itself but is plugged into another computer and shared from there, because that kind of printing depends entirely on the sharing features a Public profile turns off. It also quietly breaks discovery-based setup on a directly networked printer. Check it at Settings > Network & internet > Wi-Fi > your network > and set the network profile type to Private, then look under Advanced network settings > Advanced sharing settings and make sure Network discovery and File and printer sharing are on for the private profile. Only do this on your own home or office network — the Public setting is doing its job on café and airport Wi-Fi.

Only now, the ordinary print problems

Everything above is about the path between the computer and the printer, because that's what the phone test points at and it's what nearly every other page on this topic skips straight past. But once you've confirmed the two are on the same network and the computer is pointed at the right address, the classic Windows print faults are back on the table — and now you can trust that fixing them will actually help.

The short list: a stuck job at the front of the queue holding everything behind it, the "Use Printer Offline" switch that Windows sometimes flips on by itself and never flips back, the wrong default printer sending your pages silently to Microsoft Print to PDF, and a driver knocked loose by an update. Our guide on a printer that says connected but won't print covers all four with the exact steps. If jobs won't leave the queue at all, or you get "Print Spooler service is not running," that's a separate fault with its own fix — our print spooler guide handles it.

The order to work through it

Put together, this is a five-minute sequence rather than an afternoon. Print the printer's network configuration page from its own control panel — you already know it can print. Compare the network name on that page with the one your computer is on, and get them onto the same one, main network rather than guest. Compare the two IP addresses and confirm the first three numbers match. If they match and it still fails, look for AP or client isolation in the router's wireless settings, and set the Windows network profile to Private. Then check the printer's port on the PC against the address on that configuration page, and remove and re-add the printer if they disagree.

Reinstalling the driver — which is where most people start — belongs near the end of that list, not the beginning. A phone that prints has already told you the printer is fine, and a driver reinstall cannot fix a network the computer isn't on.

When to hand it over

Most of these come apart quickly once you know that the phone printing was evidence rather than an insult. It's worth getting help when the Wi-Fi belongs to a building, an HOA, or an employer and you can't get at the isolation setting; when there are two routers in the house and nobody is sure which one is really in charge; when the printer is shared off another computer and half the machines in the office can print and half can't; or when the address keeps moving no matter how many times you re-add the printer.

We sort out printers, home and small-business networks, and the awkward overlap between them across Southern California and the Coachella Valley — in person or by remote support. We don't sell printers or ink, so if a machine has genuinely reached the end of the road we'll say so, and if the real problem is the network rather than the printer, we'll fix the network instead of selling you a new printer to plug into it.