Do you know of a free Android SMBv2 (or SMBv3) client?

[arlen holder]

*Do you know of a free Android SMBv2 (or SMBv3) client?*

As far as I can tell, the AndSMB & SyncMe WiFi clients are SMBv1.

According to this article dating from July 20, 201&, Google released a free
SMBv2 and SMBv3 client for Android:
<https://9to5google.com/2017/07/20/android-samba-client-adds-support-for-smbv2-and-v3/>
<https://www.androidpolice.com/2017/07/19/googles-samba-client-android-now-supports-smbv3/>

The client's unique name was com.google.android.sambadocumentsprovider
<https://play.google.com/store/apps/details?id=com.google.android.sambadocumentsprovider>

However, that link no longer exists on Google Play (the APK is all over the
net, but not on Google Play as far as I can tell).
<https://github.com/google/samba-documents-provider>

The problem with opening up SMBv1 on Windows is that it opens security
holes according to this quote in the references above:
"Google released a new app called Android Samba Client on the Play Store
earlier this month, allowing you to mount SMB file shares to the Downloads
or Files app on your Android device. Now, that app has been updated to
support SMBv2 and SMBv3 protocols, crucially expanding the app┬ previous
limitation of only SMBv1.

For those unfamiliar, Samba is a suite of programs for Windows
interoperability made to run on Linux and Unix systems. It uses the
SMB/CIFS protocol to let you access Windows file and print services, and
it┬ stable, secure, and fast. Seeing the app become available earlier this
month was great, but many were disappointed to learn that it only supported
SMBv1.

What┬ wrong with SMBv1? Well, it┬ about 30 years old and has been known
to make people vulnerable to ransomware attacks over the last several
years. Lots of people stopped using v1 a long time ago. So those who has v1
enabled simply weren┤ able to use the new Android Samba Client app. Now
they can."

So the question simply becomes the following:
*Do you know of a free Android SMBv2 (or SMBv3) client?*

[arlen holder]

> *Do you know of a free Android SMBv2 (or SMBv3) client?*

Here's a test I just ran.

1. I installed these three free SMB clients on Android Nougat 7.0
o AndSMB <https://play.google.com/store/apps/details?id=lysesoft.andsmb>
o SyncMe WiFi <https://play.google.com/store/apps/details?id=com.bv.wifisync>
o GhostCommander + SMB plugin <https://f-droid.org/packages/com.ghostsq.commander/>

2. I set up Windows 10 to allow SMBv1 (in addition to SMBv2, & SMBv3):
o Start > Run > control > OK
o Programs > Programs and Features > Turn Windows Features on or off >
o Change from:
[_]SMB 1.0/CIFS File Sharing Support
[_]SMB 1.0/CIFS Automatic Removal <=== I'm not sure what this is???
[_]SMB 1.0/CIFS Client
[_]SMB 1.0/CIFS Server
[x]SMB Direct
o Change to:
[x]SMB 1.0/CIFS File Sharing Support
[_]SMB 1.0/CIFS Automatic Removal <=== I'm not sure what this is???
[x]SMB 1.0/CIFS Client
[x]SMB 1.0/CIFS Server
[x]SMB Direct
o Reboot

3. All three free Android SMB clients work to connect to the PC share.

4. I then remove SMBv1 from Windows 10 & reboot.
5. All three clients fail to connect.

6. Rooting around, I see the free Android AndSMB client (version 4.0.1)
has the option to connect using SMBv2/v3, which, when tested, works.

7. I don't see any such SMBv2/v3 option in SyncMe WiFi, which fails with
the error "Connection Reset".

8. Likewise with Ghost Commander + SMB plugin, which threw the error
"Alert. An exception occurred with code c0000001. Failed to connect to
0.0.0.0<00>/192.168.1.10"

My tentative conclusion?
a. The only known free SMBv2/v3 client for Android appears to be AndSMB.
b. There may be others; but don't use SyncMe WiFi or GhostCommander.
c. *If you know of a free SMBv2/v3 client for Android - let us know!*

[Libor Striz]

arlen holder <ar...@arlen.com> Wrote in message:

> > *Do you know of a free Android SMBv2 (or SMBv3) client?*
>
>
>

> c. *If you know of a free SMBv2/v3 client for Android - let us know!*
>

https://www.ghisler.com/androidplugins/download/

