What alternatives are there to Samba for mapping a network drive outside the local network?

Question

linux

There is a home server with a white IP on Ubuntu Server 20, Samba and FTP are raised on it, nginx is screwed on. Gigabit connection.
I would like to make a network share available to Windows clients via the Internet in the form of a network drive , after some thought I came up with the following options:
1) Forwarding the Samba port directly to the Internet is a bad option, not safe.
2) Raising a VPN server and running clients in Samba via VPN is an acceptable option, it's safe.
Both options above are preliminarydon't like it, because after some googling, several reports were found that Samba does not tolerate connections with a delay, and there is an assumption that the ping of such a connection will be at least 10, if not > 40. I don’t know how critical this figure is, there were no specifics.

3) Raising webdav to nginx is a bad (?) option, judging by the same search results it will be slower than Samba.
4) NFS - old experiments with NFS ended in failure - normally the ball worked only in the local network, but is not needed if you have Samba and no Mac. Does NFS work at all/does it make sense not on a local network?

There is only one requirement: connection to a Windows client in the form of a network share, that is, a network drive, with the ability not only to download, upload and delete files (FTP), but also open them directlyfrom disk. Small files are not expected at all, most likely they will be at least 10 gigabytes. It is desirable, of course, to squeeze the maximum out of gigabit. Clients will be trusted, so the issue of security is only in the plane of vulnerabilities (hello rotten versions of Samba).

Question two:
1) Which of these options will work the fastest?
2) Maybe I'm missing some other solutions?

There is no time for our own experiments yet, maybe someone has experience in solving a similar issue.

Answer 1

Try https://github.com/billziss-gh/sshfs-win
(you will first need to install https://github.com/billziss-gh/winfsp/releases/tag/v1.8 )
map the home folder of the linuxuser user from linux.host.com
net use X: \\sshfs\[email protected]\ to disk X.
map the home folder from linux.host.com to the X drive
net use X: \\sshfs.r\[email protected]!anotherport\home
you can also use ssh keys and map it automatically, without entering a password

Answer 2

No. Normally, opening a file "directly from disk" will only work on a local network. When working via the Internet, there will be a glucodrome (dumps, dependencies, brakes), otherwise no one would have bothered with the invention of crutches like DAV.

Answer 3

no, windows only supports samba and opening through a browser.
her nfs support is frankly disregard.

Answer 4

If you try the options and it will be stupid - try to use the remote opening of files.
In its simplest form, this is RDP. But this is not very convenient, as the entire working environment changes.
In a cool version, this is remoteapp from microsoft (but it blunts) or Citrix in Seamless window mode
. It looks like the program is launched by the shortcut - but on a remote computer, and only the picture is broadcast to you.
At the same time, this is not noticeable at all for users: well, the program opened and opened where it is executed by them. You can minimize it, resize the window, and so on.
It will be faster than opening 10gb files over the network, IMHO.
This is how users worked with 1s for me, and it was many times faster than working with a lakally installed 1s that accessed the database over the network.

Answer 5

As an option, use Direct Access - a solution from M $ out of the box.
There is a minus - you need a separate server, the client OS is not lower than enterprise, although W10 enterprise can now be issued as a subscription. Works stably. There is a description on Habré https://habr.com/en/post/325458/