I am running 12.1/KDE4.9.1 on a desktop and laptop on my home network.
On the network are also three appliance class Linux machines.
All of these have samba configured and running.
I do not have SuSE Firewall enabled.
I have been able to browse all these shares from Dolphin, by selecting Network, Samba Shares which enters smb:/ in the URL bar.
In the past, hitting carriage return would find my workgroup, then selecting the workgroup name would display the names of the various machines.
Dolphin on both my primary machines is ver 4.9.1-310.1
I don’t use SAMBA all that much, but for the past year it has just worked.
I now am getting an error message when attempting to browse he workgroup (with smb:/ and enter)
“Unable to find any workgroups in your local network. This might be caused by an enabled firewall”
If I enter in the URL bar either smb://ipaddress_of_machine/ or smb://name_of_machine/ the shares available on those machines are displayed and I can browse on down the tree.
Any suggested places to look?
Again: SuSE Firewall is off, smb is running, nmb is running.
With Samba, in order to see all of the PC’s in your workgroup, one machine needs to be the master browser. There is a way the master is determined, but if all of the computers are the very same, they may be no master or they are all masters. Often, something got changed which was determining the master browser, but if you know the exact share, you could bring it up directly. I have some writeups on Samba and a bash script to setup a PC in a certain manner. Have a look here for the details:
Normally, we would ask to see your /etc/samba/smb.conf file, which you can do with the terminal command:
cat /etc/samba/smb.conf
But before you just post what you got, please read through these two blogs, the second will create a total SAMBA setup, replacing whatever you have created. What I do is use the smb.conf example from the first blog, replacing the default you will get in the second one. The second blog creates a great smb.conf file to look at other shares, but my first example is better on what you are sharing.
I have another bash script which is good at editing root owned files like smb.conf you can find here:
The group should elect and remember the master browser, particularly if it has successfully done so in the past.
This seems to me to hint of the bug where the RPM systemd-sysvinit interferes with Samba. Check whether you have systemd-sysvinit or it’s alternative package sysvinit-init installed. This command will tell you:
zypper se sysvinit-init systemd-sysvinit
If the result says that the dodgy package systemd-sysvinit is installed, then uninstall it. The alternate package sysvinit-init should then auto-install. Then reboot and see if there’s been an improvement.
If however the bodgie package is not installed, or if replacing it does not help, then please post here the contents of the samba config file smb.conf (located at /etc/samba/smb.conf).
Always good to have the heavy hitters from each hemisphere on task
James - Your post had the same Blog referenced twice. Did you intend that? I have SWAT up and running. I don’t ever recall having designated a master browser.
Swerdna - I did in fact, for no good reason, install systemd-sysvinit on both of my primary Linux machines on this network. I have reverted both to sysvinit-init and rebooted, but my browse the workgroup problem remains as described above.
Here is my smb.conf; globals on both machines are the same, with the exception of the Server String.
I built this a couple years back from your user security example, has worked well until now.
[global]
netbios name = PVE-LinuxSRV5
server string = PVE-LinuxSRV5(12.1) Samba server
workgroup = capenet
security = user
hosts allow = 127. 192.168.10.
interfaces = 127.0.0.1/8 192.168.10.0/24
bind interfaces only = yes
remote announce = 192.168.10.255
remote browse sync = 192.168.10.255
printcap name = cups
load printers = yes
cups options = raw
printing = cups
guest account = nobody
log file = /var/log/samba/samba.log
max log size = 1000
null passwords = no
username level = 6
password level = 6
unix password sync = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain master = No
domain logons = No
logon drive = m:
logon home = \\%L\homes\%u
logon path = \\%L\profiles\%u
logon script = %G.bat
time server = no
name resolve order = wins lmhosts bcast
wins support = No
wins proxy = no
dns proxy = no
preserve case = yes
short preserve case = yes
client use spnego = no
client signing = no
client schannel = no
server signing = no
server schannel = no
nt pipe support = yes
nt status support = yes
allow trusted domains = no
obey pam restrictions = yes
enable spoolss = yes
client plaintext auth = no
disable netbios = no
follow symlinks = no
update encrypted = yes
pam password change = no
passwd chat timeout = 120
hostname lookups = no
username map = /etc/samba/smbusers
smb passwd file = /etc/samba/smbpasswd
passwd program = /usr/bin/passwd '%u'
passwd chat = *New*password* %n
*ReType*new*password* %n
*passwd*changed*
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
machine password timeout = 120
idmap uid = 99997-99999
idmap gid = 99997-99999
winbind use default domain = yes
winbind separator = @
winbind cache time = 360
winbind trusted domains only = yes
winbind nested groups = no
winbind nss info = no
usershare allow guests = No
passdb backend = smbpasswd
ldap suffix =
wins server =
[homes]
comment = Home Directories
path = /home
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
public = no
printable = no
share modes = no
locking = no
[MediaShare]
# added cjm 10/24/09
# This is a Swerdna Share#7
path = /home/SambaShares/Media
read only = no
create mask = 770
force create mode = 770
[Backup_Drive]
# added cjm 05/06/2011
# This is a Swerdna Share#7
path = /backup
read only = no
create mask = 770
force create mode = 770
## Share disabled by YaST
# [netlogon]
# comment = Network Logon Service
# path = /home/netlogon
# read only = Yes
# available = yes
# browseable = yes
# writable = no
# guest ok = no
# public = no
# printable = no
# share modes = no
# locking = no
## Share disabled by YaST
# [profiles]
# comment = User Profiles
# path = /var/samba/profiles
# read only = No
# available = yes
# browseable = no
# writable = yes
# guest ok = no
# public = no
# printable = no
# locking = no
# create mode = 0600
# directory mask = 0700
# create mask = 0600
# [printers]
# comment = All Printers
# path = /var/spool/samba
# browseable = yes
# writable = no
# guest ok = no
# public = no
# printable = yes
# share modes = no
# locking = no
# [pdf-documents]
# path = /home/pdf-documents
# comment = Converted PDF Documents
# available = yes
# browseable = yes
# writeable = yes
# guest ok = yes
# [pdf-printer]
# path = /tmp
# comment = PDF Printer Service
# printable = yes
# guest ok = yes
# use client driver = yes
# printing = bsd
# print command = /usr/bin/gadmin-samba-pdf %s %u
On 09/18/2012 12:16 PM, cmcgrath5035 wrote:
>
> Always good to have the heavy hitters from each hemisphere on task
>
> James - Your post had the same Blog referenced twice. Did you intend
> that? I have SWAT up and running. I don’t ever recall having designated
> a master browser.
>
>
> Swerdna - I did in fact, for no good reason, install systemd-sysvinit
> on both of my primary Linux machines on this network. I have reverted
> both to sysvinit-init and rebooted, but my browse the workgroup problem
> remains as described above.
>
> Here is my smb.conf; globals on both machines are the same, with the
> exception of the Server String.
> I built this a couple years back from your user security example, has
> worked well until now.
>
snip
>
>
> --------------------
>
>
Holy mackeral, lots of stuff in [global].
I suggest you replace all of the [global] stanza witk this:
[global]
netbios name = PVE-LinuxSRV5
server string = PVE-LinuxSRV5(12.1) Samba server
passdb backend = tdbsam
workgroup = capenet
name resolve order = bcast host lmhosts wins
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
use client driver = yes
map to guest = Bad User
local master = yes
os level = 33
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
You can do that with copy/paste in an editor.
Open editor with this command (if using KDE):
Thanks to you both for the suggestions and references.
James - Both your Blogs are a good read.
I have them bookmarked for future reference.
So your are a Gear Head as well as a Script_Guru, eh?
Swerdna - yes, Global was messy. I started from one of your examples a couple years back, probably tweaked and got sloppy as to documenting why.
It was working until this recent event.For completeness, I should mention that I can’t say for sure this worked after early June, 2012.
I was away from the home network and machines June-August; performed all the accumulated updates, including new kernel, two weeks ago.
I do not recall if I tried to browse my workgroup with success after those.
I’ll assume for now that one or more updates over the summer revealed the flaws in my global.
I am good at cut and paste so used Swerdna’s suggested [Global] section, restarted nmb and smb, and All Is Well again.
I see you added a
local master = yes
There is no true (always on)server on this network, mostly peer to peer file access when my Windows machines are active
or as a backup for my preferred NFS connections.
Should (must?) there be only one local master?
A quick review of James’ script looks like it would make all machines “local master = yes”
On 09/18/2012 10:46 PM, cmcgrath5035 wrote:
>
> Thanks to you both for the suggestions and references.
>
> James - Both your Blogs are a good read.
> I have them bookmarked for future reference.
> So your are a Gear Head as well as a Script_Guru, eh?
>
> Swerdna - yes, Global was messy. I started from one of your examples a
> couple years back, probably tweaked and got sloppy as to documenting
> why.
> It was working until this recent event.
> For completeness, I
> should mention that I can’t say for sure this worked after early June,
> 2012.
> I was away from the home network and machines June-August; performed
> all the accumulated updates, including new kernel, two weeks ago.
> I do not recall if I tried to browse my workgroup with success after
> those.
> I’ll assume for now that one or more updates over the summer revealed
> the flaws in my global.
>
>
> I am good at cut and paste so used Swerdna’s suggested [Global]
> section, restarted nmb and smb, and All_Is_Well again.
>
> I see you added a
> Code:
> --------------------
>
> local master = yes
>
> --------------------
>
>
> There is no true (always on)server on this network, mostly peer to peer
> file access when my Windows machines are active
> or as a backup for my preferred NFS connections.
>
> Should (must?) there be only one local master?
> A quick review of James’ script looks like it would make all machines
> “local master = yes”
>
>
> Thanks!
>
>
The line “local master = yes” does not make that computer the dominant
master. That line only allows the computer to take part in the process
of resolving names of computers against IP addresses.
If you had the additional line “preferred master = yes” then the
computer would insist on being the dominant local master. So such a
computer would need to be an always-on member of the workgroup.
But the way I set it up (without the line about “preferred master”) is
the way that’s appropriate for a sometimes-on member of the workgroup.
Fear not, it’s good to have the line “local master = yes”. That makes it
more or less like Mr Average.
[the 33 makes it kinda spiffy, but that’s another story]