(Total Commander for Android)
LAN (Windows network) Plugin 3.06 (2018-03-11):
SMB connection to Windows hosts - in case of connection problems,
try using the numeric IP address instead of the computer
name!
New: SMB2 protocol support (required for newer Windows 10)

--
Libor Striz aka Poutnik ( a pilgrim/wanderer/wayfarer)

"Humour is the only effective weapon against stupidity."
Miloš Forman


----Android NewsGroup Reader----
http://usenet.sinaapp.com/

[arlen holder]

On Mon, 21 Jan 2019 07:22:23 +0100 (GMT+01:00), Libor Striz wrote:

> https://www.ghisler.com/androidplugins/download/
> (Total Commander for Android)

> New: SMB2 protocol support (required for newer Windows 10)

Now _that's_ how Usenet is SUPPOSED to work!

Thanks Poutnik for being purposefully helpful in suggesting
Total Commander for SMBv2 support.

Total Commander worked the first time on the Windows 10 default share:
o smb://192.168.1.10:445/public

Interestingly, I had already tested Total Commander as one of my "file
managers" (where I have had the bad luck of never having found a 'good'
file manager replacement after ES File Explorer fled to the dark side).

In Total Commander, I pressed the "LAN (Windows shares)" line, and then
I pressed "<New server>, and then filled out a form which added the Windows
10 IP address of 192.168.1.10 (which I think is used just as a "name").

Total Commander then asked for the
o Server name/directory: 192.168.1.10/public
o User name: arlen
o Password: arlen
[_]Protect with master pass
[x]SMB2
[_]Older NAS compatibility (LMv1)
[_]Use old name lookup method

///LAN/192.168.1.10/public
SMB2 CONNECT.

So that makes two of the four SMB clients tested that work.

These two worked the first time:
o AndSMB works (apparently) with SMBv2 & SMBv3
- <https://play.google.com/store/apps/details?id=lysesoft.andsmb>
o Total Commander + plugin works with SMBv2
- <https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander>
- <https://play.google.com/store/apps/details?id=com.ghisler.tcplugins.LAN>

These two failed on their first tests:
o GhostCommander + plugin apparently is only for SMBv1
- <https://f-droid.org/en/packages/com.ghostsq.commander/>
- <https://f-droid.org/en/packages/com.ghostsq.commander.samba/>
o SyncMe WiFi appears to be only SMBv1
- <https://play.google.com/store/apps/details?id=com.bv.wifisync>

Thank you Poutnik for purposefully adding to our tribal knoweldge!

My recommendation?
1. I'd use AndSMB because I like KISS applications that do 1 thing well.
2. Total Commander also works - and it works as a file manager.

(Some day I'll find a good replacement for the now deprecated
ES File Explorer as a good file manager.)

[arlen holder]

On Mon, 21 Jan 2019 20:15:40 -0000 (UTC), arlen holder wrote:

> Thanks Poutnik for being purposefully helpful in suggesting
> Total Commander for SMBv2 support.

Hi Poutnik, and the Android team,

I found a good kdbx synchronization tool today, by accident.

I tested three more SMB clients today on Nougat 7.0 for the team.
o Astro File Manager
o EasySMB (aka SMB Client)
o SMBSync2 <==== this tool was a *powerful* surprise!

The test is pretty easy.
1. One Win10 machine is set up to allow SMBv1, v2, & v3
2. The other Win10 machine is set up only for SMB v2 & v3

They either connect to the Win10 SMBv2 or v3 shares; or they don't.

The three free SMB clients tested today are downloaded from:
o Astro File Manager <https://play.google.com/store/apps/details?id=com.metago.astro>
o EasySMB SMB Client <https://play.google.com/store/apps/details?id=net.appazing.easysmb>
o SMBSync2 <https://play.google.com/store/apps/details?id=com.sentaroh.android.SMBSync2>

Results of a single test of each of the two Win10 setups:

*Astro:* (obnoxious data collection)
o In "Storage Locations" you press the plus sign to "add".
o You choose "SMB Server"
o Server = 192.168.1.10
o Username = arlen
o Workgroup/Domain = blank
o Password = arlen
o Results for SMBv1 = worked
o Results for SMBv2/3 = Oops! ASTRO has encountered an unexpected problem.

*EasySMB:* (obnoxious ads)
o Press the hamburger > Servers > Add >
o Display name = smbv1
o Host = 192.168.1.10
o Domain = blank
o Path = blank
o Username = arlen
o Password = arlen
o Color = blue
o Results for SMBv1 = worked
o Results for SMBv2/3 = Failed to connect: 0.0.0.0<00>/192.168.1.10

