"Destination Host Unreachable" when two computers ping each other ipv4

Hi. I was trying to ssh from OpenSSH client Windows 10 PowerShell to Fedora 36 Server Minimal Install but it returned Reply from 192.168.1.4: Destination host unreachable.. Then I proceeded to ping both ways. Note that:

  • PC1 is running Fedora 36 and PC2 Windows 10.
  • Both connected through Ethernet to modem/router Technicolor CGA0112, DHCP DOUBLESTACK.
  • Both can ping other devices on the LAN and their default gateway which is the same.
  • Neither shows the other one in arp.
  • Disabled firewalls and restarted network interface settings on both.

And still “Destination Host Unreachable”

Thank you in advance.

Edit : Also switched connection to RJ45’s (modem/router has only two). Reseted the modem/router and still “Destination Host Unreachable”, only Windows 10 ipv4 changed.

Are you sure that you’re pinging/reaching out to the correct IP Address? Also, are you sure devices are on the same VLAN?

Could you provide ipconfig/ip informations about IP assignment, routes, and anything that might be relevant from the networking side?

PS C:\Windows\system32> ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : DESKTOP-Q7RCPLD
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
   Physical Address. . . . . . . . . : 1C-1B-0D-C2-CB-D1
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2803:2d60:1118:443::2(Preferred)
   Lease Obtained. . . . . . . . . . : jueves, 23 de junio de 2022 20:45:50
   Lease Expires . . . . . . . . . . : martes, 28 de junio de 2022 20:45:50
   IPv6 Address. . . . . . . . . . . : 2803:2d60:1118:443:d9ea:9c2b:b2a0:a6f0(Preferred)
   Temporary IPv6 Address. . . . . . : 2803:2d60:1118:443:a00a:e298:19c2:6d4f(Preferred)
   Link-local IPv6 Address . . . . . : fe80::d9ea:9c2b:b2a0:a6f0%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : jueves, 23 de junio de 2022 20:44:46
   Lease Expires . . . . . . . . . . : sábado, 25 de junio de 2022 04:27:55
   Default Gateway . . . . . . . . . : fe80::5a96:30ff:fe73:2df9%20
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 337386253
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-C7-11-C5-1C-1B-0D-C2-CB-D1
   DNS Servers . . . . . . . . . . . : 2800:98:0:4::4
                                       2803:3400:4::2c
                                       190.184.56.72
                                       216.230.139.8
                                       2800:98:0:4::4
                                       2803:3400:4::2c
   NetBIOS over Tcpip. . . . . . . . : Enabled

and nmcli device show

GENERAL.DEVICE:                         enp2s0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         D4:3D:7E:36:88:D9
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     enp2s0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         192.168.1.13/24
IP4.GATEWAY:                            192.168.1.1
IP4.ROUTE[1]:                           dst = 192.168.1.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 100
IP4.DNS[1]:                             190.184.56.72
IP4.DNS[2]:                             216.230.139.8
IP6.ADDRESS[1]:                         2803:2d60:1118:443::1/128
IP6.ADDRESS[2]:                         2803:2d60:1118:443:d63d:7eff:fe36:88d9/64
IP6.ADDRESS[3]:                         fe80::d63d:7eff:fe36:88d9/64
IP6.GATEWAY:                            fe80::5a96:30ff:fe73:2df9
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 1024
IP6.ROUTE[2]:                           dst = 2803:2d60:1118:443::/64, nh = fe80::5a96:30ff:fe73:2df9, mt = 100
IP6.ROUTE[3]:                           dst = ::/0, nh = fe80::5a96:30ff:fe73:2df9, mt = 100
IP6.ROUTE[4]:                           dst = 2803:2d60:1118:443::1/128, nh = ::, mt = 100
IP6.DNS[1]:                             2800:98:0:4::4
IP6.DNS[2]:                             2803:3400:4::2c

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ::1/128, nh = ::, mt = 256

Yes I am sure I’m using the correct IP Address. Both are physically connected to the router/modem.

PS C:\Windows\system32> arp -a

Interface: 192.168.1.2 --- 0x14
  Internet Address      Physical Address      Type
  192.168.1.1           58-96-30-73-2d-f9     dynamic
  192.168.1.6           3e-3e-a4-02-67-8a     dynamic
  192.168.1.12          70-18-8b-62-b2-ee     dynamic
  192.168.1.255         ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.251           01-00-5e-00-00-fb     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static
  255.255.255.255       ff-ff-ff-ff-ff-ff     static

other one

arp scan --localnet

Interface: enp2s0, type: EN10MB, MAC: d4:3d:7e:36:88:d9, IPv4: 192.168.1.13
Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan)
192.168.1.1	58:96:30:73:2d:f9	Technicolor CH USA Inc.
192.168.1.3	c0:25:67:be:bd:6c	Nexxt Solutions
192.168.1.5	c0:25:67:be:bd:6c	Nexxt Solutions
192.168.1.12	70:18:8b:62:b2:ee	Hon Hai Precision Ind. Co.,Ltd.
192.168.1.4	d8:f1:5b:ba:68:7a	Espressif Inc.
192.168.1.8	a6:23:44:47:4e:05	(Unknown: locally administered)
192.168.1.6	3e:3e:a4:02:67:8a	(Unknown: locally administered)
192.168.1.18	d8:b0:53:32:5b:e7	(Unknown)

8 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.9.7: 256 hosts scanned in 2.197 seconds (116.52 hosts/sec). 8 responded

A temporary solution; connected Linksys E2500 router to Technicolor CGA0112 Internet then connected through ethernet both PC1, PC2 and everything goes well.

So yeah, as you mentioned, PC1 (.2) doesn’t have .4 in the ARP table, so doesn’t know how to reach it. My only guess is that they’re in fact on different vlans and thus don’t see each other.

Which is also weird because they both see .6 and .12 machines, whatever those are.

My guess is something with that particular router since adding new one eliminated the issue, but what, I am clueless :person_shrugging: :cry: