Unexpected FTP client permission problem not on WinXP but on Win10 only

How do I overcome this new (to me) Windows 10 permission problem?

On Windows XP, I don't have these unexpected permission problems that
Windows 10 seems to have just copying photo files from the DCIM folder on
my Android phone to a folder on the Windows 10 computer over the WiFi LAN.
https://s29.postimg.org/hl3fm3s1z/ftp_folder.jpg

FTP Folder Error:
The item could not be transferred.
Make sure you have permission to store files here
and that the file name is valid.
Details: A connection with the server could not be established.

Here's what I do on Windows XP that works fine but fails as shown above on
Windows 10.

1) I turn on any anonymous FTP server on Android.
2) On Windows 10 I doubleclick on "This PC"
3) In "This PC" windows, I right click & select "Add a network location"
4) I press "Next" to the "Welcome to the Add Network Location Wizard"
5) I press "Choose a custom network location"
6) I enter the "Internet or network address:" of ftp://192.168.1.9:3721/
(Note WinXP doesn't require the last slash but Windows 10 requires it!)
7) I press "Next" and leave "Log on anonymously" checked.
8) I press "Next" and leave the name at the default & press "Next" again
9) I then press "Finish" and up pops my sdcard in the Windows 10 explorer.

At this point I can easily navigate over WiFi to my photos, but when I try
to copy and paste photos from the phone to Windows, I get the permission
error even though there are no permission problems that I know of.
https://s3.postimg.org/jng05kz6b/ftp_folder_anon.jpg

All this worked just fine on Windows XP.
What do I have to hack or change to get this simple copy to work on Win10?

Roy Tremblay actually wrote:

All this worked just fine on Windows XP.
What do I have to hack or change to get this simple copy to work on Win10?

I tried this registry hack and rebooted, but it did nothing except kill
MSRT (the reboot did that - the registry hack did nothing):
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorks tation\Parameters
Create a new 32-bit DWORD
AllowInsecureGuestAuth = 1 (hex)
https://social.technet.microsoft.com...r-with-network
https://www.tenforums.com/network-sh...ct-shares.html

After that registry hack & reboot failed, I tried creating an extraneous
folder, turned "sharing" on, and that worked.

Now I can transfer files from Android to Windows 10 over the WiFi LAN.

So, I guess the main question is why didn't sharing need to be turned on
for Windows XP to transfer files from an Android anonymous FTP server but
sharing has to be turned on in Windows 10 to perform the same task?

On Thu, 1 Jun 2017 00:48:13 +0000 (UTC), Roy Tremblay wrote:

All this worked just fine on Windows XP.
What do I have to hack or change to get this simple copy to work on Win10?

Having met problems like this not on Win 10 or even 8.* or 7 but Vista, I
can only surmise you're running into an overly ambitious instance of UAC
(User Account Control). That's like Unix file/directory permissions, but
far more ad hoc or ad lib or disorganized -- search the web for info on how
to get around it. And be sure *not* to be trying to copy into a directory
that's within any of the more tightly controlled areas of the HD, where the
UAC limitations are even stricter (e.g., HOSTS is in a sub-...-subdirectory
of one such directory, so that it becomes a real (= royal) pain to edit
your HOSTS file until you've overcome the UAC permissions problems).

HTH. Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP.

tlvp actually wrote:

Having met problems like this not on Win 10 or even 8.* or 7 but Vista, I
can only surmise you're running into an overly ambitious instance of UAC
(User Account Control).

There must be some hiccup between Android & Windows 10 networking.
https://s2.postimg.org/twp9fz16x/finicky_ftp.gif

I can repeatedly prove that it's finicky - but I don't know the cause.

I doubleclick on the "Network location" ftp://192.168.1.2:3721 and it
fails. I try again, and it fails. I try a few more times, and it works.
Later I try, and it fails. Then it works.

I do nothing in between.
It's just finicky.
I don't know why.
https://s2.postimg.org/twp9fz16x/finicky_ftp.gif

Roy Tremblay actually wrote:

I can repeatedly prove that it's finicky - but I don't know the cause.

I doubleclick on the "Network location" ftp://192.168.1.2:3721 and it
fails. I try again, and it fails. I try a few more times, and it works.
Later I try, and it fails. Then it works.

I do nothing in between.
It's just finicky.
I don't know why.
https://s2.postimg.org/twp9fz16x/finicky_ftp.gif

BTW, this never happened with the same phone and WinXP, even now.
So, there's something finicky in Windows 10, and probably it's related to
permissions based on the error.

But what?
I don't know (because it works half the time and fails the other half).
If I just keep trying, it eventually works, with nothing changed in
between.
https://s2.postimg.org/twp9fz16x/finicky_ftp.gif