Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • It might be a Microsoft update that stops the older SMB version 1 file-sharing protocol. I doubt you really want to use NFS, I would either re-enable SMB v1 on WIndows or re-try SMB v2 on Linux. Since you want the files for an NGINX application I would consider NGINX on Linux or permanently move the files to your WIndows server using SSH. Commented yesterday
  • Looking inside "Windows Features," I see that I have SMB 1.0/CIFS Client & SMB Direct both turned on. I just read that Samba version 4.x+ disables SMBv1 because it's insecure. Mine is (4.15.13-Ubuntu). I will update my information with the smb.conf file. Commented yesterday
  • This Linux system is = Ubuntu | NGINX | HLS | Liquidsoap | SSL, in case the information is needed. Commented yesterday
  • Regardng " [Main Instruction] Windows cannot access \\192.168.5.5... The network path was not found," I had a similar issue, due to accidentally connecting to a guest account on a router, while the other machine used the main account. Yes, it could be a Windows update issue, but also check connections. Commented yesterday
  • 1
    Check out learn.microsoft.com/en-us/answers/questions/2189515/… and learn.microsoft.com/en-us/answers/questions/5552546/…. Your issue may be possibly related to one of last WinUpdates. Commented yesterday