Windows 10: Windows 10 Home vs Pro on network: Home won't allow browse shared fldr

can someone help me sort this? I have a bunch of devices on my lan, some by ethernet some wireless.
One Windows 10 Pro desktop, on ethernet, serves all the other devices - at least in theory. Working well, no big issues.
But with my Windows 10 Home edition on a Zenbook, with networking on, network discovery on, public folder shared, I can RDP into the other windows 10 machine just fine, I can map network drives etc. Life's good, right?

With my 'droid, using ES File Manager, I can move files easily between windows 7 machine, Windows 10 desktop, other droids, etc. However, the ONE MACHINE it cannot get coherent is the Zenbook running Windows 10 Home. It simply will not connect with the correct IP and credentials. I can "see" the machine by scanning the network map with the Droid, access it, setup the credentials, but cannot get in. I am wild-guessing the firewall may be blocking but I have no trouble doing what's needed with the other Windows 10 machine, so ...... stumped. Both are fully updated to latest win 10 updates, both are essentially set same way networking-wise to my knowledge.

Anyone have a clue here?

:)

 

home network with windows home and pro

Sharing files and networking is no different in Home vs Pro. There are no special features or bells or whistles in Pro for what you want to do.

 

Windows 10 Home Remote Desktop/ Terminal Services

Hello,

Can you confirm that Windows 10 Home edition cannot use Remote Desktop as a way of remotely accessing a Windows 10 Home because it does not come with a
Terminal Service License? In my experience with Windows 10 Home after an update pushed out in April of 2017, it appears that you need to upgrade to Windows 10 Pro to acquire a Terminal Service license. Is that
true?

If so, how many Terminal Service licenses does Windows 10 Pro allow for vs a server?

Thank you,