Samba not working

Hey guys.

My samba was working perfectly on Kubuntu 16.04 and I copied my smb.conf to netrunner rolling. I also tried using the default smb.conf with netrunner adding my shares to the bottom.

I can’t browse any networks. I can however type paths into dolphin and get to stuff and my shares function perfectly just as they used to in kubuntu. This also works on windows but I cannot use hostnames only IP addresses.

The error I get when trying to browse network in dolphin on the localhost computer is:
Unable to find any workgroups in your local network. This might be caused by an enabled firewall.

The error I get on the windows8 computer when typing in \blackjok3r-pc is:
Windows cannot access \blackjok3r-pc.
However I can use the IP address to connect to the shares on my netrunner box.

I am not useing a firewall unless netrunner installs one by default. Is this the case and how do I turn it off for either samba or completly off? I have a router between me and the internet.



Sample configuration file for the Samba suite for Debian GNU/Linux.

This is the main Samba configuration file. You should read the

smb.conf(5) manual page in order to understand the options listed

here. Samba has a huge number of configurable options most of which

are not shown in this example

Some options that are often worth tuning have been included as

commented-out examples in this file.

- When such options are commented with “;”, the proposed setting

differs from the default Samba behaviour

- When commented with “#”, the proposed setting is the default

behaviour of Samba but the option is considered important

enough to be mentioned here

NOTE: Whenever you modify this file you should run the command

“testparm” to check that you have not made any basic syntactic


#======================= Global Settings =======================



Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = WORKGROUP

server string is the equivalent of the NT Description field

server string = %h server (Samba, Ubuntu)

name resolve order = lmhosts bcast host wins

Windows Internet Name Serving Support Section:

WINS Support - Tells the NMBD component of Samba to enable its WINS Server

wins support = no

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

This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no


The specific set of interfaces / networks to bind to

This can be either the interface name or an IP address/netmask;

interface names are normally preferred

; interfaces = eth0

Only bind to the named interfaces and/or networks; you must use the

‘interfaces’ option above to use this.

It is recommended that you enable this feature if your Samba machine is

not protected by a firewall or is a firewall itself. However, this

option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = yes


This tells Samba to use a separate log file for each machine

that connects

log file = /var/log/samba/log.%m

Cap the size of the individual log files (in KiB).

max log size = 1000

If you want Samba to only log through syslog then set the following

parameter to ‘yes’.

syslog only = no

We want Samba to log a minimum amount of information to syslog. Everything

should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log

through syslog you should set the following parameter to something higher.

syslog = 0

Do something sensible when Samba crashes: mail the admin a backtrace

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

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

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

If you are using encrypted passwords, Samba will need to know what

password database type you are using.

passdb backend = tdbsam

obey pam restrictions = yes

This boolean parameter controls whether Samba attempts to sync the Unix

password with the SMB password when the encrypted SMB password in the

passdb is changed.

unix password sync = yes

For Unix password sync to work on a Debian GNU/Linux system, the following

parameters must be set (thanks to Ian Kahan < for

sending the correct chat script for the passwd program in Debian Sarge).

passwd program = /usr/bin/passwd %u
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .

This boolean controls whether PAM will be used for password changes

when requested by an SMB client instead of the program listed in

‘passwd program’. The default is ‘no’.

pam password change = yes

This option controls how unsuccessful authentication attempts are mapped

to anonymous connections

map to guest = bad user

########## Domains ###########
domain master = auto

The following settings only takes effect if 'server role = primary

classic domain controller’, ‘server role = backup domain controller’

or ‘domain logons’ is set

It specifies the location of the user’s

profile directory from the client point of view) The following

