Latest LQ Deal: Linux Power User Bundle
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 08-05-2018, 08:19 AM   #1
LQ Newbie
Registered: Aug 2018
Location: Melbourne
Distribution: Slackware 14.2 - Multilib
Posts: 25

Rep: Reputation: Disabled
Question Slackware 14.2 -Multi- | Samba problems connecting to and from Win 10 x64.

Ok, So I believe(d) I have correctly configured my Samba server.

I followed the instructions via this guide:

Everything seemed to be humming along perfectly.

From Slackware: Can ping WWIN10PC via CLI no problems.
From Windows: can ping Slackware via CLI no problems.

From slackware: nmblookup HOST shows Win 10 Host and IP.
From Slackware: smbclient -L WIN10IP shows Win 10 Deets and Shares.

Then, this happens:

> Checked and Double checked all Shares are Mounted & Defined Correctly. (this is what i thought the error was telling me)

> Checked HDD mounted correctly.
> Win10PC is not Microsoft Account.
> Have Network Reset WIN10PC via cmd.
> have renewed /all connections on WIN10PC.
> have stopped and restared samba service on slackware many times.
> have rebooted WIN10PC countless times.
> have reset Modems/Routers.

It seems like a simple fix.
Looked everywhere, And found 1 page for UBUNTU with the error i was recieving, and the question was unfortunately unanswered.

my smb.conf

# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================

# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
server string = Samba Server

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
# # Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Specifies the Kerberos or Active Directory realm the host is part of
; realm = MY_REALM

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces =

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no

# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g

#============================ Share Definitions ==============================
comment = Home Directories
browseable = no
writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes

# This one is useful for people to share files
comment = Temporary file space
path = /tmp
read only = no
public = yes

# A publicly accessible directory, but read only, except for people in
# the "wheel" group
comment = Music Stuff 2.7TB
path = /home/Blackhole1
public = yes
writable = yes
printable = yes
write list = wheel

# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765

testparm checks out all ok.

I believe the problem lies with WIN10, would I be right ?

Old 08-05-2018, 09:10 AM   #2
LQ Newbie
Registered: Aug 2018
Location: Melbourne
Distribution: Slackware 14.2 - Multilib
Posts: 25

Original Poster
Rep: Reputation: Disabled

So I am able to access WIN10PC from Slackware via

but not the reverse.
Old 08-06-2018, 12:09 AM   #3
LQ Newbie
Registered: Aug 2018
Location: Melbourne
Distribution: Slackware 14.2 - Multilib
Posts: 25

Original Poster
Rep: Reputation: Disabled
So can anyone help me orrrrr?
Old 08-06-2018, 02:48 AM   #4
LQ Newbie
Registered: Aug 2018
Location: Melbourne
Distribution: Slackware 14.2 - Multilib
Posts: 25

Original Poster
Rep: Reputation: Disabled
ok, fine, time to stop paddling in the kiddie pool.
I get the message.

I'll just deal with it until i can work it out myself.
Old 08-06-2018, 07:08 AM   #5
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 721

Rep: Reputation: 404Reputation: 404Reputation: 404Reputation: 404Reputation: 404
You were complaining here:
about people ignoring your posts and I wonder if you were referring only to this thread? If so, next time please start the thread in the Slackware Forum.

I wish I could help you with your win10 issue but I'm afraid I can't as I'm not using it at all, for me M$ committed "corporate suicide" when Billy Boy left and they launched win8.
However, until someone more experienced than me with win10 will try to help you, I remember there were some recent discussions here on Slackware LQ about issues with Samba <-> win10 and I'd kindly suggest you to use the search function of the LQ and look after: win10 slackware samba
Maybe you can start with this thread:

P.S. Asked the mods to move this thread to the Slackware Forum

Last edited by abga; 08-06-2018 at 07:09 AM.
Old 08-06-2018, 08:33 AM   #6
Registered: Mar 2011
Location: MA, USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 7,214
Blog Entries: 12

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
Moved: This thread is more suitable in Slackware and has been moved accordingly to help your thread/question get the exposure it deserves.
Old 08-06-2018, 10:08 AM   #7
Registered: Sep 2012
Posts: 204

Rep: Reputation: Disabled
You might look at things from the windows side. by default win10 has disable down level SMB protocols. I have been on current now for a quite a some time which has a later samba so I don't know what the version in 14.2 supports at this point.

If you are on a small home network were you are not terribly concerned about the security enhancements like server signing, LLNMR/NTLM responsing poisoning attacks etc you might re-enable smbv1 in win10. (Don't do this on a portable machine that you connect to other networks you don't trust or if you are on a network where there are clients you don't trust).
Old 08-06-2018, 12:30 PM   #8
Registered: Oct 2014
Distribution: Slackware, Proxmox, Debian, CentOS, Ubuntu MATE
Posts: 746

Rep: Reputation: Disabled
I am not a Samba expert.

The output spew in the image you attached shows you queried the Windows 10 Home system. From that perspective your smb.conf is not important. The smb.conf file is for the Slackware server side.

The error output indicates the Windows 10 Home system is not configured with a Workgroup name. When configured with a Workgroup name, the smbclient -L output should include Domain= information.

As you have configured the Slackware Samba server with workgroup = WORKGROUP, for consistency use the same name on the Windows 10 side. You then should see smbclient -L output including Domain=WORKGROUP.
Old 08-08-2018, 01:26 PM   #9
Senior Member
Registered: May 2015
Location: Utah, USA
Distribution: Slackware 14.2 || Slackware-current && CentOS
Posts: 1,318

Rep: Reputation: 694Reputation: 694Reputation: 694Reputation: 694Reputation: 694Reputation: 694
Yeah you need to set the WORKGROUP name on the windows machine. It seems the error message is pretty self explanatory. This is not a Microsoft Windows forum, so I won't Google how to go about doing that for you. The results should be fairly easy to find with a quick search. Just be sure to enable all the usual suspects when adding a Windows share.
Old 08-08-2018, 03:18 PM   #10
Senior Member
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,426

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
endless-rain --

What upnort and mralk3 said ... I believe they nailed it.

In addition, as long as you're not messing with WinXP or older, it won't hurt to add: protocol = SMB2 to your /etc/samba/smb.conf

See: man 5 smb.conf


-- kjh


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 14.2 -Multi- | Samba problems connecting to and from Win 10 x64. endless-rain Linux - Networking 0 08-06-2018 03:45 PM
Problems with updates - Slackware 13.1 x64 rob2uk Slackware 4 03-24-2011 06:18 PM
trouble connecting Samba from Win XP clients halludba Linux - Software 4 03-04-2010 03:31 PM
OpenSuse 11.2 x64 - just installed along side Win 7 x64 - major prob Linux side thoug KL51 SUSE / openSUSE 7 12-11-2009 06:18 AM
samba issue: connecting from win machine pratik Linux - Networking 7 08-07-2003 05:42 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:57 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration