7
  • ESXi 6.5
  • Ubuntu 22.04.5 LTS

I set up the Ubuntu Server a few years ago.

I was able to work with the files through Explorer and edit them, which was amazing, as Linux does not have the best text editors for the core versions.

Now, today, I can no longer view the Linux shares. I can ping it, but cannot access it. In Windows network, I can see all 28 systems in the network, but cannot see the Linux system.

I get this error when trying to reach the Linux share.

[Window Title] Network Error

[Main Instruction] Windows cannot access \\192.168.5.5

[Content] Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.

[V] See details [Diagnose] [Cancel]

[Expanded Information] Error code: 0x80070035 The network path was not found.

I get this same error, whether I use the sharedName or without it.

I watched several videos on setting up the share, and it is identical to what I already have set up. So, what am I missing?

I read that enabling NFS on Windows would work, so i tried that, and still nothing. Just to make sure it was not an issue with my laptop, I also installed NFS on my Desktop system as well, still nothing.

I've rebooted the Linux system several times. I've done everything that I've read to do, but nothing seems to work.

I found this other Super User question's answer, and attempted to apply it:

[Global]  
min protocol = SMB2  
protocol = SMB2

Rebooted SMBD, and then rebooted the server, and still no share available.

I am planning a 3-node Nginx installation on another server, and I need the files that are on this Linux server.

I am not the best at Linux, but if given proper instructions, I can find my way around it.

SMB.CONF

[global]
   #Read that adding min and max was the best way??
   min protocol = SMB2                                                                                 
   max protocol = SMB2                                                                                 
   client min protocol = SMB2
   client max protocol = SMB2

   workgroup = WORKGROUP
   server string = %h server (Samba, Ubuntu)
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d

####### Authentication #######

   server role = standalone server
   obey pam restrictions = yes
   unix password sync = yes

   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user

#======================= Share Definitions =======================

[Linux05-Web]
    comment = LinuxCore05 Inetpub
    path = /srv/web/Inetpub/wwwroot/stream.domain.com
    valid users = linux05
    browsable = yes
    guest ok = yes # This was set to "no" I changed it last night.
    read only = no
    writeable = Yes
    write list = linux05
    create mask = 0664
    directory mask = 0755
    force user = www-data

I am only supplying one of the shares, as there are 5 shares. I also checked, and my SMB version is 4.15.13-Ubuntu. I read that from version 4.x and up, it disables SMB v1 as it is insecure.

I checked the Firewall.

ufw status = inactive

I honestly don't remember disabling it, or I might have sometime over the year of trying to access it. But still, with it inactive, I cannot access it.

Update: I was able to connect through the smbclient to a share on my computer. So, at least Linux can access Windows, but Windows cannot access Linux.

I can copy files to Windows from Linux. It seems that something must be corrupt on the Linux system for it not to allow Windows to access it.

But, at least I can access Windows from Linux, and am successfully copying the important files over. Very happy right now. However, I still would like to dive into why Linux does not allow Windows to access it.

Improve this question
New contributor
Coding Source is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
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

2 Answers 2

Reset to default
2

I wanted to add this here, for those who might run into this issue of Windows losing connection to Linux.

I was able to connect through the smbclient to a share on my computer. So, at least Linux can access Windows, but Windows cannot access Linux.

I can copy files to Windows from Linux. It seems that something must be corrupt on the Linux system for it not to allow Windows to access it. But, at least I can access Windows from Linux, and am successfully copying the important files over. Very happy right now.
However, I still would like to dive into why Linux does not allow Windows to access it.
Still open to suggestions, but wanted to add this as an Answer, as it did allow me to save my files.

Improve this answer
New contributor
Coding Source is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
1
  • Please use the edit link on your question to add additional information. The Post Answer button should be used only for complete answers to the question. Commented 17 hours ago
1

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.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.