Hi, I’m new on linux so I’m sorry if my questions are stupid.
I have installed OpenSuse 13.2 with KDE desktop on my laptop. On my lan, I also have a NAS (fixed ip and a desktop running W8.1). Everything is configured to be on the workgroug WORKGROUP.
I have told openSuse to be in this workgroup (WORKGROUP) by using Yast. In dolphin, when I click on Network>Samba Shares, I got an error message telling me “No workgroup found on your local network. Thus might be because of an enabled fire-wall” (approximate message, as I’m using openSuse in french…)
I tried to temporary deactivate the firewall, then when I click on Network>Samba shares i have a single Workgroup (not WORKGROUP) icon, and when I click on it, I only have my Linux Laptop.
On the other hand, even with firewall activated, i can acces the folders on my NAS without any issue by just typing in Dolphin in the adress bar smb://IP of the NAS/
Please Help!
Here is smb.conf for information:
[global]
workgroup = WORKGROUP
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 = No
security = domain
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
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
On 5/8/2015 5:46 AM, Benoit wrote:
>
> Hi, I’m new on linux so I’m sorry if my questions are stupid.
>
> I have installed OpenSuse 13.2 with KDE desktop on my laptop. On my lan,
> I also have a NAS (fixed ip and a desktop running W8.1). Everything is
> configured to be on the workgroug WORKGROUP.
>
> I have told openSuse to be in this workgroup (WORKGROUP) by using Yast.
> In dolphin, when I click on Network>Samba Shares, I got an error message
> telling me “No workgroup found on your local network. Thus might be
> because of an enabled fire-wall” (approximate message, as I’m using
> openSuse in french…)
>
> I tried to temporary deactivate the firewall, then when I click on
> Network>Samba shares i have a single Workgroup (not WORKGROUP) icon, and
> when I click on it, I only have my Linux Laptop.
>
> On the other hand, even with firewall activated, i can acces the folders
> on my NAS without any issue by just typing in Dolphin in the adress bar
> smb://IP of the NAS/
>
> Please Help!
>
>
Benoit;
I noticed that you have “security = domain” in /etc/smb.conf. This setting is only be for a member server of an NT
style domain. If you do not have a PDC on your network, remove this line and use the default value (security = user).
In addition to allowing the Samba Server, Netbios Server and Samba Client through the firewall, be sure to disable
AppArmor at least while you are testing.
PS. Your smb.conf content is not visible on the nntp side and only by accident did I see it. I assume you edited your
original post. That is why edits are a bad idea.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
Thank you venzkep for your help. I modified smb.conf as you suggested and it helps a bit. However I’m still facing a couple issues.
With firewall and app armor turned off (for tests), I can see in Dolphin my NAS (but not my desktop PC on W8.1). Then when I click on my NAS, I get a list of folders which are not at all the smb shares configured in my NAS (it seems to be the shares configures in smb.conf instead…)
Here is /etc/samba/smb.conf (as not visible in the first edited post):
I read man smb.conf but i’m quite lost… Except for the modification proposed by venzkep, it is as per openSuse installation…
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 = WORKGROUP
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 = No
security = user
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
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
here is ~>smbtree:
Enter boubou’s password:
WORKGROUP
\STB01 Neufbox
\STB01\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\STB01\print$ Printer Drivers
\STB01\groups All groups
\STB01\users All users
\STB01\profiles Network Profiles Service
\PC-FIXE
\PC-FIXE\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\PC-FIXE\print$ Printer Drivers
\PC-FIXE\groups All groups
\PC-FIXE\users All users
\PC-FIXE\profiles Network Profiles Service
\LINUX-Y1OC Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64
\LINUX-Y1OC\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\LINUX-Y1OC\print$ Printer Drivers
\LINUX-Y1OC\groups All groups
\LINUX-Y1OC\users All users
\LINUX-Y1OC\profiles Network Profiles Service
\BENHDD Home Media Network Hard Drive
\BENHDD\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\BENHDD\print$ Printer Drivers
\BENHDD\groups All groups
\BENHDD\users All users
\BENHDD\profiles Network Profiles Service
STB01 is the TV decoder. It “normally” shares its internal hard drive.
PC-FIXE is the desktop PC, sharing only a Download folder
LINUX-Y1OC is this laptop PC, sharing in my understanding what is configured in smb.conf
BENHDD is the NAS, sharing a few folders, among them Movies, Music, BackUps, …
Again, I can acces in Dophin the folders of my nas by typing in adress bar smb://IP OF NAS/Movies/ for instance.
I can also mount the remote folder with : sudo mount.cifs //192.168.1.59/Movies /mnt/movies -o username=XXXX,password=YYYYYY -v
But I would like to have my network shared folders accessible directly in Dolphin.
On 5/9/2015 8:36 AM, Benoit wrote:
>
> Thank you venzkep for your help. I modified smb.conf as you suggested
> and it helps a bit. However I’m still facing a couple issues.
>
> With firewall and app armor turned off (for tests), I can see in Dolphin
> my NAS (but not my desktop PC on W8.1). Then when I click on my NAS, I
> get a list of folders which are not at all the smb shares configured in
> my NAS (it seems to be the shares configures in smb.conf instead…)
>
<snip>
>
> STB01 is the TV decoder. It “normally” shares its internal hard drive.
> PC-FIXE is the desktop PC, sharing only a Download folder
> LINUX-Y1OC is this laptop PC, sharing in my understanding what is
> configured in smb.conf
> BENHDD is the NAS, sharing a few folders, among them Movies, Music,
> BackUps, …
>
> Again, I can acces in Dophin the folders of my nas by typing in adress
> bar smb://IP OF NAS/Movies/ for instance.
> I can also mount the remote folder with : sudo mount.cifs
> //192.168.1.59/Movies /mnt/movies -o username=XXXX,password=YYYYYY -v
>
> But I would like to have my network shared folders accessible directly
> in Dolphin.
>
>
Benoit;
The need to drill down on shares seem to be a long time problem with Dolphin. As long as you can access the shares from
the location bar with: smb://<Hostname or IP>, there is not much I can tell you.
As a work around you can add a iink on your desktop that will open Dolphin to your share. On the desktop right click
and choose “Create New”, then “Link to Location(URL)…”. In the popup enter a name for the link on the first line and
then smb://<Hostename or IP> (or smb://<hostname>/<sharename>) on the second line
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
FWIW, I have to access remote samba shares in my workplace. I access on the fly via Dolphin, and have the locations save in ‘Places’. The URLs look like
Thank you again for your help. I don’t think I’m facing a dolphin issue, I got the same result in Konqueror, and again the same result in terminal with smbtree. Basically samba detects all smb devices on the network, but fails to find their smb shares. But it only fails when connecting through hostname. For instance if I type in the adress bar of either Dolphin or Konqueror smb://benhdd/Movies (benhdd being my NAS hostname), I got an error message telling me that the folder doesn’t exists. But if I type smb://192.168.1.59/Movies (IP adress of my NAS).
To be more specific, when I type in Dolphin adress bar smb://foo/ (which of course doesn’t exist on my network), I got the same result that when clicking on Benhdd in samba shares (or when typing smb://benhdd/) : I got the list of shares configured in smb.conf (I confirmed it by keeping only the [global] and [printers] sections in smb.conf).
I sure can find an alternative way but I would really prefer to understand what is my configuration issue. I would be ok with a dolphin issue while smbtree provides me with the correct list of shares. As I have the same result in Dolphin, Konqueror, Smbtree and smb4k, I’m sure the issue comes from samba (or from the way it is configured).
I have modified nsswitch.conf and tried different versions, ending with:
passwd: files winbind
group: files winbind
shadow: files winbind
#hosts: files mdns_minimal [NOTFOUND=return] dns // as per install
host: files wins dns
networks: files dns
services: files
protocols: files
rpc: files
ethers: files
netmasks: files
#netgroup: files nis //as per install
netgroup: nisplus
#publickey: files //as per install
publickey: nisplus
bootparams: files
automount: files nis
aliases: files
I also checked my windbind and samba packages.
This is not changing anything to the situation. I still can access smb shares by directly typing IP adress, but neiher Dolphin nor smbtree (orsmb4k, or Konqueror) can “explorate and browse” my local network.
It’s quite disapointing at this stage, as it works perfectly on my desktop W8.1, on my laptop W7 partition, or on my android tablet. And I’m running out of ideas… I feel like coming back to the dark years of W95 .
On 5/10/2015 4:26 AM, Benoit wrote:
<snip>
>
> Thank you again for your help. I don’t think I’m facing a dolphin issue,
> I got the same result in Konqueror, and again the same result in
> terminal with smbtree. Basically samba detects all smb devices on the
> network, but fails to find their smb shares. But it only fails when
> connecting through hostname. For instance if I type in the adress bar of
> either Dolphin or Konqueror smb://benhdd/Movies (benhdd being my NAS
> hostname), I got an error message telling me that the folder doesn’t
> exists. But if I type smb://192.168.1.59/Movies (IP adress of my NAS).
>
> To be more specific, when I type in Dolphin adress bar smb://foo/ (which
> of course doesn’t exist on my network), I got the same result that when
> clicking on Benhdd in samba shares (or when typing smb://benhdd/) : I
> got the list of shares configured in smb.conf (I confirmed it by keeping
> only the [global] and [printers] sections in smb.conf).
>
> I sure can find an alternative way but I would really prefer to
> understand what is my configuration issue. I would be ok with a dolphin
> issue while smbtree provides me with the correct list of shares. As I
> have the same result in Dolphin, Konqueror, Smbtree and smb4k, I’m sure
> the issue comes from samba (or from the way it is configured).
>
>
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
On 5/10/2015 1:15 PM, PV wrote:
> On 5/10/2015 4:26 AM, Benoit wrote:
> <snip>
>>
>> Thank you again for your help. I don’t think I’m facing a dolphin issue,
>> I got the same result in Konqueror, and again the same result in
>> terminal with smbtree. Basically samba detects all smb devices on the
>> network, but fails to find their smb shares. But it only fails when
>> connecting through hostname. For instance if I type in the adress bar of
>> either Dolphin or Konqueror smb://benhdd/Movies (benhdd being my NAS
>> hostname), I got an error message telling me that the folder doesn’t
>> exists. But if I type smb://192.168.1.59/Movies (IP adress of my NAS).
>>
>> To be more specific, when I type in Dolphin adress bar smb://foo/ (which
>> of course doesn’t exist on my network), I got the same result that when
>> clicking on Benhdd in samba shares (or when typing smb://benhdd/) : I
>> got the list of shares configured in smb.conf (I confirmed it by keeping
>> only the [global] and [printers] sections in smb.conf).
>>
>> I sure can find an alternative way but I would really prefer to
>> understand what is my configuration issue. I would be ok with a dolphin
>> issue while smbtree provides me with the correct list of shares. As Ib(d)
>> have the same result in Dolphin, Konqueror, Smbtree and smb4k, I’m sure
>> the issue comes from samba (or from the way it is configured).
>>
>>
>
>
Sorry that was a premature send. I now understand that you can contact other shares only by IP and never by name.
nmb(d) provides netbios name service for smb(d). Is nmb running?
systemctl status nmb
If it is not running you will need to start it.
su -
systemctl enable nmb
systemctl start nmb
The first command makes sure it willl start at boot and the second starts it on a running system.
The following all need to be allowed services through the firewall
Samba Service, Netbios Service and Samba Client (YaST2 > Security and Users > Firewall > Allowed Services).
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
Yes, I can access the shares by IP, but not by name, which seems to be the way Dolphin try to access.
After reboot:
boubou@linux-y1oc:~> systemctl status nmb
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
Active: failed (Result: timeout) since lun. 2015-05-11 20:49:39 CEST; 55s ago
Process: 760 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=killed, signal=TERM)
Main PID: 760 (code=killed, signal=TERM)
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for interface ..."
It’s a little bit weird, but as I’m connecting per wifi, I guess the service is trying to start before I fill my Kwallet password allowing to connect to the wifi (next issue when the current one will be solved???)
In firewall, I have allowed samba client, samba server and netbios server both in DMZ and external area.
Then I try:
boubou@linux-y1oc:~> sudo systemctl start nmb
boubou@linux-y1oc:~> systemctl status nmb
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
Active: active (running) since lun. 2015-05-11 20:56:07 CEST; 11s ago
Main PID: 1950 (nmbd)
Status: "nmbd: ready to serve connections..."
CGroup: /system.slice/nmb.service
└─1950 /usr/sbin/nmbd -D
But both dolphin and smbtree still provide the same results:
boubou@linux-y1oc:~> smbtree
Enter boubou's password:
WORKGROUP
\\STB01 Neufbox
\\STB01\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\\PC-FIXE
\\PC-FIXE\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\\LINUX-Y1OC Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64
\\LINUX-Y1OC\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
\\BENHDD Home Media Network Hard Drive
\\BENHDD\IPC$ IPC Service (Samba 4.1.17-5.1-3375-SUSE-oS13.2-x86_64)
Note that Dolphin has never displyed STB01 or PC-FIXE, just BenHDD, and even not always… smbtree seems much more reliable.
No change after service smb -restart.
No change after firewall deactivation.
I now have a simplified smb.conf:
# 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 = WORKGROUP
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
usershare allow guests = No
security = user
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
It’s a little bit weird, but as I’m connecting per wifi, I guess the service is trying to start before I fill my Kwallet password allowing to connect to the wifi (next issue when the current one will be solved???)
I would consider reconfiguring your wireless connection with ‘All users may connect with this network’. Then it won’t need to rely on kwallet and will take care of authentication itself, and be up by the time the desktop is up and running.
nsswitch.conf as per previous post
I note that you have ‘host:’ instead of ‘hosts:’
#hosts: files mdns_minimal [NOTFOUND=return] dns // as per install
host: files wins dns
For reference, I have
hosts: files wins mdns_minimal [NOTFOUND=return] dns
I corrected the typo in nsswitch.conf and configured the wireless connection for accessibility to all users.
And everything works OK!!!
Thank you so much to both of you.
.