I have used the same smb.conf file from Fedora and Kubuntu and have since migrated to OpenSuSE 12.2 and then 12.3 RC1. With the same config file on OpenSuSE, Samba just doesn’t want to work. I can see my SuSE machine from another ubuntu machine and sometimes a windows machine, but I can never browse the files on the network. Lately I can’t even see the SuSE machine with my phone (android) but can see it with Ubuntu, but still cannot browse the shares.
The firewall is disabled in SuSE. It seems that OpenSuSE has never been easy to setup with samba. I have always had problems getting Samba working with SuSE. I typically use KDE and in Yast I setup samba to allow users to share their home directories. I noticed there’s share options in dolphin within KDE. Am I not supposed to mess with those options? What could I be doing wrong?
I’ll post my smb.conf next time I reboot. I’m in Windows now doing some troubleshooting.
for me it is exactly viceversa, in openSUSE, all versions I’ve used, SAMBA server is working perfectly just after some clicks in Yast configuration module.
OpenSuSE has been the best at everything I’ve needed to do, except being cooperative with Samba. Maybe I just have bad luck. Anyway, here’s the smb.conf that was generated after I went and set it up through Yast. I’m using Samba 3.6.12-59.2.1 with OpenSuSE 12.3 RC1.
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
workgroup = GALAXY
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = Yes
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = Yes
domain master = Yes
local master = Yes
os level = 65
preferred master = Yes
security = user
usershare max shares = 100
wins server =
wins support = No
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = Yes
read only = No
writeable = Yes
gues ok = Yes
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
I just got my other smb.conf file that I’ve been using with Kubuntu and Fedora and another file server I have setup. With this config file used with Open SuSE, the computer doesn’t show up at all on the network from the other machines.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = galaxy
#force user = dave
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# 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
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# 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 = 127.0.0.0/8 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
#### Debugging/Accounting ####
# 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 #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# 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 <<kahan@informatik.tu-muenchen.de> 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
*Retype\snew\s*\spassword:* %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 ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if '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 below)
; 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
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ 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
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# 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
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# 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 director as \\server\username
;[homes]
; 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
# The following parameter makes sure that only "username" can connect
#
# 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.)
;[netlogon]
; 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
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
wins support = no
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
guest ok = yes
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = yes
# 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
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[TITAN home]
path = /home/dave
comment = Home dir on Titan
available = yes
browsable = yes
public = yes
writable = yes
I’m moving back to the default smb.conf generated by Yast to troubleshoot this.
On 2/9/2013 3:46 PM, DupermanDave wrote:
<snip>
>
> OpenSuSE has been the best at everything I’ve needed to do, except
> being cooperative with Samba. Maybe I just have bad luck. Anyway, here’s
> the smb.conf that was generated after I went and set it up through Yast.
> I’m using Samba 3.6.12-59.2.1 with OpenSuSE 12.3 RC1.
>
>
>
>
> Code:
> --------------------
>
> # smb.conf is the main Samba configuration file. You find a full commented
> # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
> # samba-doc package is installed.
> [global]
> workgroup = GALAXY
> passdb backend = tdbsam
> printing = cups
> printcap name = cups
> printcap cache time = 750
> cups options = raw
> map to guest = Bad User
> include = /etc/samba/dhcp.conf
> logon path = \%L\profiles.msprofile
> logon home = \%L%U.9xprofile
> logon drive = P:
> usershare allow guests = Yes
> add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
> domain logons = Yes
> domain master = Yes
> local master = Yes
> os level = 65
> preferred master = Yes
> security = user
> usershare max shares = 100
> wins server =
> wins support = No
<snip>
>
> --------------------
>
Dave;
Did you really intend for the openSUSE machine to be configured as a PDC on a
Samba domain? If so are the other machines joined to the domain? For proper
name resolution add the following to the above smb.conf:
I’m having some progress now. I decided to start fresh and delete the smb.conf and start over with Yast. I deleted all shares and only have my home folder share now and I also have it so that “Retrieve WINS server from DHCP” is enabled. Now I have no problems seeing the computer or folders from other machines.
Now is the tricky part. I can see the folders I’m sharing, but I cannot access them. It asks for a username and password. In the past, I added "force user = " and set it to my user on the host machine. I need some advisement here on what I should do next. I want to be able to access everything on the computer without needing a username or password.
>
> Setting it up as a PDC is the only way I’ve seen it done in tutorials
> I’ve found while trying to troubleshoot the problem on my own.
>
> Is there a way to not setup users with samba and just give access to
> any user?
>
>
Dave;
You’ve been reading the wrong HowTos. See the one I posted by Swerdna.
To make Samba setup as a simple Workgroup computer just remove these two
parameters from /etc/samba/smb.conf.
domain logons = Yes
domain master = Yes
To give access to any user, you can set “security = share”, however this is
depreciated and no longer maintained. (It is removed from Samba4). The best
way is to give guest access to your shares. Keep in mind that Samba can not
violate Linux permissions, so guest shares ordinarily set the “other” permission
to allow the kind of access they want for the share. This Howto, also by
Swerda, shows a number of classical share examples:
Alright. I guess we can mark this as solved. I just went ahead and did the “sudo smbpsswd” thing and crated an account that way. Thanks for all the help and pointers everyone!
Nice it works. Next time try to get information based on the distribution you are using. And next time try to write openSUSE instead of your variant of Shift key usage. rotfl!
Lol. Sorry, I’m used to SuSE before it went “open”. It’s a habit.
Anyway, the problem seems to be back. After a reboot, it seems I can see the openSUSE computer on the network, but I cannot browse the computer. If I try and browse locally on the machine through KDE’s network browser, I get “Cannot connect to host for smb://titan/”
My smb.conf is as follows:
[global]
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = No
domain master = No
security = user
usershare allow guests = Yes
usershare max shares = 100
wins server =
wins support = No
workgroup = GALAXY
[Titan Home]
comment = Linux home
inherit acls = Yes
path = /home/dave
read only = No
## Share disabled by YaST
# [netlogon]
And I re-ran smbpasswd -s <username> and created another user and password just in case that was part of the issue.
-edit-
GRRRRRRRRRRRRR. It’s being very sporadic. It just magically started working as I went to check on it through Dolphin. No reboot, no router reset, no config changes. I’ll keep an eye on it and see how it works out.
> And I re-ran smbpasswd -s <username> and created another user and
> password just in case that was part of the issue.
>
>
> -edit-
>
> GRRRRRRRRRRRRR. It’s being very sporadic. It just magically started
> working as I went to check on it through Dolphin. No reboot, no router
> reset, no config changes. I’ll keep an eye on it and see how it works
> out.
Dave;
After doing an update on openSUSE 12.2, I round a problem with my file server. I decided to do a fresh install of 12.2 and I followed a guide I made while I was doing the previous installation.
The settings are identical to the previous installation. But now I can see the computer on the network, but I cannot browse it.
Is there something missing?
Is the version of samba you’re using now the same version as when you previously had 12.2?
As an update yo my previous post, I just rebooted my machine and my openSUSE computer is once again out of the workgroup. I can’t see it or browse it. Perhaps I should wait until 12.3 is released?
I believe the update that was done was a kernel update and that probably threw my installation out. I reinstalled using the dvd I wrote of openSUSE 12.2 I downloaded.
The samba version, I’m using is the latest one I believe and the same one that I had installed previously. With all this, I’m tempted to switch over to debian.
This is getting very frustrating. I’ve just spent the whole night trying to solve this. I’ve done so far 5 reinstallations of openSUSE 12.2, just to make sure that I’ve not missed anything.
I can now guarantee for certain that my installation is correct and exactly how it was just before the update. And yet still this thing just won’t work. Having spent now a total of 18 hours on this, the whole night, I’m tired and just about to start kicking and screaming.
I am not sure again why I started reading your thread (may be the odd way you typed tthe word, but that is settled now),
because I am not a SAMBA user at all and am of no use to you. But glancing through yourr thread it looks like a bit of a mess. You are talking now and then about 12.3 (which is not releaseed and 12.3 problems should go into the Pre-Release/Beta forum, most people here use the supported versions and are not able to replay your problem on 12.3).
It is also not clear to me if you quitted using docs written for other distributions. My general experience here is that people using Swerdna’s web-site at openSUSE SuSE Linux HOWTOs and Tutorials by Swerdna are perfectly able to get a running Samba environment. It could of course be that you have some special problematic whishes.
In any case, I think that after a fresh 12.2 install (one is sufficient for most computers to have a fresh ystem ) using only the versions that come with 12.2 and using Swerdna’s advices and still having problems, you should reformulate what the prblem is, doucumented with configuration files. So that everybody gets a consistant vision of what you have installed, try to achieve and how you configured.
When you start changing things in the time span that other people try to read, understand and answer (and do not forget we are around the globe and some of us need some sleep / working time / what all) there will be misunderstandings around…
I don’t get it. I kept the settings exactly as they were before and it didn’t work. Now suddenly after a reboot, it does. Some things just don’t make any sense. I’ve rebooted it countless times with the same settings. What made it work now?
More importantly, if the server has to be rebooted anytime now, how can I be sure that I won’t face the same issue again?
Not really. That question is pretty much rhetorical. I keep hearing that OpenSUSE is more for a full on desktop rather than a server. Not sure if that is any where near the truth. It pretty much seems that way by the presentation on their site.
) using only the versions that come with 12.2 and using Swerdna’s advices and still having problems, you should reformulate what the prblem is, doucumented with configuration files. So that everybody gets a consistant vision of what you have installed, try to achieve and how you configured.