required a [profiles] share to be setup on the samba server (see


; logon path = \%N\profiles%U

Another common choice is storing the profile in the user’s home directory

(this is Samba’s default)

logon path = \%N%U\profile

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of a user’s home directory (from the client

point of view)

; logon drive = H:

logon home = \%N%U

The following setting only takes effect if ‘domain logons’ is set

It specifies the script to run during logon. The script must be stored

in the [netlogon] share

NOTE: Must be store in ‘DOS’ file format convention

; logon script = logon.cmd

This allows Unix users to be created on the domain controller via the SAMR

RPC pipe. The example command creates a user account with a disabled Unix

password; please adapt to your needs

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos “” %u

This allows machine accounts to be created on the domain controller via the

SAMR RPC pipe.

The following assumes a “machines” group exists on the system

; add machine script = /usr/sbin/useradd -g machines -c “%u machine account” -d /var/lib/samba -s /bin/false %u

This allows Unix groups to be created on the domain controller via the SAMR

RPC pipe.

; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

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

; include = /home/samba/etc/smb.conf.%m

Some defaults for winbind (make sure you’re not using the ranges

for something else.)

; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

Setup usershare options to enable non-root users to share folders

with the net usershare command.

Maximum number of usershare. 0 (default) means that usershare is disabled.

; usershare max shares = 100

Allow users who’ve been granted usershare privileges to create

public shares, not just authenticated ones

usershare allow guests = yes

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

Un-comment the following (and tweak the other settings below to suit)

to enable the default home directory shares. This will share each

user’s home directory as \server\username

; comment = Home Directories
; browseable = no

By default, the home directories are exported read-only. Change the

next parameter to ‘no’ if you want to be able to write to them.

; read only = yes

File creation mask is set to 0700 for security reasons. If you want to

create files with group=rw permissions, set next parameter to 0775.

; create mask = 0700

Directory creation mask is set to 0700 for security reasons. If you want to

create dirs. with group=rw permissions, set next parameter to 0775.

; directory mask = 0700

By default, \server\username shares can be connected to by anyone

with access to the samba server.

Un-comment the following parameter to make sure that only “username”

can connect to \server\username

This might need tweaking when using external authentication schemes

; valid users = %S

Un-comment the following and create the netlogon directory for Domain Logons

(you need to configure Samba to act as a domain controller too.)

; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

Un-comment the following and create the profiles directory to store

users profiles (see the “logon path” option above)

(you need to configure Samba to act as a domain controller too.)

The path below should be writable by all users so that their

profile directory may be created the first time they log on

; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

Windows clients look for this share name as a source of downloadable

printer drivers

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

Uncomment to allow remote administration of Windows print drivers.

You may need to replace ‘lpadmin’ with the name of the group your

admin users are members of.

Please note that you also need to set appropriate Unix permissions

to the drivers directory for these users to have write rights in it

; write list = root, @lpadmin

path = /home/public/storage
writable = yes
browseable = yes
guest ok = yes
guest account = nobody
guest only = yes

path = /home/public/oldstorage
writable = yes
browseable = yes
guest ok = yes
guest account = nobody
guest only = yes

path = /home/public/storage2
writable = yes
browseable = yes
guest ok = yes
guest account = nobody
guest only = yes

We already have a working smb.conf file that we ship with Netrunner rolling designed to work with the Manjaro base, as well as with samba-mounter. The only requirement is that you need to use your admin password to grant access to mount samba shares using samba-mounter. Otherwise, you should not need any additional settings changed or added in order to browse and access to your network shares. This is unless you have windows set up to use passwords for file and printer sharing.

Netrunner Rolling is based on Arch/Manjaro not debian. If you wish to use a smb.conf file designed for such a system, you’ll need to follow the arch wiki on setting up user groups and share points, etc. that correspond with the settings used in such a file.

NOTE: The smb.conf file in the live session (overlay) is from upstream Manjaro and different than Netrunners default that is installed to the hard drive during installation (desktop overlay). The one installed to the system is in the netrunner-settings-samba package.

OK mate. I just uninstalled and then reisntalled the netrunner samba settings package as I have done more than once already.

I have the exact same issue. I cannot browse the network at all on any computer unless a windows computer is turned on and then I only have windows computers show in my workgroup called ‘workgroup’. I can connect by using hostname on linux computers and IP addresses on windows computers.

I have figured out a work around that maps network drives to the IP address of my netrunner box but I would like it to work properly. This has only happened when I changed my main PC with all the network storage to netrunner rolling. I had 17.01 as my first linux install and it worked fine on that. I prefer the arch version but if I have to change to debian bsed I guess I will have to do that. There should be no reason to do so though as this should work fine I don’t see anyone else complaning about this issue.

I dont think its smb.conf related as I have tried all diffrent types and ones and settings etc.

Thanks for you help.

That’s strange, I have no windows machines on my network at all and I can browse all of my Linux systems samba shares.
Are you logging into samba using your admin password on the Netrunner rolling box?
Are you turning off and turning back on samba after each change to the smb.conf file?

systemctl stop smbd nmbd[/code] edit and save the smb.conf file and then [code]systemctl start smbd nmbd

Netrunner Rolling is set up as a standalone server by default. Please take a look at the arch samba wiki for more ideas on how to configure samba under arch.

Also. be sure you remove any smb.conf file you have in place prior to reinstalling our package as it may not install properly if one already exists in the file system.