Do these 3 WiFi tests of a network location to a drive letter mapping work for you on Android 7.0 Nougat & Windows 10 using only freeware?

Do these 3 WiFi tests of a network location being mapped to a drive letter
on Windows 10 work for you using the specified freeware on a modern (above
4.3) Android (e.g., I'm on Android 7.0 Nougat)?

I already have a working solution; hence this request is to help others.
What we want to figure out is what _general_ solutions work for all.

To that end, I ask that expert Windows 10 users run one of these tests.
TEST 0: Basic tests from the Windows command line (all work fine for me)
TEST A: FTPUse Windows freeware (does not work for me on Win10)
TEST B: SFTP Net Drive Windows freeware (does not work for me on Win10)
TEST C: DND Windows freeware (works just fine for me on Win10)
=====
STEP 0. On Android, install & configure any desired FTP Server freewa
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver
https://f-droid.org/en/packages/be.ppareit.swiftp_free/
https://play.google.com/store/apps/details?id=org.primftpd
https://f-droid.org/en/packages/org.primftpd/
etc.
NOTE: I used the Android "Olive Tree" FTP server set at the defaults.
Network interface = WiFi
Port = 2221
Passive Ports = 2300-2399
Anonymous user = [x]
User name = francis
User password = francis
Home directory = SdCard (/storage/emulated/0)
Ftp server available on = ftp://192.168.1.6:2221

Test your FTP connection using a variety of basic methods:
Quick test 1: Windows browser:
NOTE: The first "francis" is the login; the second one is the passwd.
You should be able to see your Android files on Windows over WiFi FTP.

Quick test 2: Windows command line:
C:\ ftp
ftp open 192.168.1.6 (your IP address will differ)
user francis
passwd francis
ftp dir (you may have to accept a Windows Defender popup)
You should be able to see your Android files on Windows over WiFi FTP.
ftp quit

Quick test 3: File Explorer
RightClick Add a network location
You should be able to see your Android files on Windows over WiFi FTP.
=====
STEP A1: Download, install, & configure the FTPUse Windows freeware
https://www.ferrobackup.com/download/FtpUseInst.exe
I saved to: C:\software\network\ftp\ftpuse\FtpUseInst.exe (485 KB)
It wanted to go to: C:\Program Files\Ferro Software\FtpUse
I installed into: C:\app\network\ftp\ftpuse
Quick test: C:\ path (it should show the directory in the path)
Quick test: C:\ ftpuse --help (it should show the manpage)

STEP A2: Test FTPUse on Windows 10:
C:\ ftpuse T: 192.168.1.6 francis /USER:francis /PORT:2221 /debug
For some reason, this isn't working even though a browser works fine:
Swift FTP: http://www.bild.me/bild.php?file=7687244dir06.jpg
Swift FTP: http://www.bild.me/bild.php?file=3316456dir08.jpg
Olive FTP: http://www.bild.me/bild.php?file=7355568dir09.jpg
Olive FTP: http://www.bild.me/bild.php?file=4223201dir010.jpg
=====
STEP B1: Download, install, & configure SFTPNetDrive Windows freeware
https://www.nsoftware.com/sftp/netdrive/ (bogus name & email ok)
I saved to: C:\software\network\ftp\sftpnetdrive\SFTPNetDRive. exe
It wanted to go to: C:\Program Files (x86)\SFTP Net Drive 2017
I installed into: C:\app\network\ftp\sftpnetdrive
The target was: C:\app\network\ftp\sftpnetdrive\SftpNetDrive.exe
Product registration can't be skipped.
You have to provide a name & email address (I gave it bogus info).
The installer default choices were set to:
Select components to install
[x]SFTP Net Drive 2017
[x]Start menu group
[x]Desktop icon
[x]Start on Windows startup
I changed that to:
Select components to install
[x]SFTP Net Drive 2017
[x]Start menu group
[x]Desktop icon
[_]Start on Windows startup
STEP B2: Mount the FTP network location as a Windows removable drive:
https://www.wintips.org/map-ftp-to-local-drive-letter-windows/
https://www.ferrobackup.com/map-ftp-as-disk.html
When the installation finished, it asked if I wanted to start.
I OK'd that request to start.
When it started, it asks:
Profile (I left this at "(Unamed)")
Server (I changed to 192.168.1.6:2221)
Username (francis)
Authentication (I changed this from "Key" to "Password")
Password (francis)
Key (I left this at "authentication agent (PuTTY or SSH))
Drive Letter: (I left this at "Last Available")
Advanced - Port (I changed the port from 22 to 2221)
I then hit the "Connect" button.
It said "Connecting..." for a long time.
Then I get: "Error" "Connection timeout".
http://www.bild.me/bild.php?file=2809525dir013.jpg
=====
STEP C1: Download, install, & configure the DND Windows freeware
http://www.directnet-drive.net/
I saved to: C:\software\network\ftp_mounting\directnetdrive\dn d-setup.msi
It wanted to go to: C:\Program Files (x86)\DirectNet Drive\
(Note the trailing backslash!)
I installed into: C:\app\network\ftp\directnetdrive\
The target was: C:\app\network\ftp\directnetdrive\dndclient.exe
STEP C2: Run the desktop shortcut & configure as per your setup.
NOTE: The configuration below is mine; yours will differ.
When DirectNetDrive runs, a form pops up:
site name (default = blank)
drive letter (default = blank)
url (default = http://)
protocol (default = WebDAV) (choices are WebDAV, FTP, SFTP)
host (default = blank)
port (default = blank)
path (default = blank)
user (default = blank)
password (default = blank)
proxy (default = None)
ssl (default = None)

I changed that to:
site name (default = blank)
drive letter = R
url (this changed to )
protocol = FTP
host = 192.168.1.6
port = 2221
path (default = blank)
user = francis
password = francis
proxy (default = None)
ssl (default = None)

I hit the "Connect" button.
Voila!
http://www.bild.me/bild.php?file=4731516dir011.jpg
I could right click to "Open a command window here" to run DOS commands
directly on the Android file system mapped to a drive letter.
http://www.bild.me/bild.php?file=6340420dir012.jpg
=====
Do these 3 WiFi tests of a network location being mapped to a drive letter
on Windows 10 work for you using the specified freeware on a modern (above
4.3) Android?

On 10/19/2018 10:45 PM, Arlen Holder wrote:
Do these 3 WiFi tests of a network location being mapped to a drive letter
on Windows 10 work for you using the specified freeware on a modern (above
4.3) Android (e.g., I'm on Android 7.0 Nougat)?

I already have a working solution; hence this request is to help others.
What we want to figure out is what _general_ solutions work for all.

To that end, I ask that expert Windows 10 users run one of these tests.
TEST 0: Basic tests from the Windows command line (all work fine for me)
TEST A: FTPUse Windows freeware (does not work for me on Win10)
TEST B: SFTP Net Drive Windows freeware (does not work for me on Win10)
TEST C: DND Windows freeware (works just fine for me on Win10)
=====
STEP 0. On Android, install & configure any desired FTP Server freewa
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver
https://f-droid.org/en/packages/be.ppareit.swiftp_free/
https://play.google.com/store/apps/details?id=org.primftpd
https://f-droid.org/en/packages/org.primftpd/
etc.
NOTE: I used the Android "Olive Tree" FTP server set at the defaults.
Network interface = WiFi
Port = 2221
Passive Ports = 2300-2399
Anonymous user = [x]
User name = francis
User password = francis
Home directory = SdCard (/storage/emulated/0)
Ftp server available on = ftp://192.168.1.6:2221

Test your FTP connection using a variety of basic methods:
Quick test 1: Windows browser:
NOTE: The first "francis" is the login; the second one is the passwd.
You should be able to see your Android files on Windows over WiFi FTP.

Quick test 2: Windows command line:
C:\ ftp
ftp open 192.168.1.6 (your IP address will differ)
user francis
passwd francis
ftp dir (you may have to accept a Windows Defender popup)
You should be able to see your Android files on Windows over WiFi FTP.
ftp quit

Quick test 3: File Explorer
RightClick Add a network location
You should be able to see your Android files on Windows over WiFi FTP.
=====
STEP A1: Download, install, & configure the FTPUse Windows freeware
https://www.ferrobackup.com/download/FtpUseInst.exe
I saved to: C:\software\network\ftp\ftpuse\FtpUseInst.exe (485 KB)
It wanted to go to: C:\Program Files\Ferro Software\FtpUse
I installed into: C:\app\network\ftp\ftpuse
Quick test: C:\ path (it should show the directory in the path)
Quick test: C:\ ftpuse --help (it should show the manpage)

STEP A2: Test FTPUse on Windows 10:
C:\ ftpuse T: 192.168.1.6 francis /USER:francis /PORT:2221 /debug
For some reason, this isn't working even though a browser works fine:
Swift FTP: http://www.bild.me/bild.php?file=7687244dir06.jpg
Swift FTP: http://www.bild.me/bild.php?file=3316456dir08.jpg
Olive FTP: http://www.bild.me/bild.php?file=7355568dir09.jpg
Olive FTP: http://www.bild.me/bild.php?file=4223201dir010.jpg
=====
STEP B1: Download, install, & configure SFTPNetDrive Windows freeware
https://www.nsoftware.com/sftp/netdrive/ (bogus name & email ok)
I saved to: C:\software\network\ftp\sftpnetdrive\SFTPNetDRive. exe
It wanted to go to: C:\Program Files (x86)\SFTP Net Drive 2017
I installed into: C:\app\network\ftp\sftpnetdrive
The target was: C:\app\network\ftp\sftpnetdrive\SftpNetDrive.exe
Product registration can't be skipped.
You have to provide a name & email address (I gave it bogus info).
The installer default choices were set to:
Select components to install
[x]SFTP Net Drive 2017
[x]Start menu group
[x]Desktop icon
[x]Start on Windows startup
I changed that to:
Select components to install
[x]SFTP Net Drive 2017
[x]Start menu group
[x]Desktop icon
[_]Start on Windows startup
STEP B2: Mount the FTP network location as a Windows removable drive:
https://www.wintips.org/map-ftp-to-local-drive-letter-windows/
https://www.ferrobackup.com/map-ftp-as-disk.html
When the installation finished, it asked if I wanted to start.
I OK'd that request to start.
When it started, it asks:
Profile (I left this at "(Unamed)")
Server (I changed to 192.168.1.6:2221)
Username (francis)
Authentication (I changed this from "Key" to "Password")
Password (francis)
Key (I left this at "authentication agent (PuTTY or SSH))
Drive Letter: (I left this at "Last Available")
Advanced - Port (I changed the port from 22 to 2221)
I then hit the "Connect" button.
It said "Connecting..." for a long time.
Then I get: "Error" "Connection timeout".
http://www.bild.me/bild.php?file=2809525dir013.jpg
=====
STEP C1: Download, install, & configure the DND Windows freeware
http://www.directnet-drive.net/
I saved to: C:\software\network\ftp_mounting\directnetdrive\dn d-setup.msi
It wanted to go to: C:\Program Files (x86)\DirectNet Drive\
(Note the trailing backslash!)
I installed into: C:\app\network\ftp\directnetdrive\
The target was: C:\app\network\ftp\directnetdrive\dndclient.exe
STEP C2: Run the desktop shortcut & configure as per your setup.
NOTE: The configuration below is mine; yours will differ.
When DirectNetDrive runs, a form pops up:
site name (default = blank)
drive letter (default = blank)
url (default = http://)
protocol (default = WebDAV) (choices are WebDAV, FTP, SFTP)
host (default = blank)
port (default = blank)
path (default = blank)
user (default = blank)
password (default = blank)
proxy (default = None)
ssl (default = None)

I changed that to:
site name (default = blank)
drive letter = R
url (this changed to )
protocol = FTP
host = 192.168.1.6
port = 2221
path (default = blank)
user = francis
password = francis
proxy (default = None)
ssl (default = None)

I hit the "Connect" button.
Voila!
http://www.bild.me/bild.php?file=4731516dir011.jpg
I could right click to "Open a command window here" to run DOS commands
directly on the Android file system mapped to a drive letter.
http://www.bild.me/bild.php?file=6340420dir012.jpg
=====
Do these 3 WiFi tests of a network location being mapped to a drive letter
on Windows 10 work for you using the specified freeware on a modern (above
4.3) Android?

Oh, Arlencia! Put my penis in your mouth
and suck it! I will fill your mouth with sperm!

On Sat, 20 Oct 2018 02:45:27 -0000 (UTC), Arlen Holder wrote:

Do these 3 WiFi tests of a network location being mapped to a drive letter
on Windows 10 work for you using the specified freeware on a modern (above
4.3) Android?

The good news is that Pooh reported that FPTuse created a drive letter for
his Android FTP file server on his local network over WiFi on Windows 10.

Hence I ran it again on my (highly customized) Windows 10, where out of a
half dozen tries, it "appeared" to work once, and failed for the others.

Here are my empirical results:

The Android FTP server (v 1.32) I used was set up in its default mode:
https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver
o Network interface
(o)WiFi
(_)Ethernet
(_)Mobile network
(_)Bluetooth PAN
(_)Loopback (127.0.0.1)
(_)All
o Port = 2221
o Passive Ports = 2300-2399
o Anonymous user = [x]
o User name = francis
o User password = francis
o Home directory
(_)Root (/)
(o)SdCard
(_)DCIM
(_)Custom folder
(_)Ext. SdCard
o Read only = [_]
o Show hidden files = [_]
o Energy save mode = [_]
o High priority service = [x]
o Show server details = [x]

The FPTUse command I used on a Windows 10 Admin window was (verbatim):
ftpuse X: 192.168.1.7 francis /USER:francis /PORT:2221 /debug
ftpuse X: 192.168.1.7 francis /USER:francis /PORT:2221 /nopassive /debug

Reboot 1: Most of the time FTPuse simply fails:
o http://www.bild.me/bild.php?file=5451129dir022.jpg
Reboot 2: But once in a great while it actually appears to work ... but ...
even then, _nothing_ shows up as a drive letter as a result.
o http://www.bild.me/bild.php?file=4121239dir021.jpg
Reboot 3: And even then, FTPuse fails the next time:
o http://www.bild.me/bild.php?file=8726712dir023.jpg

I don't usually deal with firewalls, where I turned off Windows Defender
(at least I think I did) for these experiments, but again, this isn't for
me so it really doesn't matter because if I can't do it out of the box,
neither will others be able to, which is the whole point, let's not forget.
Start Settings Update and security Windows security
Firewall and network protection (everything is turned off)
http://www.bild.me/bild.php?file=9234464dir024.jjpg.jpg

In summary, FTPUse "probably" works on Windows 10 for most people.
(It used to work for me on WinXP years ago.)

I'll write up a quick summary of the half-dozen FTP solutions separately.