Printer troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Windows 11/10, Printers, SMB/Networking, Group Policy, Office Equipment

Fix Windows network printer errors: 0x0000011b, 0x00000709, “can’t connect to shared printer” (Win 11/10)

Technician avatar Technician
Hi! When Windows shows 0x0000011b during install or 0x00000709 when setting a default/shared printer, it’s usually RPC encryption or name-resolution trouble introduced by security updates (aka PrintNightmare hardening). We’ll check the print server share path, open ports, try IPP Everywhere and TCP/IP printer port, and—only if needed—apply a safe fix 0x0000011b registry change.
Customer
Windows 11 Pro laptops can’t add our office HP shared from a Windows 10 PC. Error 0x0000011b. Another PC says 0x00000709. We just installed updates.
Technician avatar Technician
Thanks. First, confirm the print server (the PC that shares the printer) and clients are on the same network, and you can browse \\\\SERVERNAME\\ in File Explorer. Note the exact share path like \\\\PRINTPC\\HP-Laser. If SMB browsing works, the issue is Windows RPC encryption printing policy after recent KBs.
Customer
Yes, I can open \\\\PRINTPC\\ and see the share. Still fails to connect with 0x0000011b.
Technician avatar Technician
Workaround #1 — add printer by IPP (Windows):
On the client: Settings → Bluetooth & devices → Printers & scanners → Add device → Add manually → Add a printer using a TCP/IP address or hostname → set Device type: Web Services Device (HTTPS) and URL https://PRINTPC:631/ipp/print or use the printer’s IP https://PRINTERIP:631/ipp/print. If the device supports IPP Everywhere, Windows will install it without server-side spooling, bypassing 0x0000011b.
Customer
Our HP supports IPP. Adding via https://printer-ip:631/ipp/print worked on one laptop, but another still can’t connect to the shared queue we need.
Technician avatar Technician
Workaround #2 — TCP/IP printer port (RAW/9100 or LPR):
  1. On the client, open Control Panel → Devices and Printers.
  2. Add a printer → The printer that I want isn’t listed → Add a local printer → Create a new port → Standard TCP/IP Port.
  3. Enter the printer’s IP. Use RAW, Port 9100 (or LPR with queue raw).
  4. Select the correct HP/Epson/Brother driver or Generic → MS Publisher Imagesetter as a test.
This avoids the Windows network printer error path entirely.
Customer
Direct TCP/IP works, but we prefer using the server’s shared queue for accounting. Can we fix 0x0000011b properly?
Technician avatar Technician
Server-side fix — RPC encryption policy (recommended): On the print server, set the policy so legacy clients can connect while you plan a permanent rollout.
  • Run regedit as admin.
  • Go to HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Print.
  • Create DWORD (32-bit) RpcAuthnLevelPrivacyEnabled = 0.
  • Restart the Print Spooler service or reboot.
This is the standard fix 0x0000011b registry change Microsoft documented for environments impacted by PrintNightmare. Re-test adding \\\\PRINTPC\\HP-Laser.
Customer
After setting RpcAuthnLevelPrivacyEnabled=0 and restarting the spooler, clients can add the shared printer again. What about 0x00000709?
Technician avatar Technician
Error 0x00000709 often appears when Windows can’t set a default printer or binds to an older queue name. Fix:
  1. Settings → Bluetooth & devices → Printers & scanners → toggle Let Windows manage my default printer off.
  2. Delete stale connections to \\\\PRINTPC\\oldqueue and clear Devices and Printers.
  3. Open regedit → HKCU\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Windows → remove values Device and UserSelectedDefault (or set to the new queue) → sign out/in.
Reconnect the share and set it as default.
Customer
Got it. If the problem comes back after Patch Tuesday, what should we look at?
Technician avatar Technician
Check for uninstall KB update printer issue scenarios. If a cumulative KB breaks printing, uninstall it on the print server first: Settings → Windows Update → Update history → Uninstall updates. Then pause updates, confirm printing, and re-apply once a fixed KB ships.
Technician avatar Technician
Hardening tips (long-term):
• Use Type 4 drivers or IPP Everywhere queues instead of legacy shared drivers.
• If sharing via SMB, ensure clients and server are domain-joined when possible and allow RPC over TCP to the spooler (firewall Spooler RPC rules).
• Prefer add printer by IPP (Windows) for laptops; keep a fallback tcp/ip printer port Windows queue for resilience.
Customer
Everything works now via the shared queue and IPP fallback. Any quick checklist we can keep?
Technician avatar Technician
Quick checklist: verify SMB access → try IPP 631 → try TCP/IP 9100/LPR → set server key RpcAuthnLevelPrivacyEnabled=0 if you hit 0x0000011b → clear default printer/registry for 0x00000709 → review updates and spooler service. If you want, I can remote-guide policy & registry edits. Open the chat.

