Hi! If your printer prints from your phone but won’t print from your laptop, that’s actually a useful clue: the printer can produce output, so we’re usually dealing with a connection path or laptop-side issue (queue, driver, port, permissions), not a dead printer.

To narrow this down safely (no resets yet), tell me a few details — any order is fine:
1) Are you on Windows or macOS on the laptop?
2) How does the phone print — AirPrint, HP Smart, Brother Mobile Connect, Epson iPrint, or something similar?
3) What happens on the laptop: does it say Offline, does the job get stuck in the print queue, or does it “print” instantly with nothing coming out?

Got it — “jobs sit in the queue” points to the laptop’s printing pipeline (app → Windows print system → driver/port → printer). Since the iPhone can print, we can focus on what’s different about the laptop path.

Quick split test (just observation):
• When you send a job from Windows, does the printer display Receiving/Processing anything, or is there no reaction at the printer at all?
• In the Windows queue, does the job status say Printing, Error, Paused, or Offline?

Also: are your phone and laptop on the same Wi-Fi network name (same SSID), or do you have two networks like “Home-2.4G” and “Home-5G”?

That “no reaction at the printer” + mixed 2.4/5G setup is a classic scenario for “it works from one device but not the other.” It doesn’t always mean the networks can’t talk — but it’s worth checking because printers often connect to 2.4 GHz while phones/laptops bounce between bands.

One safe check that reveals a lot: on the printer’s screen (or its network report), do you see the printer connected to Home-2.4G or Home-5G? And on your Windows laptop, which one are you connected to right now?

Also, are you using a VPN on the laptop for school/work? VPNs can make a printer look “present” but block the local network route needed for printing.

That absolutely can matter — and the good news is we can diagnose it without “nuke and reinstall.” Two common culprits in your situation are:

1) Network segmentation / band isolation: some routers treat 2.4 and 5 GHz clients as separate zones (or have a “guest”/isolation setting). Your phone might still reach the printer because it switches bands, while the laptop stays on 5 GHz and can’t route to the printer’s IP.

2) VPN / security software: when VPN is on, Windows may send printer traffic into the tunnel or block local discovery/printing ports. It can look like it’s printing, but nothing ever reaches the printer.

Quick questions (again, no changes required yet):
• When the VPN is off, does the print behavior change at all (faster error vs hanging)?
• Is the printer added as a network printer by name (WSD) or by a specific IP address? If you’re not sure, that’s okay — I’ll ask a different way next.

Helpful — faster failure often means Windows can’t reach the printer endpoint (IP/port) rather than “a document problem.”

Let’s isolate reachability without messing with drivers:

Safe check A: confirm the laptop can see the printer’s address
Many printers show an IP address on their network status page (something like 192.168.x.x). If you can find that number, it tells us whether Windows is aiming at the right destination. If the router gives the printer a new IP occasionally, the laptop may be trying to print to an old one.

Safe check B: compare “same network” in plain terms
Just for a minute, can you connect the laptop to the same Wi-Fi name as the printer (the 2.4 SSID) and see whether the printer stays “Ready” or flips to “Offline”? You don’t have to print yet — I’m watching for the status change clue.

What’s the printer brand (HP, Canon, Epson, Brother)?

Nice — that suggests the band split was at least part of the story (status stability improved). If it still errors, the next layer is usually one of these:

• The laptop is printing to the wrong port type (WSD can be flaky on some networks; IP/TCP can be more stable).
• The Windows print queue / spooler is jammed (especially if older stuck jobs keep retrying).
• A security setting blocks the print traffic even on the same SSID (less common, but it happens).

Two questions to keep this grounded:
1) When you open the print queue, do you see old jobs sitting there from earlier attempts, or is it only the new job you just sent?
2) Does printing fail from every app (Notepad, a test page) or mainly from PDFs/browsers? Different answer = different cause.

If a Windows test page fails, that’s a strong hint this isn’t a “PDF setting” issue — it’s the Windows-to-printer path itself (queue/driver/port). And the older stuck jobs matter because they can keep the queue in a bad state.

I’m going to keep this in “diagnostic mode” rather than giving a huge list of changes. Here’s what I’d record before touching anything major:

• Printer status in Windows: Ready vs Offline vs Error.
• Where the job fails: does it stay “Spooling,” switch to “Printing,” then error, or disappear?
• Whether the printer’s IP changes: if the printer screen shows an IP, check if it’s the same tomorrow (DHCP changes can break laptop printing while phone apps re-discover automatically).

One more angle: do you have multiple printer entries on the laptop (like “HP… (Copy 1)” or an old one)? If Windows is sending to the wrong default printer instance, it can look like it’s printing but never reaches the device.

That “two entries” detail is huge — it often means Windows has both a WSD/discovery-based printer and a more direct driver instance. Phones typically “discover and adapt” on their own, which is why they keep working while the laptop gets stuck with a stale route.

At this point, the safest next step is not “random reinstall,” it’s to identify which entry is actually targeting the printer that’s currently on your network (same IP / same path). If you pick the wrong one as default, jobs can spool forever or error quickly.

Quick check: when you print, does Windows show any hint like “printing to port…” in printer properties? If not, no worries — the key takeaway is that the laptop likely has a driver/port mismatch or a stuck queue, while the phone is using a different protocol (often AirPrint-like or an app’s direct method).

Before doing any “fix,” clear information helps: what is the printer IP shown on the printer screen, and does either Windows printer entry show that same address anywhere?

Exactly — based on your symptoms (phone prints reliably, Windows test page fails, two printer entries, queue errors), the printer hardware is probably fine. The most likely causes live on the laptop side: wrong printer instance, stale WSD route, print queue/spooler stuck, or a network path mismatch that the phone app works around automatically.

If you grab the printer’s IP and we match it to the Windows printer entry that’s actually targeting that address, you’ll usually see the whole situation become consistent (either it works, or the error becomes specific enough to act on). The goal is to identify the failing layer before making big changes like driver reinstall or router resets.