Dave Plowman (News) wrote:
In article ,
Adrian Caspersz wrote:
On 31/07/2020 14:37, Dave Plowman (News) wrote:
But I'd say it's a red herring.

Googled lots of times. Everyone has a different answer.

Only network geeks can use the diagnostics, understand the output and
fix the problem. The rest are wannabes, born somewhere to the left of
us, littering the internet with junk posts guaranteed to confuse. It's
hopeless.

None of which seems to have made any difference. Some can see
another, but not the other way. Some show another on the network,
but aren't allowed access.
"see" at what level? ping is the starting point, you might need to
enable it through firewalls, once everything can ping everything else,
move up to SMB/CIFS sharing. If you try to use file shares first it's
running before the network can walk.
You can't actually ping things with Win 10.


Try putting a -4 in the command

ping -4 192.168.1.33

if that works, then blame iPv6.

iPv6 disabled long ago. ;-)

IPV6 necessary for HomeGroups.

There are a number of recipes on the web for disabling
IPV6, some of which are wrong. There is a Microsoft webpage
warning about this.

The machine you're trying to ping, does not have to
answer if all of ICMP is disabled. The email machine
of my ISP, has ICMP disabled. It's not always a firewall
that stops it. The foreign host might simply not be listening
due to internal settings. I can't ping the ISP Email server.

I disable IPV6 here, by using an IPV4-only router. If a
machine wanted to, it could use Teredo Tunneling to
push IPV6 through the IPV4 router. But at least the IPV4
router prevents the "chatty bits" of IPV6 through.

Paul