Quick answer: the accepted fix

Accepted fix: For Windows 11/10 network printer error 0x0000011b, set the print server registry HKLM\\SYSTEM\\CurrentControlSet\\Control\\Print\\RpcAuthnLevelPrivacyEnabled=0 and restart the spooler. If you still can’t connect to shared printer Windows 11, add by IPP (https://server:631/ipp/print) or create a TCP/IP printer port (RAW 9100/LPR). For printer error 0x00000709, disable “Let Windows manage my default printer,” clear default printer values in HKCU, and reconnect.


After Windows update: shared printer fails (0x0000011b)

Recent security updates can force RPC encryption printing Windows and break legacy shared queues. Either migrate to IPP Everywhere or temporarily apply the fix 0x0000011b registry on the server and plan a driverless rollout. If necessary, uninstall KB update printer issue and hold updates until the vendor patch lands.

Verify printing path: IPP / TCP/IP / Shared

Print a Windows test page from an IPP queue, then from a TCP/IP printer port, and finally from the shared printer. If IPP works but the share fails, it’s policy-level (0x0000011b). If none work, check firewall/DNS and reinstall drivers.

Troubleshooting tips for Windows network printer errors

Targets: windows error 0x0000011b printer, printer error 0x00000709, and generic windows 10 network printer error.

Start with SMB reachability and DNS. Try add printer by IPP Windows (https://server:631/ipp/print) and a plain tcp/ip printer port Windows (9100). For stubborn shared-queue issues, apply RpcAuthnLevelPrivacyEnabled=0 on the server, then restart the spooler. As a last resort, consider a temporary print nightmare fix path by rolling back a problematic KB and pausing updates.

Disclaimer: Editing the registry can affect system stability. Back up the registry and create a restore point first. This information is AI-generated and for general guidance. For environment-specific advice, talk to a verified expert on Whizz-Tech.


Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.

Expert will respond in minutes

We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.

Save time & money

No scheduling hassles or expensive consults. Membership can save you significant time and money each month.

FAQ

What causes Windows printer error 0x0000011b?

It’s commonly triggered by security updates that enforce RPC encryption between clients and the print spooler. Fix by adding the server registry RpcAuthnLevelPrivacyEnabled=0, switching to IPP Everywhere, or using a TCP/IP printer port.

How do I fix printer error 0x00000709?

Turn off “Let Windows manage my default printer,” remove old queue mappings, and clear default printer values in HKCU\\...\\Windows. Re-add the printer and set it as default.

Best way to add printers on laptops?

Use add printer by IPP Windows (https://server:631/ipp/print) so printing works on and off VPN. Keep a fallback TCP/IP port (9100/LPR) if IPP is blocked.

Can Windows updates break printing?

Yes. If you hit issues after Patch Tuesday, consider an uninstall KB update printer issue rollback on the print server, then re-apply when Microsoft releases a fix.

Is the PrintNightmare fix still relevant?

Yes. The print nightmare fix hardened spooler behavior, which is why 0x0000011b appears. Moving to IPP or Type 4 drivers is the long-term solution.

Common Windows network printer problems and quick fixes
SymptomLikely causeQuick fix
0x0000011b when adding shared printer RPC encryption policy after updates Set RpcAuthnLevelPrivacyEnabled=0 on server; or use IPP/TCP-IP
0x00000709 setting default printer Stale default values; old queue name Disable Windows-manage-default; clear HKCU defaults; reconnect
Clients can browse \\server but not print Firewall blocks Spooler RPC Enable File and Printer Sharing and Spooler RPC inbound rules
Works via IPP, not via share Server-side policy/driver issue Migrate to IPP Everywhere or Type 4 drivers

Windows 11/10 quick steps (0x0000011b / 0x00000709)

  1. Verify SMB access: open \\\\SERVER\\ and note \\\\SERVER\\PRINTER path.
  2. Try IPP: Add printer → manual → Web Services Device → https://server:631/ipp/print.
  3. Try TCP/IP: Add local printer → Standard TCP/IP Port (RAW 9100 or LPR).
  4. On print server: set HKLM\\...\\Print\\RpcAuthnLevelPrivacyEnabled=0 → restart spooler.
  5. For 0x00000709: disable auto-default, clear HKCU default printer keys, reconnect and set default.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant