Dave Liquorice wrote:
On Thu, 30 Jul 2020 17:33:45 +0100, Andy Burns wrote:

Googled lots of times. Everyone has a different answer.

That's always a problem with windows, too many "experts" and you end
up with the blind leading the blind.

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.

Also check that all devices are in the same "workgroup" or whatever
they call it now...


This is just for fun.

http://www.unixwiz.net/tools/nbtscan.html

http://www.unixwiz.net/tools/nbtscan-1.0.35.exe

nbtscan 192.168.1.0/24

192.168.1.101 WORKGROUP\BOB SHARING
192.168.1.102 WORKGROUP\BLUEWAVE SHARING
*timeout (normal end of scan)

That allows a survey, to see what has registered
with a particular protocol. There's more than one nameserver
in Windows, and it's outside my payscale to dissect this
stuff.

But you can start with something like that for a look.

Both machines above have workgroup=WORKGROUP, so BOB should see
BLUEWAVE and vice versa. The Windows 10 machines can
benefit from at least having the two services.msc
with "Function" as the first word in the name.
One of the Function ones seems to be a nameserver
of some sort.

And for Windows 10 to see Windows XP machines, needs SMBV1
turned on in Programs and Features : Windows Features.

Paul