Print via SMB from Windows to Linux-hosted printer — CUPS & Samba redirect guide
Joe B.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Windows 11/10, Linux (Ubuntu/Debian/Fedora), CUPS, Samba/SMB, Networking, Office Equipment
Print via SMB from Windows to Linux printer — CUPS/Samba, \\hostname\printer, IPP/LPR fallback
Technician
[printers] / [print$])? On Windows 10/11 we’ll add \\hostname\printer and fix credentials, SMB protocol version, firewall, and driver mapping.
\\printsrv\HP_Laser.
Technician
• Permissions/credentials: Samba share requires a user not matching your Windows account; Windows caches wrong creds.
• SMB protocol mismatch: server forces SMB1 off but client tries legacy; or NTLM policy blocks auth; signing required.
• Driver mapping: missing “Point and Print” driver on the server; Windows Type 4 driver isn’t compatible with raw queue.
• Firewall/Name resolution: mDNS/NetBIOS not resolving
\\printsrv or ports 445/139 blocked.• CUPS share mode: queue isn’t shared or using raw vs IPP backend incorrectly.
Plan: verify CUPS share + Samba config, clear Windows cached creds, add via SMB path (or IPP/LPR fallback), and set a stable Windows driver.
Technician
1) Open Settings → Bluetooth & devices → Printers & scanners → Add device → Add manually → Select a shared printer by name → enter
\\printsrv\HP_Laser (replace with your \\hostname\printer).2) When prompted for credentials, use your Samba user (DOMAIN\user or printsrv\user). If login fails, clear old creds: Control Panel → Credential Manager → Windows Credentials → remove entries for the server.
3) Choose a vendor driver (HP/Epson/Canon/Brother) or a compatible Type 3/Type 4 class driver. For raw queues, pick a model-specific PCL/PS driver; for CUPS filtering use Generic PostScript.
4) If the shared printer doesn’t resolve, connect by IP:
\\192.168.x.y\HP_Laser. Ensure ports 445/139 are open.
Technician
• CUPS: in the web UI (
http://localhost:631) ensure the printer is Shared and Publish shared printers is enabled.• Samba: in
smb.conf confirm [printers] with printable = yes, proper path for spools, and [print$] for driver store (optional). Set guest ok or valid users accordingly.• User mapping: run
smbpasswd -a youruser; test with smbclient //printsrv/HP_Laser -U youruser.• Protocols: set
server min protocol = SMB2 (avoid SMB1), align with Windows security (NTLMv2).• Firewall: open
445/tcp, 139/tcp, and CUPS 631/tcp if using IPP.If policy blocks SMB printing, we can use IPP over HTTP (
http://printsrv:631/printers/HP_Laser) or LPR as a fallback in Windows.
Technician
• In Add printer choose The printer that I want isn’t listed → Add a printer using a TCP/IP address or hostname → type: Internet Printer → URL:
http://printsrv:631/printers/HP_Laser or ipp://printsrv/ipp/print.• For LPR: choose TCP/IP device → LPR queue name = CUPS queue (e.g., HP_Laser).
This bypasses SMB permissions while keeping the Linux server as the print server.
Technician
• Raw queue on CUPS + Windows vendor driver (HP/Epson/Canon/Brother PCL/PS). Advantage: full features (duplex, stapling).
• Filtered queue on CUPS + Generic PS on Windows. CUPS handles rendering; Windows uses a light driver. Stable for mixed environments.
If Samba “Point and Print” is required, populate
[print$] with drivers and match architecture (x64). Otherwise, install drivers locally on each Windows client.
Technician
• Lock driver version on Windows (use the vendor package and disable automatic replacement).
• In managed environments, set Group Policy: Computer Config → Admin Templates → Printers → Point and Print Restrictions and allow your print server.
• Store stable credentials in Credential Manager (or use guest ok on a segregated LAN).
• Prefer IPP for long-term reliability where SMB security changes often.
Technician
Brother: Use Brother Linux drivers for CUPS filtering; on Windows the “Brother BR-Script/PS” or model PCL works well.
For both brands, match duplex, tray options, and paper sizes on the Windows queue to avoid “Hold for resources” in CUPS logs.
Technician
/var/log/samba/ and CUPS error_log for auth or filter errors. Save a Windows printer preset and document the UNC path for users.
Technician
Quick answer: the accepted fix
Accepted fix when Windows 10/11 cannot print to a Linux Samba/CUPS printer: share the queue in CUPS, configure Samba with SMB2 and valid users, add the printer in Windows by \\hostname\printer with correct credentials, and install a compatible vendor or Generic PS driver. If SMB fails, connect via IPP (http/ipp) or LPR.
SMB printer disappears after Windows update (driver unavailable / access denied)
Updates can change SMB client security or replace a class driver. Re-add the UNC path, clear Credential Manager, reinstall the vendor driver, and confirm Point and Print policies allow your Linux print server. As a policy-proof option, add the printer via IPP (http://server:631/printers/Queue).
How to verify SMB printing works
Print a test page and a 3-page PDF, confirm the job appears in CUPS and completes. If jobs hang, check Samba logs for NT_STATUS_ACCESS_DENIED or signing issues; try IP connection \\IP\queue and validate ports 445/139. If output is garbled, switch to a model-specific PCL/PS driver or use Generic PostScript with a filtered CUPS queue.
Windows → Linux SMB printing — troubleshooting tips
Most issues are credentials, protocol mismatch, or driver mapping.
Quick path: verify CUPS sharing → check Samba users & SMB2 → add via \\hostname\printer → install a compatible driver or use IPP/LPR fallback. For discovery/name resolution issues, use the server IP address instead of hostname.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
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
Windows can’t connect to \\hostname\printer — what to check?
Confirm the printer is Shared in CUPS, your Samba user exists (smbpasswd -a), and that Windows uses correct credentials (clear Credential Manager). Try the IP format \\serverIP\queue and ensure ports 445/139 are open.
Which protocol is best — SMB vs IPP vs LPR?
SMB works well for Windows shops. If SMB security policies block printing, IPP via CUPS is the most reliable cross-platform option; LPR is a simple fallback.
Driver strategy for Linux-hosted printers?
Use a vendor PCL/PS driver with a raw CUPS queue for full features, or install Generic PostScript on Windows and let CUPS do filtering. Avoid mismatched Type 4 drivers with raw queues.
Why did SMB printing break after a Windows update?
Updates may tighten SMB/NTLM requirements or replace a class driver. Re-add the queue, reinstall the vendor driver, and consider IPP to bypass SMB policy changes.
How do I map multiple Windows clients to a Linux print server?
Document the UNC path, pre-create Samba users, deploy drivers via script or GPO, and test both SMB and IPP connections for resilience.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| “Windows cannot connect to the printer” | Wrong creds; SMB protocol/signing; firewall | Clear credentials; enforce SMB2/NTLMv2; open 445/139; try \\IP\queue |
| Jobs stuck / Driver unavailable | Class driver replaced; raw vs filtered mismatch | Install vendor PS/PCL or use Generic PS with CUPS filtering |
| Printer visible then disappears | Name resolution / NetBIOS disabled | Use server IP or DNS A-record; add via UNC path manually |
| Access denied | Samba share permissions | Create Samba user (smbpasswd -a), set valid users or guest ok as needed |
Step-by-step (Windows 10/11 client)
- Open Printers & scanners → Add device → Add manually → \\hostname\printer (or \\IP\queue).
- Enter Samba credentials or clear old ones in Credential Manager.
- Select a compatible vendor driver (or Generic PS if CUPS filters).
- If SMB fails, add via IPP (
http://server:631/printers/Queue) or LPR.
Step-by-step (Linux server — CUPS & Samba)
- In CUPS, mark the printer as Shared and enable Publish shared printers.
- In smb.conf, configure
[printers](printable = yes) and protocols (server min protocol = SMB2); add users withsmbpasswd -a. - Open firewall ports 445/139 (SMB) and 631 (IPP).
- Decide driver model: raw queue + vendor driver on Windows, or filtered queue + Generic PS on Windows.
Sources
- Microsoft — Printers & Windows printing
- CUPS — Documentation
- Samba — smb.conf reference
- Microsoft — NTLM/SMB security guidance
Filed under: Network security / VPN / office policies (advanced)
Related articles
- Print server loses connection after GPO update — policy precedence fix
- Print rules by user/department — enforce via policy
- Printer won’t print prescriptions or medical reports — it’s urgent and nothing comes out
- Chrome managed profile watermark prints wrong — policy override checks you can do safely
- Ricoh “Hold Print” enabled by AD — disable policy
- Ricoh SMB scan works but print fails — AES signing mismatch
- Android VPN blocks printer discovery — split tunnel rule (work profile)
- Android “Secure print only” — enterprise toggle: setup, policy, fixes