Arch Linux

VictorSerge

Member

Registered: 2025-06-22

Posts: 6

Authenticating SAMBA network printer

I'm running Arch, latest kernel, KDE Plasma desktop environment.

My employer uses SAMBA printer server. I cannot get authentication to work; that is, sending print jobs fails with the message in CUPS: NT_STATUS_CONNECTION_REFUSED.

The most frustrating thing about this is that it was working fine, and then stopped, but I don't think I updated any printing-relevant packages and the employer insists that they didn't change anything on the server.

When I try deleting and reinstalling the printer:

Via CUPS: everything goes well enough but then any job stops with the message above.

Via the settings GUI:
Once I input the correct smb uri and click browse, I am prompted to enter Username, Domain, and Password. I cannot get past this point and I suspect the problem is either knowing the formatting of the Username or knowing what Domain to input (since the password is surely correct).

Username: I have tried

username
username@employer
employer\username
employer\username@employer

anything else I could try?
(username here is username on employer shared computers, not my local user name)

Domain: it automatically comes up as WORKGROUP. I have tried USER. I don't know what else to try.

Any suggestions at all? It feels like this should be perfectly simple.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,806

Re: Authenticating SAMBA network printer

employer shared computers

Is your employer running windows computers / the printer server in an Active Directory environment ?

If so, you may have to setup Kerberos authentication / AD integration .

Last edited by Lone_Wolf (2026-02-11 13:33:36)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

VictorSerge

Member

Registered: 2025-06-22

Posts: 6

Re: Authenticating SAMBA network printer

Is your employer running windows computers / the printer server in an Active Directory environment ?

Possibly. That would be a strange thing for them to change and then deny changing, though. I suppose there might have been an update to the server relevant to AD management.

If so, you may have to setup Kerberos authentication / AD integration .

This looks like something of a learning curve, but I'll look into it when I next have a spare afternoon. Even if it doesn't solve the problem, it'll be good for the soul. Thanks.