Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #234013 > unrolled thread

ping gateway ok, ping any other local network address fails

Back to article view | Back to linux.debian.user

Contents

  ping gateway ok, ping any other local network address fails rudu <rudu@cegetel.net> - 2021-04-09 12:00 +0200
    Re: ping gateway ok, ping any other local network address fails "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-04-09 12:10 +0200
      Re: ping gateway ok, ping any other local network address fails rudu <rudu@cegetel.net> - 2021-04-09 16:10 +0200
        Re: ping gateway ok, ping any other local network address fails "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-04-09 17:00 +0200
          Re: ping gateway ok, ping any other local network address fails deloptes <deloptes@gmail.com> - 2021-04-09 18:40 +0200
            Re: ping gateway ok, ping any other local network address fails "Alexander V. Makartsev" <avbetev@gmail.com> - 2021-04-09 22:10 +0200
        Re: ping gateway ok, ping any other local network address fails Lee <ler762@gmail.com> - 2021-04-09 22:30 +0200
        Re: ping gateway ok, ping any other local network address fails Mart van de Wege <mart@vdwege.eu> - 2021-04-10 13:00 +0200
    Re: ping gateway ok, ping any other local network address fails Henning Follmann <hfollmann@itcfollmann.com> - 2021-04-09 16:10 +0200
    Re: ping gateway ok, ping any other local network address fails Andrei POPESCU <andreimpopescu@gmail.com> - 2021-04-09 20:30 +0200

#234013 — ping gateway ok, ping any other local network address fails

Hi,

First, I tried to understand why a single machine among others couldn't 
print on the local printer.
So I tried to ping the printer and it failed.
The machine could nevertheless surf the web with no problem ...

I paste here a few commands I passed when remotely connected to the 
problematic machine (sorry for the french locale).
What should I check next ? Ideas ?

Thanks