*SMBSync2:* (complex interface)
This is a more complex tool which will automatically sync a master
file either from Android to the PC, or from the PC to Android.

Here's a verbatim blurb from the description of the tool:
"SMBSync 2 is a tool for synchronizing files via wireless LAN
using SMB1 or *SMB2* protocol between the internal storage of
Android terminal, SDCARD and PC/NAS. Synchronization is a
one-way from the master to the target, mirror, move, copy,
archive can be used. (Internal storage, SDCARD, SMB, ZIP
combination is possible). Can start the sync by external
application (Tasker, AutoMagic etc) or SMBSync2 schedule.*

o Press the green plus button at bottom left
o Sync task name = test of copy of kdbx db
o Sync type = Copy (choices are mirror, copy, move, archive)
o Test mode = [x] (do not copy or delete files)
o AUto sync = [x]
o Master folder = Folder Type = SMB Server
o SMB Server = 192.168.1.10
o SMB protocol = Use SMBv1 only or Use SMBv2 (2.01) only
o SMB IPC Signing Enforced = [x]
o Port number = blank
o Use Port Number [_]
o Use Account Name and Password = [x]
o Account name = arlen
o Password = arlen
o List Share = Public
o Results for SMBv1 = worked
o Results for SMBv2/3 = worked

In summary, one of the three not only worked, but turned out to be a
stunningly powerful tool for synchronizing the kdbx database file!

o Astro File Manager = FAIL
o EasySMB (aka SMB Client) = FAIL
o SMBSync2 = WORKED (plus, it turns out to be a powerful sync tool!)

[Libor Striz]

arlen holder <ar...@arlen.com> Wrote in message:

> o Astro File Manager = FAIL
> o EasySMB (aka SMB Client) = FAIL
> o SMBSync2 = WORKED (plus, it turns out to be a powerful sync tool!)
>

Thanks Arlen for the verbose testing results, I will try the
SMBSync2 when I am after LAN sync.

The recommended sync procedure for the scenario
"any DB can be the master DB for a record update"

would be

Device local DB
<DB record level app sync>
Device LAN cached DB
<LAN file sync>
LAN DB

Thus would prevent disastrous hard overwriting of the older dB file
but with some new or newer PW records.

If any app can directly sync the DB at the record level with LAN
resource,
then the device LAN cached DB And LAN sync
can be for the respective device omitted.

[arlen holder]

On Tue, 22 Jan 2019 07:45:58 +0100 (GMT+01:00), Libor Striz wrote:

> Thanks Arlen for the verbose testing results, I will try the
> SMBSync2 when I am after LAN sync.

Hi Poutnik,
The good news is that the SMBSync2 seems to be designed to sync.

It seems that it can copy any file from anywhere to anywhere.
o It can copy from one spot on the Android device to another
o Or it can copy from or to the Android device & a desktop
o And it seemed it could copy things on the net too

It seems really *powerful* if it works as I think it might.

I tested SMBSync2 copying only accidentally actually, by giving it a
directory instead of a file name, and lo and behold, my _entire_ Windows
directory was being copied over WiFi to the Android SD card!

*It seems that SMBSync2 has a _lot_ of file-manipulation switches!*

> The recommended sync procedure for the scenario
> "any DB can be the master DB for a record update"
>
> would be
>
> Device local DB
> <DB record level app sync>
> Device LAN cached DB
> <LAN file sync>
> LAN DB
>
> Thus would prevent disastrous hard overwriting of the older dB file
> but with some new or newer PW records.
>
> If any app can directly sync the DB at the record level with LAN
> resource,
> then the device LAN cached DB And LAN sync
> can be for the respective device omitted.

Hi Poutnik,
I'm not sure exactly what you're saying above, mostly because all my
Android-to-PC file syncs are manual and where I only accidentally ran into
the synchronization capabilities of the SMBSync2 software today.

I never needed an automatic sync before, where I get your point that you
don't want to overwrite the database. I think I saw in the SMBSync2
directions a checkbox to add the date to each copied file name, which might
prevent overwriting.

Data management is _always_ a tremendously difficult task for a whole bunch
of reasons, not the least of which is everyone does it a different way.

For now, I'm going to move on to testing iOS keepass-like apps, and testing
iOS SMB-capable apps, and then when I have everything working manually
across Windows, Linux, Mac, Android, and iOS, _then_ I'll tackle the sync
problem. :)

