[SOLVED] network printer is unreachable

duyinthee · 2021-10-27 09:14:31

I can not set up network printer at work.
In local network, all computers are running Windows except mine running Arch Linux.
While the network printer's ip address is 192.168.0.100, all computers' ip addresses are 192.168.99.xx.
All computers can not ping 192.168.0.100 because theirs are 192.168.99.xx. But all Windows computers can set up the network printer and print.
My computer can not locate the network printer. Avahi does not detect the network printer too.
I have avahi installed and set up localhost resolution properly.

$ systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; vendor preset: disabled)
     Active: active (running) since Wed 2021-10-27 12:07:29 +0630; 3h 19min ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 380 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 9423)
     Memory: 2.1M
        CPU: 1.009s
     CGroup: /system.slice/avahi-daemon.service
             ├─380 "avahi-daemon: running [acerE5mgma.local]"
             └─394 "avahi-daemon: chroot helper"

Oct 27 12:07:29 acerE5mgma avahi-daemon[380]: Network interface enumeration completed.
Oct 27 12:07:29 acerE5mgma avahi-daemon[380]: Registering new address record for ::1 on lo.*.
Oct 27 12:07:29 acerE5mgma avahi-daemon[380]: Registering new address record for 127.0.0.1 on lo.IPv4.
Oct 27 12:07:30 acerE5mgma avahi-daemon[380]: Server startup complete. Host name is acerE5mgma.local. Lo>
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: Joining mDNS multicast group on interface wlp3s0.IPv6 with>
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: New relevant interface wlp3s0.IPv6 for mDNS.
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: Registering new address record for fe80::66df:d104:488a:8b>
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: Joining mDNS multicast group on interface wlp3s0.IPv4 with>
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: New relevant interface wlp3s0.IPv4 for mDNS.
Oct 27 12:07:49 acerE5mgma avahi-daemon[380]: Registering new address record for 192.168.99.90 on wlp3s0>

So, I set up the network printer manually setting URI as

socket://192.168.0.100:9100

It also does not work. In printer properties, there is message that the printer is unreachable.
I also have the driver install. https://aur.archlinux.org/packages/cnrdrvcups-lb/
I followed the wiki too https://wiki.archlinux.org/title/CUPS#Network and https://wiki.archlinux.org/title/CUPS/T … te_printer

So, the difference between ip addresses 192.168.0.100 and 192.168.99.xx is the case? If so, how the windows computers are working well even if they also can not ping 192.168.0.100?
What I am missing?

Thanks ...

Last edited by duyinthee (2021-11-02 11:00:22)

seth · 2021-10-27 12:13:17

While the network printer's ip address is 192.168.0.100, all computers' ip addresses are 192.168.99.xx

* Why is the printer in a different network segment and are you sure about the windows systems reaching it this way?
* What distributes those IPs some dhcp server or do you configure them statically?
* Is there a repeater (in less than repeating mode) involved?
* Is the mdns responder configured properly and does avahi discover the printer? => https://wiki.archlinux.org/title/Avahi

duyinthee · 2021-10-28 03:29:09

thanks for reply and check list.
* yes the windows systems are reaching the network printer this way and why the printer in a different segment is myabe that the office has only one internet line and two large rooms. Only one router can not cover the whole office. So the service man use another router as bridge, is it called "repeater", I don't really understand. I don't know why the service man configure the network printer's ip address (static) in a different segment.
* one thing I forgot to mention is that, previously my linux system was able to print that network printer with ip in a different segment, but since then Avahi didn't detect it so I set up manually like socket://192.168.0.100:9100.
Then, in Oct, I reinstall Arch for some reasons, now I can not set up again the printer.
Yes, I have mdns responder configured.

$ cat /etc/nsswitch.conf
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files

publickey: files

# hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
hosts: files mdns_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

Last edited by duyinthee (2021-10-28 03:32:04)

seth · 2021-10-28 07:35:39

It's not a repeater, but a bridge - it needs to do its bridging job, though.

You said **all** computers are in 192.168.99.0/24?
So the printer is the only device in a different segment?
That seems rather odd.

