Network Printer Works on One PC But Not Others – Fix

EP
Erropedia Team
📅 June 16, 2026 📅 Updated Sep 12, 2026 👁 25 views Hardware – Printers Intermediate
Printer connected via network prints from one computer but errors out on others. Usually a driver or port mismatch.

You’ve got that one PC where the network printer chugs along fine. Everyone else gets an error like “Printer not responding” or “Windows cannot connect to the printer.” Maybe the job sits in the queue and never moves, or it spools for a minute then disappears.

I’ve seen this a hundred times. Most common trigger: someone installs the printer on one machine with a direct IP port, then tries to share it over the network instead of adding it properly on the other PCs. Or the driver version on the other machines doesn't match the printer's PDL (page description language).

The root cause is almost always a mismatch between the driver installed on the host PC and what Windows pulls when the other machines try to connect. Or the port is pointing to a stale IP.

What’s actually happening

Network printers talk to your computers over TCP/IP. Windows uses a printer driver to translate what you see on screen into commands the printer understands. When you install the printer on the first PC, you pick a driver that works – maybe PCL6 or PostScript. That machine prints fine. But when another PC tries to use that same printer, Windows might grab a generic driver or a wrong PDL version from the print server (or from the printer itself via WSD). The result? The printer rejects the job, or the spooler chokes.

Another common culprit: the first PC is using a WSD (Web Services for Devices) port, which is flaky. Other machines can't resolve the printer's device address consistently. Or the printer’s IP changed – maybe DHCP renewed it – and the other PCs still point to the old IP.

Step-by-step fix

  1. Check the printer’s IP address. On the printer’s control panel, go to Network Settings > TCP/IP and write down the IP. Or print a network configuration page. Do not rely on what Windows shows.
  2. On the working PC, open Devices and Printers. Right-click the printer, select Printer Properties, go to the Ports tab. Note which port is selected – it should say “Standard TCP/IP Port” with an IP address. If it says WSD or something vague, that’s your problem.
  3. Delete the printer from all non-working PCs. Go to Settings > Devices > Printers & scanners, find the printer, click Remove device.
  4. Install the printer on each non-working PC using a direct TCP/IP port. Click “Add a printer” and choose “The printer that I want isn’t listed”. Select “Add a printer using an IP address or hostname”. Enter the printer’s IP. Uncheck “Query the printer and automatically select the driver” – this is critical. Windows will try to be clever and pull the wrong driver. Instead, pick the correct driver from the list or click “Have Disk” if you have a specific driver file. For HP printers, use the HP Universal Print Driver (PCL6) – it works across most models. For Brother, use the full driver package from their site.
  5. Once installed, print a test page. If it works, repeat on the other PCs. If it fails, check that the printer’s IP hasn’t changed – assign a static IP in the printer’s network settings to prevent DHCP changes.
  6. If you’re sharing the printer from a PC (not using a network printer directly), stop doing that. Network printers are designed to be added directly. Sharing adds a layer of Windows dependencies. Remove the share and add the printer directly on each machine.

What to check if it still fails

If you’ve done all the above and still get errors, look at these:

  • Firewall blocking ports. Some printers use port 9100 for raw printing. Make sure Windows Firewall (or third-party AV) isn’t blocking it. Temporarily disable the firewall on one PC to test – if it works, create an inbound rule for TCP port 9100.
  • Driver mismatch between 32-bit and 64-bit. If one PC is 32-bit Windows and another is 64-bit, you need separate drivers. The 64-bit driver won’t work on the 32-bit machine even if Windows tries.
  • Spooler corruption. Run this as admin on the problem PC: net stop spooler, then delete everything in C:\Windows\System32\spool\PRINTERS, then net start spooler. Reinstall the printer.
  • Network discovery and printer sharing settings. All PCs should be on the same network profile (Private, not Public). Go to Control Panel > Network and Sharing Center > Advanced sharing settings and turn on network discovery and file/print sharing for Private networks.
  • Firmware update on the printer. Had a client last month where an old Brother MFC’s firmware had a bug that caused PCL6 jobs to fail on non-Windows 10 machines. Updated firmware fixed it.

If none of that works, the printer might be on its last legs. But 9 times out of 10, it’s just a bad driver or a WSD port. Switch to a direct TCP/IP port with a proper driver, and you’re golden.

Related Errors in Hardware – Printers
0X40262437 0x40262437 on print server: deferred lead-link adapter fix Print Preview Lies? Fix When Printed Output Differs Printer Offline in Windows 11? Fix the Ghost Port Printer won't print envelopes straight? Here's the fix
network printer not working on one computer printer works on one pc not others network printer driver mismatch printer port settings TCP/IP port printer Windows printer sharing printer spooler crash network printer discovery printer firewall block printer installation fail

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.