Windows: can’t add network/shared printer (0x0000011b / 0x00000709) — step-by-step fix
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)
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.
| Symptom | Likely cause | Quick 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)
- Verify SMB access: open
\\\\SERVER\\and note\\\\SERVER\\PRINTERpath. - Try IPP: Add printer → manual → Web Services Device →
https://server:631/ipp/print. - Try TCP/IP: Add local printer → Standard TCP/IP Port (RAW 9100 or LPR).
- On print server: set
HKLM\\...\\Print\\RpcAuthnLevelPrivacyEnabled=0→ restart spooler. - For 0x00000709: disable auto-default, clear
HKCUdefault printer keys, reconnect and set default.
Sources
- Microsoft — Print Spooler security & RPC changes
- Microsoft — IPP printing in Windows
- Microsoft — Printer registry keys
Filed under: Printer won’t print
Related articles
- Printer prints a PDF blank — but the printer isn’t “out of ink”
- Printer says “Offline” and won’t print — what should I check first?
- My printer “forgot” my Wi-Fi — the saved network is gone
- Printer Wi-Fi settings reset by itself — why did it forget my network?
- My printer keeps popping up “Set up Wi-Fi” again — why won’t it stay connected?
- Why does my printer need Wi-Fi setup again? It was working yesterday.
- My printer Wi-Fi setup keeps failing — what am I doing wrong?
- Printer Wi-Fi setup is confusing — why won’t it connect to my network?