RAW 9100 jobs stuck — when to use LPR vs RAW and correct queue name

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, macOS (Sonoma/Ventura/Monterey), Printers, Networking, TCP/IP Ports (RAW 9100 / LPR), CUPS

Windows print jobs stuck on RAW 9100 — switch to LPR, set LPR byte counting, and use the correct queue name (HP, Epson, Canon, Brother)

Technician

Hey! Let’s unstick those jobs on RAW/Port 9100. Tell me the printer brand (HP/Epson/Canon/Brother), the connection type (Wi-Fi or Ethernet), and whether you added the queue as a Standard TCP/IP Port (RAW 9100) or LPR. We’ll check if JetDirect 9100 is blocked by the firewall or if the device expects LPR with a specific queue name (e.g., raw, lp, print, or a model-specific name). We’ll also verify LPR byte counting and the Windows Print Spooler status.

Customer

Windows 11 PCs, mixed printers. Jobs show “Printing” forever on a Standard TCP/IP Port (RAW 9100) and never leave the queue. Another site said use LPR. How do I decide between LPR vs RAW, and what queue name should I enter?

Technician

Why RAW 9100 jobs get stuck:
• The device exposes only LPR/LPD (port 515) or prioritizes it; RAW 9100 is disabled or filtered.
• Wrong LPR queue name (common defaults: raw, lp, print, or the exact queue shown in the web UI).
• LPR byte counting mismatch (enabled vs disabled) causes hangs/truncation.
• SNMP status or bidirectional support loops the port monitor.
• Firewall/NAC blocks TCP 9100 or 515; Wi-Fi isolation/VLAN ACLs drop traffic.
Rule of thumb: use RAW 9100 for JetDirect-style printing when 9100 is open; use LPR when the MFP requires a named queue or when RAW stalls.

Customer

What’s the exact Windows path to switch the port and set the queue name?

Technician

Windows 10/11 — switch to LPR or repair the RAW 9100 port:
1) Settings → Bluetooth & devices → Printers & scanners → your printer → Printer properties → tab Ports.
2) Click Add Port… → Standard TCP/IP Port → New Port….
3) Enter the printer’s IP/hostname → when prompted, choose Custom → Settings….
4) Choose either:
  • Protocol: RAW — Port Number: 9100 (JetDirect). If jobs hang, uncheck SNMP Status Enabled and test.
  • Protocol: LPR — enter Queue Name (try raw / print / lp or the exact name shown on the device). Toggle LPR Byte Counting per vendor docs.
5) Apply and test: Test-NetConnection -ComputerName <IP> -Port 9100 (RAW) or -Port 515 (LPR).

Customer

How do I find the correct LPR queue name for HP/Epson/Canon/Brother?

Technician

Typical LPR queue names (varies by firmware):
• HP (JetDirect): often raw (direct), or named per function (e.g., print). RAW 9100 is usually supported — if blocked, use LPR.
• Epson: common print or lp on embedded print servers; check the web panel → Network → Services.
• Canon: imageRUNNER queues may be named; use the exact LPD queue shown in the device UI; RAW works on some models, LPR on others.
• Brother: legacy BINARY_P1 or raw/print. The web UI lists the Queue Name for LPR/LPD.
If unsure, print the Network Configuration Page or open the printer’s web admin — it shows the LPD queue and whether RAW 9100 is enabled.

Customer

Jobs still stall on RAW. Could firewall or SNMP cause this?

Technician

Yes. Quick checks:
• Firewall: allow TCP 9100 (RAW) or TCP 515 (LPR) from clients. Test with Test-NetConnection or telnet <IP> 9100.
• SNMP status: in Port settings uncheck SNMP Status Enabled (some MFPs misreport and stall).
• Wi-Fi isolation/VLAN: ensure inter-VLAN ACLs allow 9100/515; disable AP client isolation for printer segment.
• Antivirus/IPS: some suites block JetDirect traffic — add an exception.
If RAW remains flaky, switch the port to LPR with the correct queue name — it’s often more reliable.

Customer