$ /sbin/ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.1.50  netmask 255.255.255.0  broadcast 192.168.1.255
         inet6 fe80::f67f:8a2c:e338:3db4  prefixlen 64  scopeid 0x20<link>
         ether d0:50:99:7a:ae:6f  txqueuelen 1000  (Ethernet)
         RX packets 26166  bytes 6940725 (6.9 MB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 33708  bytes 29316822 (29.3 MB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
         inet 127.0.0.1  netmask 255.0.0.0
         inet6 ::1  prefixlen 128  scopeid 0x10<host>
         loop  txqueuelen 1000  (Boucle locale)
         RX packets 513  bytes 48788 (48.7 KB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 513  bytes 48788 (48.7 KB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ ping -c 4 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 octets de 192.168.1.1 : icmp_seq=1 ttl=64 temps=0.468 ms
64 octets de 192.168.1.1 : icmp_seq=2 ttl=64 temps=0.435 ms
64 octets de 192.168.1.1 : icmp_seq=3 ttl=64 temps=0.445 ms
64 octets de 192.168.1.1 : icmp_seq=4 ttl=64 temps=0.427 ms

--- statistiques ping 192.168.1.1 ---
4 paquets transmis, 4 reçus, 0 % paquets perdus, temps 3068 ms
rtt min/avg/max/mdev = 0.427/0.443/0.468/0.015 ms


$ ping -c 4 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
De 192.168.1.50 icmp_seq=1 Hôte de destination injoignable
De 192.168.1.50 icmp_seq=2 Hôte de destination injoignable
De 192.168.1.50 icmp_seq=3 Hôte de destination injoignable
De 192.168.1.50 icmp_seq=4 Hôte de destination injoignable

--- statistiques ping 192.168.1.20 ---
4 paquets transmis, 0 reçus, +4 erreurs, 100 % paquets perdus, temps 3048 ms
  tuyau 3



$ netstat -r
Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic   MSS Fenêtre irtt 
Iface
default         msbr.home       0.0.0.0         UG        0 0          0 
enp2s0
link-local      0.0.0.0         255.255.0.0     U         0 0          0 
enp2s0
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 
enp2s0


$ ping -c 4 msbr.home
PING msbr.home (192.168.1.1) 56(84) bytes of data.
64 octets de msbr.home (192.168.1.1) : icmp_seq=1 ttl=64 temps=0.412 ms
64 octets de msbr.home (192.168.1.1) : icmp_seq=2 ttl=64 temps=0.447 ms
64 octets de msbr.home (192.168.1.1) : icmp_seq=3 ttl=64 temps=0.415 ms
64 octets de msbr.home (192.168.1.1) : icmp_seq=4 ttl=64 temps=0.436 ms

--- statistiques ping msbr.home ---
4 paquets transmis, 4 reçus, 0 % paquets perdus, temps 3059 ms
rtt min/avg/max/mdev = 0.412/0.427/0.447/0.014 ms


$ sudo iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
  pkts bytes target     prot opt in     out     source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
  pkts bytes target     prot opt in     out     source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
  pkts bytes target     prot opt in     out     source destination


$ groups
administration adm cdrom sudo dip plugdev lpadmin sambashare

[toc] | [next] | [standalone]

#234014

[Multipart message — attachments visible in raw view] — view raw

On 09.04.2021 14:41, rudu wrote:
> Hi,
>
> First, I tried to understand why a single machine among others 
> couldn't print on the local printer.
> So I tried to ping the printer and it failed.
> The machine could nevertheless surf the web with no problem ...
>
> I paste here a few commands I passed when remotely connected to the 
> problematic machine (sorry for the french locale).
> What should I check next ? Ideas ?
>
It looks like your printer could be mis-configured.

What is make\model of your printer?
How printer was connected to your local area network (using Switch or 
Router)?
What method have you used to configure IP address of the printer?
Usually, network settings could be verified by printing a special 
settings report page.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

[toc] | [prev] | [next] | [standalone]

#234033

Le 09/04/2021 à 12:08, Alexander V. Makartsev a écrit :
> On 09.04.2021 14:41, rudu wrote:
>> Hi,
>>
>> First, I tried to understand why a single machine among others 
>> couldn't print on the local printer.
>> So I tried to ping the printer and it failed.
>> The machine could nevertheless surf the web with no problem ...
>>
>> I paste here a few commands I passed when remotely connected to the 
>> problematic machine (sorry for the french locale).
>> What should I check next ? Ideas ?
>>
> It looks like your printer could be mis-configured.
>
> What is make\model of your printer?
> How printer was connected to your local area network (using Switch or 
> Router)?
> What method have you used to configure IP address of the printer?
> Usually, network settings could be verified by printing a special 
> settings report page.

Thanks for your help Alexander,

To configure the printer, I first have to be able to ping it on the 
local network, which every over computer can do.
And they can print all right, so this desktop must have some network 
misconfiguration of some sort, I guess ...
It seems like trapped into a tunnel toward the gateway/router to get 
out, but can't shake hands with a pal next door.
I first suspected a firewall rule of some sort, but there's none.

I had to investigate remotely as I can't physically access the machine, 
so until I can have another chance (the lock-down situation here doesn't 
help) I'm gathering hints and ideas.

Rudu

[toc] | [prev] | [next] | [standalone]

#234041

[Multipart message — attachments visible in raw view] — view raw

On 09.04.2021 19:09, rudu wrote:
> Le 09/04/2021 à 12:08, Alexander V. Makartsev a écrit :
>> On 09.04.2021 14:41, rudu wrote:
>>> Hi,
>>>
>>> First, I tried to understand why a single machine among others 
>>> couldn't print on the local printer.
>>> So I tried to ping the printer and it failed.
>>> The machine could nevertheless surf the web with no problem ...
>>>
>>> I paste here a few commands I passed when remotely connected to the 
>>> problematic machine (sorry for the french locale).
>>> What should I check next ? Ideas ?
>>>
>> It looks like your printer could be mis-configured.
>>
>> What is make\model of your printer?
>> How printer was connected to your local area network (using Switch or 
>> Router)?
>> What method have you used to configure IP address of the printer?
>> Usually, network settings could be verified by printing a special 
>> settings report page.
>
> Thanks for your help Alexander,
>
> To configure the printer, I first have to be able to ping it on the 
> local network, which every over computer can do.
Do you have remote access to another computer on the same local network 
to confirm that printer's IP address is "192.168.1.20", as you expect, 
and it responds to ping command from another computer?

Please answer other questions I asked:
1. What is make\model of your printer?
2. Is your printer connected to another PC using USB cable, or is it 
connected directly to the local network using a network cable (RJ-45 
patch cord), or is it connected using wireless connection?
3. How was IP address "192.168.1.20" assigned initially to it? (Ex. 
Using physical screen and buttons on the printer itself, or it was 
configured automatically)

> And they can print all right, so this desktop must have some network 
> misconfiguration of some sort, I guess ...
> It seems like trapped into a tunnel toward the gateway/router to get 
> out, but can't shake hands with a pal next door.
> I first suspected a firewall rule of some sort, but there's none.
>
> I had to investigate remotely as I can't physically access the 
> machine, so until I can have another chance (the lock-down situation 
> here doesn't help) I'm gathering hints and ideas.
I don't see any reason why your computer could not ping the printer, 
since you can ping gateway IP and access the Internet from it.
I suspect printer's IP address has changed somehow, or it is in powered 
off state (some printers can power off themselves, if they were not used 
for a set period of time).

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

[toc] | [prev] | [next] | [standalone]

#234046

Alexander V. Makartsev wrote:

> I don't see any reason why your computer could not ping the printer,
> since you can ping gateway IP and access the Internet from it.
> I suspect printer's IP address has changed somehow, or it is in powered
> off state (some printers can power off themselves, if they were not used
> for a set period of time).

if netmask is /32 or /30 ?

[toc] | [prev] | [next] | [standalone]

#234060

[Multipart message — attachments visible in raw view] — view raw

On 09.04.2021 21:37, deloptes wrote:
> Alexander V. Makartsev wrote:
>
>> I don't see any reason why your computer could not ping the printer,
>> since you can ping gateway IP and access the Internet from it.
>> I suspect printer's IP address has changed somehow, or it is in powered
>> off state (some printers can power off themselves, if they were not used
>> for a set period of time).
> if netmask is /32 or /30 ?
>
https://lists.debian.org/debian-user/2021/04/msg00260.html

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

[toc] | [prev] | [next] | [standalone]

#234062

On 4/9/21, rudu <rudu@cegetel.net> wrote:
>
> To configure the printer, I first have to be able to ping it on the
> local network, which every over computer can do.
> And they can print all right, so this desktop must have some network
> misconfiguration of some sort, I guess ...
> It seems like trapped into a tunnel toward the gateway/router to get
> out, but can't shake hands with a pal next door.
> I first suspected a firewall rule of some sort, but there's none.
>
> I had to investigate remotely as I can't physically access the machine,
> so until I can have another chance (the lock-down situation here doesn't
> help) I'm gathering hints and ideas.

netstat -nr
  because your earlier
$ netstat -r
Table de routage IP du noyau
Destination     Passerelle      Genmask         Indic   MSS Fenêtre irtt Iface
default         msbr.home       0.0.0.0         UG        0 0          0 enp2s0

looks a bit strange (msbr.home for the default gateway??)  And

arp -n
after pinging the printer to see if you got an answer to your arp or no

Lee

[toc] | [prev] | [next] | [standalone]

#234066

rudu <rudu@cegetel.net> writes:
>
> To configure the printer, I first have to be able to ping it on the
> local network, which every over computer can do.

So all other peers on the LAN can get to the printer.

> And they can print all right, so this desktop must have some network
> misconfiguration of some sort, I guess ...
> It seems like trapped into a tunnel toward the gateway/router to get
> out, but can't shake hands with a pal next door.

If your netmask on both sides of the connection is OK, then the problem
is at the Ethernet level. Your previous output showed a /24 on the
desktop. Can you verify that all the other peers are also in
192.168.1.0/24?

If so, next step should be trying to plug the misbehaving desktop into a
different switch port, assuming 1. you have one free, 2. you can get
someone to do that for you, as you have no physical access yourself (did
I understand that correctly?), and 3. this is a dumb switch that just
forwards between all ports, so any port is fine.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

[toc] | [prev] | [next] | [standalone]

#234034

On Fri, Apr 09, 2021 at 11:41:56AM +0200, rudu wrote:
> Hi,
> 
> First, I tried to understand why a single machine among others couldn't
> print on the local printer.
> So I tried to ping the printer and it failed.
> The machine could nevertheless surf the web with no problem ...
> 
> I paste here a few commands I passed when remotely connected to the
> problematic machine (sorry for the french locale).
> What should I check next ? Ideas ?
>

[..]

What does your network topology look like?


-H


-- 
Henning Follmann           | hfollmann@itcfollmann.com

[toc] | [prev] | [next] | [standalone]

#234055

[Multipart message — attachments visible in raw view] — view raw

On Vi, 09 apr 21, 11:41:56, rudu wrote:
> 
> I paste here a few commands I passed when remotely connected to the
> problematic machine (sorry for the french locale).

You can always prepend 'LANG=C.UTF-8' to get the output in English.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web