[Libor Striz]

arlen holder <ar...@arlen.com> Wrote in message:

> On Tue, 22 Jan 2019 07:45:58 +0100 (GMT+01:00), Libor Striz wrote:
>

Thanjs. Good to know to focus on the utility features.

>
>> The recommended sync procedure for the scenario
>> "any DB can be the master DB for a record update"
>>
>> would be
>>
>> Device local DB
>> <DB record level app sync>
>> Device LAN cached DB
>> <LAN file sync>
>> LAN DB
>>
>> Thus would prevent disastrous hard overwriting of the older dB file
>> but with some new or newer PW records.
>>
>> If any app can directly sync the DB at the record level with LAN
>> resource,
>> then the device LAN cached DB And LAN sync
>> can be for the respective device omitted.
>
> Hi Poutnik,
> I'm not sure exactly what you're saying above, mostly because all my
> Android-to-PC file syncs are manual and where I only accidentally ran into
> the synchronization capabilities of the SMBSync2 software today.
>
> I never needed an automatic sync before, where I get your point that you
> don't want to overwrite the database. I think I saw in the SMBSync2
> directions a checkbox to add the date to each copied file name, which might
> prevent overwriting.

It was not about automatic syncing that would just make the same
routine procedure less annoying

It was about file syncing ( ordinary overwriting older files or
choosing direction by a user )
versus
*file structure* syncing, specific for KDBX syncing.

Consider KDBX syncing has very close analogy in a folder syncing,
if you imagine KDBX like a folder.

Syncing folders copies folder files in both directions,
while ordinary file syncing would be
like overwriting of one folder by content of the other.

For the single master, one way update flow scenario,
it does not matter.

But for the multimaster DB scenario, bidirectional update flow,
dustinguishing is the key not to lose data.

[arlen holder]

On Tue, 22 Jan 2019 08:42:01 +0100 (GMT+01:00), Libor Striz wrote:

> Consider KDBX syncing has very close analogy in a folder syncing,
> if you imagine KDBX like a folder.

Hi Poutnik,
You know _more_ about this stuff than I do so I defer to your judgement.

I don't yet have a use model other than:
o Windows owns the "master" passwd.kdbx file
o Android (iOS, Mac, & Linux) use a "copy" of that Windows master file

I'm fully aware that _plenty_ of other use models exist, where, for
example, I've implemented this use model for the CalDAV services:
o There is no "master" iCalendar events.ics file
o Each platform "merges" iCalendar events into their events.ics file

That use model is described here - where kdbx "merging" can be similar:
o Has anyone here ever set up a CalDAV server on Windows for use with Android CalDAV clients?
o <https://groups.google.com/forum/#!topic/comp.mobile.android/52iSsFUQinE>

I am not sure yet, but I "think" the cross-platform password managers can
all "merge" a "partial" kdbx file to make a "complete" kdbx file.

If that's true, then it's the same concept as what I'm already using for
the offline calendaring, where I add to any calendar on any platform, and
then I "merge" the iCalendar "events.ics" file on any other platform.

As with the kdbx file, the only need is to pass the "partial" file back and
forth between the platforms.

[Libor Striz]

arlen holder <ar...@arlen.com> Wrote in message:

> I don't yet have a use model other than:
> o Windows owns the "master" passwd.kdbx file
> o Android (iOS, Mac, & Linux) use a "copy" of that Windows master file

It may not be handy if you set/update passwords specific for a OS
platform different than Windows.

Or if it happens to work with a general PW on them. You would
then need to go extra to the Win machine and put the pw
there,
and to copy the DB back.

Is not it like a scrabbling behind the right ear
by the left hand ?

> I'm fully aware that _plenty_ of other use models exist, where, for
> example, I've implemented this use model for the CalDAV services:
> o There is no "master" iCalendar events.ics file
> o Each platform "merges" iCalendar events into their events.ics file

Why not to use this for passwords?

>
>
>
> I am not sure yet, but I "think" the cross-platform password managers can
> all "merge" a "partial" kdbx file to make a "complete" kdbx file.

What do you mean by a partial file ?
A file with PW subset like Android only passwords or Linux only
passwords?

If so, than merging of such a partial file to complete file is
possible for keepasXC.

But for bidirectional keepass2/win(KP4WIN) or K2A, it ends with
identical content on both sides.

I do not use KP4WIN for some time now, I am not sure if
unidirectional merge is possible,
aside of PW subset export to other DB, And Syncing with this subset DB.

