Only one of two Windows 10 machines can connect to XP machine

I have an XP Machine that has several shared resources (USB Drives, partitions, folders, etc.) and have had an XP LAN for years. I want to be able to access the shared resources from two other Windows 10 machines.

Problem: The Acer (Win 10 Home) can see shared resources on the Surface (Win 10 Pro), but CANNOT see ANY of the shared resources on the Gateway (Windows XP Pro). The Surface can see ALL shared resources on the Gateway and shared resources on the Acer.

The rule, as I understand it is that all computers must be in the same workgroup. They aren't. The 2 Win 10 machines are in a workgroup called WORKGROUP, and the XP machine is in a workgroup called HOME. Yet the Surface can see shared resourced on the Gateway which is in a different workgroup.

How can I get the Acer to see the same resources (ostensibly across workgroups) as the Surface?

SMB 1.0 File sharing support is enabled on the Surface; enabling it on the Acer did not solve the problem. I don't even know where to start. Any suggestions would be appreciated.

Welcome to the forum. It must be xp home as that ises home as the workgroup change it to workgroup and then it should work

How to change your Computer Name (or Workgroup) in Windows XP

Samuria said:

Welcome to the forum. It must be xp home as that ises home as the workgroup change it to workgroup and then it should work

How to change your Computer Name (or Workgroup) in Windows XP

Yeah, that was my first instinct before I posted. But that Surface machine can see ALL the resources on the XP machine and they are in different workgroups - if I change the workgroup on the XP machine, I'm afraid that I'll perturb the long established drive mappings and other references to those shares (Surface can see XP).

So why can one Windows 10 machine see the resources in another workgroup, but another Windows 10 machine can't?

Run this on the pc that cant see xp does this see it NetBScanner - NetBIOS scanner

Silky said:

SMB 1.0 File sharing support is enabled on the Surface; enabling it on the Acer did not solve the problem...

Specifically, in order to connect to an XP machine it is the 'SMB 1.0/CIFS Client' that must be enabled.

Samuria said:

Run this on the pc that cant see xp does this see it NetBScanner - NetBIOS scanner

Yeppers. NetBIOS Scanner sees the other win 10 AND the XP machine, as run from the machine that cannot see it in "Network" (File explorer)

Bree said:

Specifically, in order to connect to an XP machine it is the 'SMB 1.0/CIFS Client' that must be enabled.

Thanks for the help. I did that before I posted. It IS enabled.

If the scanner can see it can you map a drive to it via ip or name if not what errors do you get

Samuria said:

If the scanner can see it can you map a drive to it via ip or name if not what errors do you get

Okay, head scratcher... right after I ran NetBIOS Scanner, that XP computer is showing up in Network. I don't get it, but, I guess the problem is gone.

I appreciate your speedy help.

The scanner often kick things into life