Why does "net use/ftpuse" sometimes mount the result as a drive,
but yet, in other cases, "net use" doesn't result in a drive?
Example 1: Android WebDav server.
When I "net use" the WebDav share, it results in the Android
file system mounted as a drive letter on Windows.
NET USE [devicename | *] [\\computername\sharename[\volume] [password | *]] [/USER:[domainname\]username] [/USER:[dotted domain name\]username] [/USER:[username@dotted domain name] [/SMARTCARD] [/SAVECRED] [/REQUIREINTEGRITY] [/REQUIREPRIVACY] [/WRITETHROUGH] [/TRANSPORT:{protocolname}]] [[/DELETE] | [/PERSISTENT:{YES | NO}]]
Example 2: Android FTP server.
The Windows FTPUse command also results in the Android file
file system mounted as a drive letter on Windows.
FTPUSE <driveletter>: <ftpserver> [/USER:<username> <password>] [/PORT:<port>]
<
https://www.ferrobackup.com/map-ftp-as-disk.html> <
https://www.wintips.org/map-ftp-to-local-drive-letter-windows/> <
https://github.com/jokerby/ftpusegui>
Example 3: iOS SMB server.
The Windows "net use" command certainly maps the network drive.
You can copy files both ways over the LAN using the command line.
But it doesn't result in a drive letter on Windows?
Why not?
Why does "net use" on a WebDav share result in a drive letter,
while the same command on an SMB share doesn't result in a drive letter?
--- MBSE BBS v1.1.1 (Linux-x86_64)
* Origin: BWH Usenet Archive (
https://usenet.blueworldho (3:633/280.2@fidonet)
