Im having an issue with connecting to samba from windows.
This is the exact filepath im trying to connect to: \\192.168.1.242\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 = 192.168.0.1/24 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 \\192.168.1.242\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
62 Answers
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:
2I'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
4