We also print from Macs and Linux. Should we use LPR or socket there?

Technician

On macOS/Linux (CUPS):
• socket://IP:9100 = RAW 9100 (JetDirect). Fast, minimal overhead.
• lpd://IP/QUEUE = LPR/LPD. Use when the device expects a named queue or RAW is blocked.
Test with: lpstat -t, lpoptions -p PRINTER -l, and lp -d PRINTER file.pdf.
If jobs hang, switch protocols and confirm the queue name matches exactly.

Customer

Anything else to clear a stuck Windows queue?

Technician

To clear a Windows Print Spooler that’s stuck:
1) Run PowerShell as admin:
Stop-Service Spooler
Remove-Item -Path C:\Windows\System32\spool\PRINTERS\* -Force
Start-Service Spooler
2) Delete failed jobs from the UI and retry on the fixed port (RAW or LPR).
3) If the port still reverts, remove the printer and create a fresh Standard TCP/IP Port with the correct protocol and queue.

Customer

Do brands matter here? We run HP LaserJet, Epson WorkForce, Canon imageRUNNER, and some Brother models.

Technician

Brand specifics — HP / Epson / Canon / Brother:
• HP (JetDirect): RAW 9100 is standard; if blocked or flaky, use LPR queue: raw. Disable SNMP status if jobs stall.
• Epson: many MFPs prefer LPR with queue: print or lp. Toggle LPR byte counting if jobs truncate.
• Canon: imageRUNNER queues may be named; use the exact LPD queue from the web UI; RAW works on some models, LPR on others.
• Brother: legacy BINARY_P1 or raw/print; LPR often more reliable over Wi-Fi.

Customer

Can you give me a short checklist to decide LPR vs RAW and queue settings?

Technician

Quick decision checklist:
1) Test connectivity: Test-NetConnection <IP> -Port 9100 (RAW) and -Port 515 (LPR).
2) If RAW reachable and vendor supports JetDirect → use RAW 9100.
3) If RAW fails or device lists an LPD queue → use LPR with the exact Queue Name.
4) Toggle LPR Byte Counting per vendor guidance; uncheck SNMP Status Enabled if stalls persist.
5) Recreate the port rather than editing a broken one; then send a 1-page test PDF.

Customer

Perfect — switching to LPR with the right queue fixed it. Thanks!

Technician

Summary: If RAW 9100 print jobs are stuck, confirm firewall reachability, try disabling SNMP status, and switch to LPR with the correct queue name (raw/print/lp or device-specific). Rebuild the Standard TCP/IP Port, adjust LPR byte counting, and retest. Need hands-on help? Open the chat.

Quick answer: the accepted fix

Accepted fix when RAW 9100 jobs are stuck: recreate the Standard TCP/IP Port as LPR with the correct Queue Name (e.g., raw, print, lp), or repair RAW 9100 and disable SNMP Status. Allow TCP 9100/515 through the firewall and clear the Print Spooler before retesting.

FAQ

Step-by-step (Windows 10/11)

1. Delete failed jobs. Open Printer properties → Ports → Add Port… → Standard TCP/IP Port.
2. Choose Custom → Settings…. For RAW, set Port 9100 and uncheck SNMP Status Enabled if stalls persist.
3. Or choose LPR, enter the Queue Name from the printer’s web UI (raw/print/lp), and set LPR Byte Counting as recommended.
4. Test: Test-NetConnection -ComputerName PRINTER -Port 9100 or -Port 515; print a 1-page PDF.

Step-by-step (macOS/Linux, CUPS)

1. Add printer as socket://IP:9100 (RAW) or lpd://IP/QUEUE (LPR) in Printers & Scanners / CUPS.
2. Match the Queue exactly; if RAW fails, switch to LPR.
3. Print a test page; if truncated, toggle options/byte counting or try vendor driver.

Sources

• Microsoft — Standard TCP/IP Port printing
• HP — JetDirect/9100 printing
• Canon — LPD/LPR configuration
• Epson — Network printing (LPR/RAW)
• Brother — LPR/RAW port 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.