>

>
> As with the kdbx file, the only need is to pass the "partial" file back and
> forth between the platforms.
>

Aside of the partial file confusion,
this is what I speak about.
No master DB And synchronization of the PW records of
particular DB file instances.

[Arlen Holder]

UPDATE:
o <https://i.postimg.cc/SsH7KQsD/mixplorer02.jpg>
o <https://i.postimg.cc/nLzvY993/mixplorer03.jpg>
o <https://i.postimg.cc/jjL7JVB9/mixplorer04.jpg>

*Happy Easter*

Thanks to Mick Finnlay over on the alt.comp.freeware ng, we now have a free
SMBv2.1 client on Android (which can be downloaded wholly anonymously)
as described here earlier today:
o Tutorial: How to connect Android to Windows as a drive letter
over a Wi-Fi LAN for free simple reliable bidirectional copy
<https://groups.google.com/forum/#!topic/alt.comp.freeware/PkJ3nV4OnCY>

Here is Mick Finnlay's purposefully helpful post:
<https://groups.google.com/d/msg/alt.comp.freeware/PkJ3nV4OnCY/_IAIm3xKDwAJ>

Which led to these simplified instructions to obtain the freeware SMBv2.1
client on Android wholly anonymously (which is the beauty of privacy):
<https://groups.google.com/d/msg/alt.comp.freeware/PkJ3nV4OnCY/UvvWahlyDwAJ>

In short:
1. Use your web browser to obtain the MiXplorer APK sans any login needed:
<https://forum.xda-developers.com/attachment.php?attachmentid=4966993&d=1583692659>
2. Use the Aurora Store to anonymously obtain the SMBv2 client plugin:
<https://play.google.com/store/apps/details?id=com.mixplorer.addon.smb>

Interestingly, I haven't used SMB in so many years that I've forgotten how
to test it, so I need to first create an SMB share on Windows to test it
out (since I normally just copy files bidirectionally between Android &
Windows over the Wi-Fi LAN using WebDav servers on Android to make Android
simply a drive letter on Windows using the Windows "mount" commands).
--
Top posting because this is an old thread so here's the original post:

[Arlen Holder]

UPDATE:

Woo hoo!
o *I was able to get 3 free Android _SMBv2_ clients to work with Windows*.

As always, to help others with every thread that is posted to Usenet,
o This is how I set up SMBv2 connections between Android & Windows.

Windows:
1. Settings > Network & Internet > Change connection properties >
Network: Network profile (o) Private
2. Settings > Network & Internet > change your network settings >
Sharing options > Change sharing options for different network profiles
Private (current profile) Network discovery >
When network discovery is on, this computer can see other network
computers and devices and is visible to other network computers.
(o) Turn on network discovery
[x]Turn on automatic setup of network connected devices.
3. Settings > Network & Internet > change your network settings >
Sharing options > Change sharing options for different network profiles
All Networks: Public folder sharing >
When Public folder sharing is on, people on the network, including
homegroup members, can access files in the Public folders.
(o)Turn on sharing so anyone with network access can read and write
files in the Public folders
4. Settings > Network & Internet > change your network settings >
Sharing options > Change sharing options for different network profiles
All Networks: Password protected sharing >
When password protected sharing is on, only people who have a user
account and password on this computer can access shared files,
printers attached to this computer, and the Public folders.
To give other people access, you must turn off password
protected sharing.
(o)Turn on password protected sharing
5. [Save changes]
6. In Windows file explorer, right click on the public folder to be shared:
Properties > Sharing > [Share] > (username) > [Share] > [Done] > [Close]
7. Make a note of the PC IP address (if NETBIOS is flaky).
Settings > Network & Internet > Change connection properties >
IP settings > IPv4 address: 192.168.1.xxx

