[SOLVED] Samsung SL-C430W refuses to print test page USB/Ethernet/WiFi Debian 10.
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hmmm. Interesting. I assumed that the IP address was static on the printer, from when I set it in Win 10. However:
Code:
$ ping SEC8425197B7B79.local
PING SEC8425197B7B79.local (192.168.0.103) 56(84) bytes of data.
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=1 ttl=64 time=14.9 ms
64 bytes from 192.168.0.103 (192.168.0.103): icmp_seq=2 ttl=64 time=2.36 ms
Code:
$ ping 192.168.0.103
PING 192.168.0.103 (192.168.0.103) 56(84) bytes of data.
64 bytes from 192.168.0.103: icmp_seq=1 ttl=64 time=4.64 ms
64 bytes from 192.168.0.103: icmp_seq=2 ttl=64 time=2.57 ms
64 bytes from 192.168.0.103: icmp_seq=3 ttl=64 time=4.33 ms
Ok, that reads like progress, so the VPN was the cause of this connectivity issue.
FWIW, many admins prefer assigning static IP addresses to printers (and other peripheral devices) on the LAN. However, if you manage the DHCP server (often provided by the router in SOHO environments), then best to leave the printer as DHCP assigned address, and use IP address reservation in the router itself. Easier to manage from one place than from each device.
I received a message from bchemnet, that runs the Samsung Unified Linux Driver Repository, regarding my issue:
I have CUPS 2.2.10-6+deb10u4 installed on my system. I know that the devs at MXLinux patched their own solution from Debian testing, so I (possibly incorrectly) assume that getting the relevant commit backported isn't an option, so how do I manually update CUPS to 2.2.12? I couldn't find it in buster-backports and testing has 2.3.3op1-7...
The gist is that CUPS is making changes that are not compatible with the Samsung drivers. CUPS 2.2.11 has recently been patched to restore working behavior for Samsung printers, but there is no guarantee that will remain true. Debian inherited the problematic change in 2.2.10-4 and it may remain as of 2.2.10-6. If you are using a Debian-based distribution and still have this problem, report it to the bug tracker and reference the CUPS issue above.
The gist is that printers that do not use IPP, and/or that use custom drivers such as the Samsung driver, and at risk of no longer working after CUPS 2.3 is released (although they will likely continue working for some unknown amount of time after the initial release). Some of the newer Samsung-branded printers support IPP, so will not necessarily be affected by the changes. I do not know what the long-term implications are for continuing to provide this repository and the associated drivers.
Now (without the VPN active), what is reported by lpstat?
Code:
lpstat -t
Code:
$ lpstat -t
scheduler is running
system default destination: Samsung_C43x_Series_SEC8425197B7B79_
device for Samsung_C43x_Series_SEC8425197B7B79_: ipp://SEC8425197B7B79.local:631/ipp/print
Samsung_C43x_Series_SEC8425197B7B79_ accepting requests since Sun 07 Feb 2021 11:27:45 AM EET
printer Samsung_C43x_Series_SEC8425197B7B79_ is idle. enabled since Sun 07 Feb 2021 11:27:45 AM EET
Quote:
Originally Posted by ferrari
Also, can you now print a test page successfully?
Yes, although I get the following errors when I open "print settings - localhost":
Code:
Option 'orientation-requested' has value '0' and cannot be edited.
Option 'print-quality' has value '0' and cannot be edited.
$ lpstat -t
scheduler is running
system default destination: Samsung_C43x_Series_SEC8425197B7B79_
device for Samsung_C43x_Series_SEC8425197B7B79_: ipp://SEC8425197B7B79.local:631/ipp/print
Samsung_C43x_Series_SEC8425197B7B79_ accepting requests since Sun 07 Feb 2021 11:27:45 AM EET
printer Samsung_C43x_Series_SEC8425197B7B79_ is idle. enabled since Sun 07 Feb 2021 11:27:45 AM EET
Yes, although I get the following errors when I open "print settings - localhost":
Code:
Option 'orientation-requested' has value '0' and cannot be edited.
Option 'print-quality' has value '0' and cannot be edited.
As long as the print job is successful, is that really a problem though?
As long as the print job is successful, is that really a problem though?
No. To recap, here is where I am at. I have reconfigured my firewall so that I can successfully print either using WiFi or Ethernet without any problems. However, my VPN blocks contact to my printer either using WiFi or Ethernet. I have tried
Code:
$ nordvpn whitelist add subnet 192.168.0.0/24
but now I get
Code:
$ ping SEC8425197B7B79.local
ping: SEC8425197B7B79.local: Name or service not known
rather than
Code:
$ ping SEC8425197B7B79.local
PING SEC8425197B7B79.local (192.168.0.103) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
Not sure what to do about that, and I need my VPN enabled, whenever my computer is on. With the printer connected to my computer with a USB cable, I continue to get an SPL ERROR: 11-1114 error code.
OK, got it. The problem was that I had used a different whitelist configuration, removed it, and then used the above command to add to the whitelist, and didn't reboot before I tried pinging again. Now that I have rebooted the system, everything seems to be working fine when using WiFi or Ethernet. I have my firewall, I have my VPN and I can print. No USB connection, but I can live with this. I will mark this solved. Thanks for all the help, ferrari.
Last edited by globetrotterdk; 02-07-2021 at 07:34 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.