F5F Stay Refreshed Software Operating Systems Connecting a printer to an Arch Linux system for Windows users

Connecting a printer to an Arch Linux system for Windows users

Connecting a printer to an Arch Linux system for Windows users

K
Kittylover71
Junior Member
3
02-13-2023, 10:18 AM
#1
I've dealt with the common belief that printers don’t “just work.” I’ve followed several instructions, set up CUPS and the samsung-unified-driver package, and successfully printed a test page. The issue begins when sharing the printer to a Windows client. I attempted Samba first (see config), but it prompts for a driver, selects my model, and shows the printer in the control panel. Still, nothing prints—no errors, just silence. Then I tried IPP, following each step carefully, but the same problem persists. I also tried changing the printer’s make/model to raw in CUPS, without success. Now I’m stuck with this setup.
K
Kittylover71
02-13-2023, 10:18 AM #1

I've dealt with the common belief that printers don’t “just work.” I’ve followed several instructions, set up CUPS and the samsung-unified-driver package, and successfully printed a test page. The issue begins when sharing the printer to a Windows client. I attempted Samba first (see config), but it prompts for a driver, selects my model, and shows the printer in the control panel. Still, nothing prints—no errors, just silence. Then I tried IPP, following each step carefully, but the same problem persists. I also tried changing the printer’s make/model to raw in CUPS, without success. Now I’m stuck with this setup.

A
Aimee749
Junior Member
18
02-13-2023, 11:49 AM
#2
Can the printer function properly when linked directly to a Windows client? It may stem from a Windows driver problem.
A
Aimee749
02-13-2023, 11:49 AM #2

Can the printer function properly when linked directly to a Windows client? It may stem from a Windows driver problem.

F
foxerbro81
Junior Member
27
02-13-2023, 04:10 PM
#3
Yes, it functions effectively.
F
foxerbro81
02-13-2023, 04:10 PM #3

Yes, it functions effectively.

J
jep96
Junior Member
6
02-14-2023, 12:58 AM
#4
The documentation states that printer sharing must be enabled on the cups server for remote access via IPP. If you haven’t done this yet, it might be the cause of your problem: https://www.cups.org/doc/sharing.html. Also check if your firewall on the Arch computer is blocking IPP requests.
J
jep96
02-14-2023, 12:58 AM #4

The documentation states that printer sharing must be enabled on the cups server for remote access via IPP. If you haven’t done this yet, it might be the cause of your problem: https://www.cups.org/doc/sharing.html. Also check if your firewall on the Arch computer is blocking IPP requests.

S
Shad0wHydra13
Senior Member
716
02-25-2023, 10:39 PM
#5
Printer sharing is active in cups, and it works in Windows as well. I can access it without issues, but printing documents fails. No firewalls are present on the server. It might be the router that’s preventing requests.
S
Shad0wHydra13
02-25-2023, 10:39 PM #5

Printer sharing is active in cups, and it works in Windows as well. I can access it without issues, but printing documents fails. No firewalls are present on the server. It might be the router that’s preventing requests.

K
Killa_Dx
Senior Member
645
02-26-2023, 06:56 AM
#6
It's been several decades using Windows, yet for shared printers you usually don't install drivers on the client side. CUPS manages the drives and controls the printer for the user, sharing it as a standard device with advertised capabilities like color/BW, duplex, and paper sizes. However, since I've moved away from Windows, I can't help with this setup, nor can I confirm your CUPS settings are accurate. A simple check shows your configuration appears correct. What I'd suggest is removing the printer from Windows and re-adding it as a network device. Avoid picking a specific model—this assumes a local or directly connected printer without a server like CUPS in between.
K
Killa_Dx
02-26-2023, 06:56 AM #6

It's been several decades using Windows, yet for shared printers you usually don't install drivers on the client side. CUPS manages the drives and controls the printer for the user, sharing it as a standard device with advertised capabilities like color/BW, duplex, and paper sizes. However, since I've moved away from Windows, I can't help with this setup, nor can I confirm your CUPS settings are accurate. A simple check shows your configuration appears correct. What I'd suggest is removing the printer from Windows and re-adding it as a network device. Avoid picking a specific model—this assumes a local or directly connected printer without a server like CUPS in between.

R
RossBoomsocks
Junior Member
41
02-26-2023, 09:13 PM
#7
Try this on the Linux system: add guest user with /bin/nologin then open nano /etc/samba/smb.conf and update the sections accordingly. Include new lines where needed.
[Printers] available = yes guest access = allowed [guest] comment = Guest directory path = /tmp public = yes only guest = yes printables = no
Restart service if issues arise: sudo systemctl restart smb or reboot.
Ensure the client has proper permissions and a valid account on the host for Samba sharing.
R
RossBoomsocks
02-26-2023, 09:13 PM #7

Try this on the Linux system: add guest user with /bin/nologin then open nano /etc/samba/smb.conf and update the sections accordingly. Include new lines where needed.
[Printers] available = yes guest access = allowed [guest] comment = Guest directory path = /tmp public = yes only guest = yes printables = no
Restart service if issues arise: sudo systemctl restart smb or reboot.
Ensure the client has proper permissions and a valid account on the host for Samba sharing.