Android:
A. You can obtain the free *MiXplorer* APK here (it's not on Google Play):
<https://forum.xda-developers.com/attachment.php?attachmentid=4966993&d=1583692659>
B. Obtain the MiXplorer SMBv2 client plugin via Google Play:
<https://play.google.com/store/apps/details?id=com.mixplorer.addon.smb>
C. Launch MiXplorer > top-left (big) hamburger >
top-right (small) hamburger > Add storage > LAN (Samba) > Search local
(it should find your pc in the resulting NETBIOS list)
If that does not find your PC due to NETBIOS issues, then:
C. Launch MiXplorer > top-left (big) hamburger >
top-right (small) hamburger > Add storage > LAN (Samba) >
smb://192.168.1.xxx
Username = <put the Windows username used in sharing>
Password = <put the password for that Windows username>
Display name = SMB
[Save]

You can obtain *CX-Explorer* on Android with its freeware SMBv2 client:
<https://play.google.com/store/apps/details?id=com.cxinventor.file.explorer>
A. CX-Explorer: Network > (press + sign) > REMOTE > Local Network >
(it should find your pc in the resulting NETBIOS list)
Domain = <blank>
Host = 192.168.1.xxx
Port = 445
A. CX-Explorer: Network > (press + sign) > REMOTE > SMB >
(use this method if it doesn't find your PC in the NETBIOS list)
Domain = <blank>
Host = 192.168.1.xxx
Port = 445

You can obtain *X-Plore* on Android with its freeware SMBv2 client:
<https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore>
A. X-Plore: Show > LAN
B. LAN > Add server > Add server > Scan
(it should find your pc in the resulting NETBIOS list)
Label = <blank>
Server = 192.168.1.xxx
Username = <put the Windows username used in sharing>
Password = <put the password for that Windows username>
[Test]
B. LAN > Add server > Add server > Add server
(use this method if it doesn't find your PC in the NETBIOS list)
Label = <blank>
Server = 192.168.1.xxx
Username = <put the Windows username used in sharing>
Password = <put the password for that Windows username>
[Test]

Note: My network is flaky due to the fact my mikrotik Ethernet-to-Wi-Fi
transceiver apparently blocks NETBIOS broadcasts, so for me, the SMB client
automatic scans only work for a while after a router reboot, but the
manually entered IP addresses work reasonably OK in the long run.

Note: 192.168.1.xxx is the actual IP address of your Windows PC.
--
Usenet works best when adults post with purposefully helpful intentions.

[Howard Kaplan]

On Tuesday, May 12, 2020 at 9:27:32 PM UTC-4, Arlen Holder wrote, in part:
>
> You can obtain *X-Plore* on Android with its freeware SMBv2 client:
> <https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore>
> A. X-Plore: Show > LAN
> B. LAN > Add server > Add server > Scan
> (it should find your pc in the resulting NETBIOS list)

I've just discovered that X-Plore now has a built-in Sync function very similar to what SyncMe offers, but using SMB2. (A little searching with the Wayback Machine reveals that it was being beta tested in 2021.) Once you've set up X-Plore to recognize a "server" (actually a shared Windows folder), as described above, you can synchronize that folder with an Android folder, or you can copy newer files from one to the other without erasing orphans at the destination. This function is documented at https://www.lonelycatgames.com/docs/xplore/file-sync.

[Kenan ÇOT]

21 Ocak 2019 Pazartesi tarihinde saat 06:39:28 UTC+3 itibarıyla arlen holder şunları yazdı:

Android pil sağlığı öğrenme
https://www.teknofeed.com/samsung-pil-sagligi-ogrenme/

[Patrick]

Google's Samba client for Android now supports SMBv3, PUBLISHED JUL20,2017
https://www.androidpolice.com/2017/07/19/googles-samba-client-android-now-supports-smbv3/

[Paul Mac]

Hi Arlen,
Thank you and others for all your hard work plodding through this material.

I'm new at this topic so I have comparatively mediocre information to offer, 'purposefully helpful intentions' nonetheless.
I researched your questions from your previous text:

"2. I set up Windows 10 to allow SMBv1 (in addition to SMBv2, & SMBv3):
o Start > Run > control > OK
o Programs > Programs and Features > Turn Windows Features on or off >
o Change from:
[_]SMB 1.0/CIFS File Sharing Support

[_]SMB 1.0/CIFS Automatic Removal <=== I'm not sure what this is??? <<-------

[_]SMB 1.0/CIFS Client
[_]SMB 1.0/CIFS Server
[x]SMB Direct
o Change to:
[x]SMB 1.0/CIFS File Sharing Support

[_]SMB 1.0/CIFS Automatic Removal <=== I'm not sure what this is??? <<-------

[x]SMB 1.0/CIFS Client
[x]SMB 1.0/CIFS Server
[x]SMB Direct

o Reboot".

SMB 1.0/CIFS Automatic Removal = "Automatically removes support for the legacy SMB 1.0/CIFS protocol when such support isn't actively needed during normal system usage."
I'd like to cite my source but that has escaped me now.

I hope I've helped.
Paul