"Reaching this way" means that the driver really uses that IP to talk to the printer (you mentioned that windows can't ping it either? But the printer might simply not reply to ICMP requests)

Yes, I have mdns responder configured.

And does avahi discover the printer w/ the command in the linked wiki?

What's the output of

ip a; ip r

Can you

ping 192.168.0.1 # we'll assume the "service man" has the bridge there
nmap -Pn 192.168.0.100
tracepath -b 192.168.0.100

duyinthee · 2021-10-28 10:25:37

Avahi does not detect the printer. I run avahi-browser in terminal, the printer is not detected.

$ ip a; ip r
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: enp2s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether f0:76:1c:c0:48:a8 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 70:77:81:33:1f:33 brd ff:ff:ff:ff:ff:ff
    inet 192.168.99.90/24 brd 192.168.99.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 2685sec preferred_lft 2685sec
    inet6 fe80::66df:d104:488a:8bf9/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
default via 192.168.99.1 dev wlp3s0 proto dhcp metric 600
192.168.99.0/24 dev wlp3s0 proto kernel scope link src 192.168.99.90 metric 600

can not ping 192.168.0.1, stuck there.

$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

$ nmap -Pn 192.168.0.100
Starting Nmap 7.92 ( https://nmap.org ) at 2021-10-28 16:50 +0630

$ tracepath -b 192.168.0.100
 1?: [LOCALHOST]                      pmtu 1500
 1:  192.168.99.1 (192.168.99.1)                           6.191ms
 1:  192.168.99.1 (192.168.99.1)                           2.577ms
 2:  10.132.0.1 (10.132.0.1)                               7.699ms
 3:  172.18.87.2 (172.18.87.2)                             8.856ms
 4:  172.17.125.104 (172.17.125.104)                       7.808ms
 5:  no reply
 6:  no reply
 7:  no reply
 8:  no reply
 9:  no reply

You said **all** computers are in 192.168.99.0/24?
So the printer is the only device in a different segment?
That seems rather odd.

Yes.

"Reaching this way" means that the driver really uses that IP to talk to the printer (you mentioned that windows can't ping it either? But the printer might simply not reply to ICMP requests)

yes they also can not ping but can set up the printer and print.

Thanks, anyway.

Last edited by duyinthee (2021-10-28 10:26:17)

duyinthee · 2021-10-28 10:51:52

In system-config-printer, I tested two ip addresses.
one is 192.168.0.100 and 192.168.99.100 is the another.

error message for 192.168.0.100 is

Processing - The printer is unreachable at this time.

the error message for 192.168.99.100 is

Processing - The printer may not exist or is unavailable at this time.

so, I think, the system knows the printer exist at 192.168.0.100 but unreachable.

Last edited by duyinthee (2021-10-28 10:53:40)

seth · 2021-10-28 13:02:06

$ tracepath -b 192.168.0.100
 1?: [LOCALHOST]                      pmtu 1500
 1:  192.168.99.1 (192.168.99.1)                           6.191ms
 1:  192.168.99.1 (192.168.99.1)                           2.577ms
 2:  10.132.0.1 (10.132.0.1)                               7.699ms
 3:  172.18.87.2 (172.18.87.2)                             8.856ms
 4:  172.17.125.104 (172.17.125.104)                       7.808ms

So it's strolling from 192.168.99.0/24 into 10.132.0.0/24 into 172.18.87.0/24 into 172.17.125.0/24 - iow through several private segments but not into 192.168.0.0/24
How do you *KNOW* that the printer is at 192.168.0.100 and can I talk to TheServiceMan™?

For now, let's see what 172.18.87.2 & 172.17.125.104 actually are…

nmap 172.18.87.2 172.17.125.104

duyinthee · 2021-10-29 03:48:09

How do you *KNOW* that the printer is at 192.168.0.100

I can check ip address of that network printer set up which is working in the Windows systems.
TheServiceMan is from internet company, I don't know.

Now, I am Work-From-Home. Once I get the office next week, I will report here the output of

nmap 172.18.87.2 172.17.125.104

Thanks for your helps. I have learned a lot.

seth · 2021-10-29 07:19:21

You can probably check the printers IP at the printer, there's either gonna be a touchscreen or lcd + buttons or you can make it print out its configuration.

duyinthee · 2021-11-02 03:40:02

The output is here

~ $ nmap 172.18.87.2 172.17.125.104
Starting Nmap 7.92 ( https://nmap.org ) at 2021-11-02 10:07 +0630
Nmap scan report for 172.18.87.2
Host is up (0.014s latency).
Not shown: 998 closed tcp ports (conn-refused)
PORT    STATE SERVICE
22/tcp  open  ssh
179/tcp open  bgp

Nmap done: 2 IP addresses (1 host up) scanned in 1.53 seconds

I have the printer, but it has security password to enter system setting.
Thanks...

duyinthee · 2021-11-02 03:44:32

More, I can also ping both of them

 ~ $ ping 172.18.87.2
PING 172.18.87.2 (172.18.87.2) 56(84) bytes of data.
64 bytes from 172.18.87.2: icmp_seq=1 ttl=62 time=9.25 ms
64 bytes from 172.18.87.2: icmp_seq=2 ttl=62 time=7.27 ms
64 bytes from 172.18.87.2: icmp_seq=3 ttl=62 time=6.29 ms
64 bytes from 172.18.87.2: icmp_seq=4 ttl=62 time=21.8 ms
^C
--- 172.18.87.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 6.292/11.149/21.787/6.232 ms
 ~ $ ping 172.17.125.104
PING 172.17.125.104 (172.17.125.104) 56(84) bytes of data.
64 bytes from 172.17.125.104: icmp_seq=1 ttl=61 time=5.89 ms
64 bytes from 172.17.125.104: icmp_seq=2 ttl=61 time=12.6 ms
64 bytes from 172.17.125.104: icmp_seq=3 ttl=61 time=10.2 ms
64 bytes from 172.17.125.104: icmp_seq=4 ttl=61 time=5.44 ms
^C
--- 172.17.125.104 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 5.435/8.528/12.602/2.993 ms

duyinthee · 2021-11-02 03:54:41

I also set up printer with both of IPs.
The setup with

172.18.87.2

says

Processing - The printer may not exist or is unavailable at this time.

The setup with

172.17.125.104

says

Processing - The printer is unreachable at this time.

seth · 2021-11-02 07:28:23

172.18.87.2 is part of the internal routing system, https://en.wikipedia.org/wiki/Border_Gateway_Protocol
172.17.125.104 is a dead end and doesn't respond.

Atm. 192.168.0.0/24 doesn't look like it's a routed network segment.

I have the printer, but it has security password to enter system setting.

You cannot even query the status?
Who has the password? TheServiceMan™ … and maybe anybody inside your office?

Ok, broadsword.

nmap -p9100 -oG ~/scan.gnamp 192.168.0.0/24 192.168.99.0/24 172.17.125.0/24 172.18.87.0/24 10.132.0.0/24

This will scan the network segments that have shown up and the one you claim to hold the printer for port 9100 (jetstream) to see whether *any* host in those networks has the port open and writes the logs into your home system.
The scan can easily take ~30 seconds or so, so git it some time.

duyinthee · 2021-11-02 10:56:52

At last, it is exactly network issue in the office.
I checked all Window systems. They all set up the printer with the ip 192.168.0.100.
Then, I did new printer-set-up in one Windows system with the same ip 192.168.0.100 and tested. Now, it does not work.
So this means that even Windows systems can not print that network printer with new printer setup.
They are only working with old printer-set-up. I don't know why? Maybe because of cache or something in the router's configuration.

So, I called everyone to get the printer's user ID and Password. Finally, I got and check the ip address.
Surprisingly, the ip address is 192.168.99.111. It is on the same subnet with my Arch system.
So, now my Arch is working well with that network printer with the right ip address 192.168.99.111.
But, all the Windows are still printing with the wrong ip address 192.168.0.100.

I reported this network issue to my boss and all colleagues but no one seems interested .

Thanks very much. I learned a lot from this post.

Last edited by duyinthee (2021-11-02 10:58:43)

Arch Linux

#1 2021-10-27 09:14:31

[SOLVED] network printer is unreachable

#2 2021-10-27 12:13:17

Re: [SOLVED] network printer is unreachable

#3 2021-10-28 03:29:09

Re: [SOLVED] network printer is unreachable

#4 2021-10-28 07:35:39

Re: [SOLVED] network printer is unreachable

#5 2021-10-28 10:25:37

Re: [SOLVED] network printer is unreachable

#6 2021-10-28 10:51:52

Re: [SOLVED] network printer is unreachable

#7 2021-10-28 13:02:06

Re: [SOLVED] network printer is unreachable

#8 2021-10-29 03:48:09

Re: [SOLVED] network printer is unreachable

#9 2021-10-29 07:19:21

Re: [SOLVED] network printer is unreachable

#10 2021-11-02 03:40:02

Re: [SOLVED] network printer is unreachable

#11 2021-11-02 03:44:32

Re: [SOLVED] network printer is unreachable

#12 2021-11-02 03:54:41

Re: [SOLVED] network printer is unreachable

#13 2021-11-02 07:28:23

Re: [SOLVED] network printer is unreachable

#14 2021-11-02 10:56:52

Re: [SOLVED] network printer is unreachable

Board footer