The Windows 10 error message The network path was not found suggests that the Windows client is not receiving the SMB share advertisements. If I recall correctly, there is a separate network service (daemon) on Linux that provides this. Perhaps the problem lies there.

The log files (/var/log/samba/log.%m) should normally be useful in determining what is happening.

Cross-platform Windows file sharing can be complex to set up and diagnose, especially if there are Windows domain controllers involved.

If the only purpose of file-sharing is to use a preferred text editor on Windows to edit text files on Linux, I would consider alternatives.

• Find whether your preferred editor or an equivalent editor can be installed on Linux. Or

• Install Microsoft's SSH on Windows 10 - I recall it being installable through the control panel as a supported but optional feature. Then to edit a file, use a workflow something like

    scp [email protected]:/path/to/filename C:\temp\
    preferrededitor C:\temp\filename
    scp C:\temp\filename [email protected]:/path/to/
  

• Alternatively use scp to move all the from Linux to Windows and run NGINX there. E.g. something like scp [email protected]:/path/to/ .

Luckily for me, my favourite text editor is available on both Linux and Windows so I use it everywhere and avoid this type of cross-platform file-sharing.