Hello. So far I’ve been connecting to Samsung ML-2165W printer, without any problems. Recently, my computer have lost the connection with the printer, and any attempts are cut by messages of Cups and Yast, that adding printer is forbidden or acquiring devices list is forbidden (for sure I enter proper username and password). Printer’s diode is displaying stable blue light, meaning that it has connection with the router. Restarting all three devices doesn’t help. Can anyone share advice?
Please show us the CUPS printer status and URI…
lpstat -t
From that information we can guide you further.
Can you ping the printer by its assigned IP address? If you’re not sure about the current IP address, you could examine the router (via its admin web interface) and it should show a list of connected devices. If using DHCP, it may be that the printer IP address changed. This can be avoided by reserving IP addresses (DHCP reservation) for a given device in the router configuration.
Some great advice already mentioned.
Just a thought. Have you changed any Firewall settings recently?
Here it goes:
sim@localhost:~> lpstat -t
scheduler is running
no system default destination
lpstat: No destinations added.
lpstat: No destinations added.
lpstat: No destinations added.
lpstat: No destinations added.
sim@localhost:~>
sim@localhost:~> ping 192.169.0.16
PING 192.169.0.16 (192.169.0.16) 56(84) bytes of data.
^C
--- 192.169.0.16 ping statistics ---
34 packets transmitted, 0 received, 100% packet loss, time 33783ms
sim@localhost:~> ^C
The URI is: ipp://192.168.0.16/ipp/printer
No.
Only one thought - some time ago I installed some additional HP software to handle another device, printer+scanner HP. Not sure if wifi printer lost connection prior to that or after…
No printer is currently defined. Somehow you have deleted it.
To configure it via the CUPS web interface, you’ll need to use the root credentials.
Since you didn’t get a response from that IP address, you should check connectivity via the router admin web interface. You may need to take steps to configure such that the assigned IP address doesn’t change as explained already.
Make sure your router’s DHCP server works properly. Host 3400G has no printers installed, but I can submit jobs to the printers. They get their address from the router, e.g. the Brother laser printerHL-L2350DW:
**3400G:~ #** nslookup BRW1CBFC0D1EA86
Server: 192.168.178.1
Address: 192.168.178.1#53
Name: BRW1CBFC0D1EA86
Address: 192.168.178.20
**3400G:~ #**
On host 3400G I configured remote printing using ‘yast2 printer’. As user karl I configured using lpoptions. Lpstat displays settings:
karl@3400G:~> LANG=C lpstat -t
scheduler is running
system default destination: MFC255CW
device for HLL2350DW: lpd://BRW1CBFC0D1EA86/BINARY_P1
device for MFC255CW: lpd://BRWC417FEB49788/BINARY_P1
HLL2350DW accepting requests since Mon May 17 18:56:16 2021
MFC255CW accepting requests since Mon Apr 12 14:04:36 2021
printer HLL2350DW is idle. enabled since Mon May 17 18:56:16 2021
printer MFC255CW is idle. enabled since Mon Apr 12 14:04:36 2021
karl@3400G:~> cat ~/.cups/lpoptions
Default MFC255CW
karl@3400G:~>
I tried assigning fixed addresses but stopped doing so when I experienced numerous issues. What works best for most home networks, in my experience of course:
- hosts use fixed (static) host names
- devices (links) get their arbitrary addresses from the DHCP server of the router
I strictly refrain from tinkering. Hosts change their addresses every now and then, but this doesn’t cause any issues.
DHCP reservation effectively delivers static IP addressing (but within the DHCP address space). Of course hostnames can also be employed, but DNS not in common use in home networks. Avahi hostnames are another option, but for now I would prefer to keep things simple for the OP.
What you call tinkering others may call configuration. 
When experiencing frequent issues with wicked since March 2014 I tried systemd-netword fixed IP addresses: Systemd-networkd - openSUSE Wiki This turned out to work reliably, but was cumbersome when making changes.
I always wondered why net installers of any distribution would readily connect to their repositories without tedious manual configuration. I gave DHCP a try: Network Management With Systemd - openSUSE Wiki Yes, still some configuration is needed, but it’s concise and changes are rarely needed. Host erlangen currently has a single link:
**erlangen:~ #** cat /etc/systemd/network/20-wired.network
[Match]
Name=e*
[Network]
DHCP=yes
**erlangen:~ #**
**erlangen:~ #** networkctl status
**●** State: **routable **
Address: 192.168.178.32 on enp0s31f6
f123:.................... on enp0s31f6
f123:.................... on enp0s31f6
Gateway: 192.168.178.1 (AVM GmbH) on enp0s31f6
f123:..................... (AVM GmbH) on enp0s31f6
DNS: 192.168.178.1
NTP: 192.168.178.1
May 21 12:24:53 erlangen systemd[1]: Starting Network Service...
May 21 12:24:54 erlangen systemd-networkd[621]: Enumeration completed
May 21 12:24:54 erlangen systemd[1]: Started Network Service.
May 21 12:24:54 erlangen systemd-networkd[621]: eth0: Interface name change detected, eth0 has been renamed to enp0s31f6.
May 21 12:24:54 erlangen systemd-networkd[621]: enp0s31f6: IPv6 successfully enabled
May 21 12:24:54 erlangen systemd-networkd[621]: enp0s31f6: Link UP
May 21 12:25:04 erlangen systemd-networkd[621]: enp0s31f6: Gained carrier
May 21 12:25:05 erlangen systemd-networkd[621]: enp0s31f6: DHCPv4 address 192.168.178.32/24 via 192.168.178.1
May 21 12:25:06 erlangen systemd-networkd[621]: enp0s31f6: Gained IPv6LL
**erlangen:~ #**
None of this is relevant to this thread! This relates to printer configuration.
Address 192.169.0.16 is located in Bainbridge Island, Washington, United States of America.
You need to test 192.168.0.16.
Oh, thank you, I don’t know how it happened… Here it goes:
sim@localhost:~> ping 192.168.0.16
PING 192.168.0.16 (192.168.0.16) 56(84) bytes of data.
From 192.168.0.12 icmp_seq=1 Destination Host Unreachable
From 192.168.0.12 icmp_seq=2 Destination Host Unreachable
From 192.168.0.12 icmp_seq=3 Destination Host Unreachable
From 192.168.0.12 icmp_seq=4 Destination Host Unreachable
From 192.168.0.12 icmp_seq=5 Destination Host Unreachable
From 192.168.0.12 icmp_seq=6 Destination Host Unreachable
From 192.168.0.12 icmp_seq=7 Destination Host Unreachable
From 192.168.0.12 icmp_seq=8 Destination Host Unreachable
From 192.168.0.12 icmp_seq=9 Destination Host Unreachable
From 192.168.0.12 icmp_seq=10 Destination Host Unreachable
From 192.168.0.12 icmp_seq=11 Destination Host Unreachable
From 192.168.0.12 icmp_seq=12 Destination Host Unreachable
^C
--- 192.168.0.16 ping statistics ---
15 packets transmitted, 0 received, +12 errors, 100% packet loss, time 14312ms
pipe 4
sim@localhost:~>
192.168.0.12 as gateway? Not 192.168.0.1?
Check printer settings with USB connection.
ILL network settings are broken.
The OP was attempting to ping the IP address of the printer as per my request in post #2.
@sim: Please post output of the following commands
ip address
ip route
sim@localhost:~> ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether a8:a1:59:1a:88:51 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ec:08:6b:11:79:fc brd ff:ff:ff:ff:ff:ff
inet 192.168.0.12/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
valid_lft 84379sec preferred_lft 84379sec
inet6 fe80::953d:cf8a:cb5b:1a55/64 scope link noprefixroute
valid_lft forever preferred_lft forever
sim@localhost:~> ip route
default via 192.168.0.1 dev wlan0 proto dhcp metric 600
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.12 metric 600
sim@localhost:~>
Ok, so this confirms that you’re connected to a network (192.168.0.0/24). You need to verify that the printer is connected to your wifi and that a valid IP address is assigned. Check your router via its web interface as already mentioned.
It is - when I print printer’s information page (by pressing its button for 10 sec), it gives information that the printer is connected to the router and the quality of connection is good.
I’d be interested in what information you can provide from the router about connected devices and assigned IP addresses.
And again. Your firewall in Leap?
It might be worth turning it off, at least for some diagnostics
Most routers have a firewall built in to protect you from the outside world, so it’s not a big issue