Im having an issue with connecting to samba from windows.

This is the exact filepath im trying to connect to: \\\server-sharedfiles.

Server-sharedfiles is the name of the folder i would like to share and the filepath is set in the config file to that folder like this: /home/server/server-sharedfiles/.

The error i get is that it thinks i typed it wrong.

config file:

workgroup = server server min protocol = NT1 server string = %h server (Samba, Ubuntu) netbios name = FileServer wins support = yes dns proxy = no

name resolve order = lmhots host wins bcast

interfaces = eth0 bind interfaces only = yes

log file = /var/log/samba/log.%m max log size = 1000

syslog = 0

panic action = /usr/share/samba/panic-action %d

server role = standalone server passdb backend = tdbsam 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

usershare allow guests = yes

[printers] comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes guest ok = no read only = yes create mask = 0755

[print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no

[MY_SHARE] writeable = yes path = /home/server/server-sharedfiles comment = Fileserver guest account = wide links = no security = user

i have tried using \\\MY_SHARE\ and that wont work either and gives this same error:


winver on my pc outputs this:


for samba vesion i get this:

server@VERUM-SERVER:/etc/samba$ samba --version Version 4.3.11-Ubuntu


  • 2
    You typed it wrong indeed, it needs \\... Nov 11, 2021 at 12:46
  • its not that, it still gives the same err Nov 11, 2021 at 14:52
  • No, It IS that - double backslash instead of single at the beginning -, for starters. You may have other errors though. Please edit and post the configuration. Nov 11, 2021 at 15:05
  • ah my bad the forum inturprets a double backslash as a single one, and im still having the same issue even with the double backslash Nov 11, 2021 at 15:28
  • You are trying to connect to the path instead of the share, try replacing 'server-sharedfiles' with 'MY_SHARE' Nov 11, 2021 at 17:14

2 Answers 2


Without having all the information I suspect this is a case of Windows 10 requiring a higher level of SMB encryption than your SMB server allows. I'd check on your SMB server what version of SMB it supports first, then check what versions of SMB your windows machine supports.

Either your SMB server system would have to enable a higher version of SMB (not always possible), or your windows system would need the registry changed to allow (and match) the lower SMB version of the server.

This happens quite frequently with linux based SMB servers when accessing from Windows 10.

Posting what OS and version of SMB you're using would help, along with what version and build of Windows 10 you're using.

As an example, if your SMB server only had SMB 1.0 enabled: https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-default-in-windows

  • winver on my windows comuter im using to connect shows this: imgur.com/a/2LddYUs. on my server i get this: (copy and paste) server@VERUM-SERVER:/etc/samba$ samba --version Version 4.3.11-Ubuntu Nov 15, 2021 at 15:26
  • This article shows how to get your SMB protocol version: thewindowsclub.com/check-smb-version-windows I haven't used Windows 11 so there are perhaps some new issues there. You can clearly get your linux samba version from this site: samba.org/samba/history .If you have version 4.3.11 that is a version from 2015 so it's likely something will need to be changed on the Windows side to support it. What is your linux OS, is it a NAS? Is there any way to update the samba version? If it's a NAS, sometimes there are newer firmwares you can install.
    – Marshalleq
    Nov 16, 2021 at 18:20

I'm not sure if what you posted above is a typo but I can reproduce your error easily by using one line from your smb.conf into mine:

name resolve order = lmhots host wins bcast

To be honest I wouldn't have thought it would make a mess of things since Samba generally ignores things that are incorrect but in this case it stops smbd from running:

:~$ sudo service smbd restart

Job for smbd.service failed because the control process exited with error code. See "systemctl status smbd.service" and "journalctl -xe" for details.

When I correct the line:

name resolve order = lmhosts host wins bcast

And restart smbd: sudo service smbd restart

I can access the share from Windows again.

Just make sure you address the share the way Rowland Penny mentioned above

  • sry, i dont quite understand, you dont say what to change the line to, also im not getting any errors in ubuntu, or at least not over ssh Nov 15, 2021 at 15:32
  • In the smb.conf on your Ubuntu machine you have a typo in your "name resolve order" line. One of the elements reads lmhots . It should be lmhosts. Make the change then restart smbd.
    – Morbius1
    Nov 15, 2021 at 17:39
  • ah ok thx i fixed it, still not working tho..., it gives the same "network name not found" error Nov 16, 2021 at 9:28
  • Assuming [1] the ip address is correct and [2] you disabled your linux firewall ( ufw ) to see if it's in the way, the only thing left is Linux permissions on the shared folder and the path to it. So do a ls -dl /home/server and a ls -dl /home/server/server-sharedfiles to find out.
    – Morbius1
    Nov 17, 2021 at 13:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.