RAW 9100 vs LPR — fix print jobs dropping mid-print

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, Printers, Networking, Print Servers, Queue Optimization

RAW 9100 vs LPR — correct queue naming, stable ports, and why jobs drop mid-print

Technician

Hey, we can sort this. When print jobs drop mid-print or disappear from the Windows print queue, it’s very often a mismatch between RAW 9100 and LPR settings, or an incorrect LPR queue name on a Windows print server or direct IP port.
I’ll walk you through checking the port type, LPR queue naming, spooler settings, and device-side configuration so your jobs stop vanishing half-way through.

Customer

We have a network printer on a Windows print server. Some users print fine, others say their jobs just vanish or stop in the middle of large PDFs. Port is set to RAW 9100 on some queues, LPR on others. It’s inconsistent.

Technician

Got it — classic RAW 9100 vs LPR situation.
In short:

• RAW 9100 (TCP 9100) streams data directly. If the connection blips, the job can drop mid-print without retry.
• LPR relies on a specific LPR queue name (often raw, lp, print, or model-specific). A wrong queue name = jobs “sent” but never printed.
• Mixing different ports for the same device, misconfigured bidirectional support, or using LPR byte counting incorrectly can cause jobs to vanish, get stuck, or only partly print.

We’ll standardize: one stable protocol, correct queue naming, right port options, and confirm settings match what your HP/Brother/Canon/Epson device expects.

Customer

How do I check if the LPR queue name is wrong or if RAW 9100 is causing drops? Right now big jobs sometimes stop at random pages.

Technician

Step 1 — Confirm the port type & LPR queue name
On the Windows print server or PC that hosts the printer:

1. Right-click the printer → Printer properties → Ports.
2. Check whether it’s using Standard TCP/IP Port in RAW 9100 mode or LPR mode.
3. If LPR is selected:
   • Verify the exact LPR queue name from the printer’s web interface or documentation.
   • A wrong queue (e.g. lp1 instead of raw) = jobs reported as successful but never print.

Secondary check: ensure spool folder isn’t full or on a flaky disk; a broken spooler can mimic RAW 9100 drops.

Customer

The device page shows queue “raw”. Some of our ports use LPR with queue “lp” and “auto”. Others are RAW 9100. That sounds wrong?

Technician

Yes, that mix will absolutely cause inconsistent printing and jobs going missing.
Step 2 — Standardize RAW vs LPR for this printer

• Pick one method per device:
  • If vendor docs recommend LPR with queue raw, use LPR + correct queue name on all queues.
  • If they recommend RAW 9100, use a Standard TCP/IP Port (RAW, port 9100) consistently.
• Remove old ports that use lp, “auto” or random queue names.
• Disable experimental settings (SNMP, byte counting, bidirectional support) temporarily while testing stability.

One printer = one protocol + one correct queue. That alone fixes many “sent but never printed” or jobs dropping mid-print issues.

Customer

How does RAW 9100 actually cause mid-print drops? Users complain long reports stop on page 5 of 20.

Technician

Step 3 — Understand RAW 9100 behavior
RAW 9100 is a fast, simple stream:

• If the network link drops, the printer reboots, or a firewall/IPS cuts the session, the job stops with no retry.
• Poor Wi-Fi bridges, overloaded switches, or flaky VPN tunnels make RAW 9100 jobs drop mid-print.
• Server-side timeouts or security devices that scan/interrupt TCP 9100 can truncate large PDFs or label batches.

If your environment is noisy or multi-site, moving this queue to a validated LPR port with correct queue name or tightening RAW stability often solves intermittent failures.

Customer

So should we switch everything to LPR, or keep RAW 9100? And what about byte counting and SNMP on LPR?

Technician

Step 4 — Choose the right protocol for your printer
General guidance:

• Use LPR if:
  • The vendor explicitly documents an LPR queue (e.g. many copiers, print servers).
  • You need better accounting and consistent job completion tracking.
• Use RAW 9100 if:
  • The printer is on a stable LAN with static IP.
  • The vendor states 9100/RAW is the preferred method (common for HP, Zebra, label/receipt printers).
• For LPR:
  • Set the exact queue name (case-sensitive on some devices).
  • Enable/disable LPR byte counting according to vendor docs; wrong setting can cause stuck or incomplete jobs.

Pick one, configure it correctly everywhere, and you remove a huge part of your jobs dropping mid-print risk.

Customer

We’re using a Windows print server for 40 users. Some queues are shared from the server, some direct IP from clients. Could that be part of the problem?

Technician

Yes — that split design is a common failure pattern.
Step 5 — Clean up a multi-user / print server setup

• Standardize: create a single, known-good queue on the Windows print server (RAW or LPR with correct queue name).
• Share that queue; have clients use the shared path, not random direct IP ports.
• Remove direct-IP queues from workstations that bypass the server or use different port types.
• Check Advanced tab:
  • “Spool print documents so program finishes printing faster” is typical.
  • Use “Start printing after last page is spooled” for unstable links so long jobs don’t cut off.

This ensures consistent behavior and makes job drop troubleshooting much easier.

Customer

After fixing ports and using the same shared queue, small jobs are fine. How do we stress test so big jobs don’t fail again?

Technician

Step 6 — Verify with large jobs & logging

• Print several large PDFs and long reports through the same queue.
• Watch Print Management → Jobs and the printer’s web UI:
  • Jobs should move from Spooling → Printing → Completed, not vanish.
• Enable basic printer error logging or SNMP alerts to catch timeouts.
• If you still see failures:
  • Check for firewall or IDS/IPS scanning TCP 9100 or LPR.
  • Test switching from RAW 9100 to LPR (or vice versa) with the correct queue name as a stability comparison.

Once those tests pass, you’ve got a stable network print queue for both small and large jobs.

Customer

Looks solid now. Users report no more disappearing jobs. Anything else we should lock in so it stays reliable?

Technician

Summary: To fix RAW 9100 vs LPR print jobs dropping mid-print, standardize on one protocol, set the correct LPR queue name or RAW 9100 port, remove bad/old ports, unify queues on the print server, tune spooler options, and verify with large jobs. This prevents jobs from disappearing, half-printing, or stalling in the queue.
Want a specialist to review your Windows print server, ports, and queue configuration live? Open the chat.

Quick answer: the accepted fix

Accepted fix when print jobs drop mid-print on RAW 9100 vs LPR: confirm the correct protocol for your printer, set the exact LPR queue name or stable RAW 9100 port, remove inconsistent ports and duplicate queues, and route all users through a single, standardized queue on the Windows print server. Test with large jobs to ensure no more disappearing prints.

FAQ

Step-by-step: stabilize RAW 9100 vs LPR on Windows

1. On the printer, set a static IP and note supported protocols and LPR queue names.
2. On the Windows print server, open Printer properties → Ports and remove legacy/incorrect ports.
3. Create a new Standard TCP/IP Port:
   • Choose RAW 9100 if recommended, or
   • Select LPR and enter the exact queue name from the device docs.
4. Apply consistent settings on all shared queues and client connections; avoid mixing protocols per device.
5. In Advanced, tune spooler options and test with large jobs to confirm no more mid-print drops.

Note for mixed environments (macOS, Linux, print appliances)

1. Align macOS and Linux queues with the same LPR queue name or RAW 9100 target used on Windows.
2. When using CUPS or print appliances, ensure their output queue to the device also uses the documented protocol and queue.
3. Avoid having one system use LPR “raw” while another uses a random RAW 9100 or AirPrint path for the same printer.

Sources

• Microsoft — Print server management
• HP Support — Network printing and port configuration
• Brother — Standard TCP/IP & LPR queue setup

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.