I tried all ways to share folders on OpenSUSE 13.1 using SAMBA, but without success. Frankly, I do not know what to do to resolve this situation.
Among my actions are taken…
I can make the server work normally and without error including its parameters (testparm), but I can not access it from another machine (Linux or Windows) using “smb://[MACHINE_IP]/[SHARE_NAME]” or “[MACHINE_IP][SHARE_NAME]”! I also tested using the machine itself.
Nothing seems to make samba work. What was supposed to be a simple and ordinary thing in other distributions became a nightmare. I’m beginning to think that this is a problem in the distribution itself!
FYI: Since the last Samba update in December, Samba could not create necessary files on startup because AppArmor blocks it.
The latest AppArmor update should fix this though.
Have same problem as mentioned, same samba version and distro. It worked just fine for me after I’ve installed openSUSE 13.1 about a month ago (only was necessary to disable app armor). And now it suddenly stopped to work, starts but does not share (I fixed some in config - cause I even was unable to start), do no know why. From localhost it asks me for user name and password (previously was not as guest access are enabled), and does not connect from Windows machine at all? What is wrong here? New samba version after rpm upgrade or what? Could You summarize the solution for me please?
I have a similar problem, although samba is >running<. I have gone through about 100 tutorials, changed smb.conf from simple to complicated and back to simple and nothing at all works. I had samba running ok with openSUSE 12.2, now trying to implement 13.1.
I know the revisions to smb.conf are being propagated via restarting nmb and smb, because I have added and removed shares, etc. and they display via the browser. HOWEVER, every implementation ends up exactly the same:
I can browse my server home directory via //smb/[server]/[user] but I cannot write to it. I cannot gain access to any other share (although one share is in my user tree, so I can access it when I connect to my home directory). I have also removed and re-created my smb passwords, doesn’t help. I’ve verified that my linux user on the server has r/w access to the exported directories. I also tried the suggestion here to turn apparmor off.
I’ve checked via dolphin smb:/, via smbclient, and via windows xp network browser. All have the exact same result – I can browse my server’s home directory remotely, I can’t obtain write privileges and I can’t access the other shares. The system is using tdbsam – I tried deleting the database files and reconstructing them. That did not work either. With smbclient I was able to log into the “sharetest” share (presumably available to all users per below smb.conf), but commands such as “dir” result in “NT_STATUS_ACCESS_DENIED”.
smb.conf [latest version]
[global]
workgroup = WORKGROUP
security = user
netbios name = MAIN
[homes]
valid users = %S
browseable = no
read only = No
create mask = 0700
directory mask = 0700
[shared016]
comment = shared016
path = /home/[user]/lan/shared016
read only = No
[sharetest]
comment = sharetest
path = /var/test
read only = No
valid users = @users
force group = users
create mask = 0660
directory mask = 0771
writable = yes
I searched YAST for “smb” and discovered “pam_smb”. I added it and now I can r/w access the share I intended to be r/w for all users. Still not solved for home directory and shared016 but I will go back and look at the smb.conf again – I think it is a positive that I can access “something” in any event. Especially as in my case, I only wanted a shareable windows folder anyway.
It seems to me if pam_smb is needed, it should be a dependency in the samba install, but what do I know?
pam_smb is definitely not needed for a writable Samba share.
But of course the corresponding user (for guest access this is most likey “nobody”) has to have read, write and execute permissions to that directory.
If you only want read access, read and execute permissions are sufficient of course.
Below I put the outputs of the smbd and nmbd logs!
These logs covering the time when I start the service to when I try to access the share from another computer!
vim /var/log/samba/log.smbd
"
[2014/02/10 11:58:31, 0] …/source3/smbd/server.c:1198(main)
smbd version 4.1.3-3.12.1-3127-SUSE-oS13.1-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2013
[2014/02/10 11:58:31.412297, 0] …/source3/smbd/server.c:1278(main)
standard input is not a socket, assuming -D option
"
vim /var/log/samba/log.nmbd
"
[2014/02/10 11:58:26, 0] …/source3/nmbd/nmbd.c:902(main)
nmbd version 4.1.3-3.12.1-3127-SUSE-oS13.1-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2013
[2014/02/10 11:58:26, 0] …/source3/nmbd/nmbd.c:941(main)
standard input is not a socket, assuming -D option
"
"
[2014/02/10 11:58:31, 0] …/source3/smbd/server.c:1198(main)
smbd version 4.1.3-3.12.1-3127-SUSE-oS13.1-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2013
[2014/02/10 11:58:31.412297, 0] …/source3/smbd/server.c:1278(main)
standard input is not a socket, assuming -D option
"
/var/log/samba/log.nmbd
"
[2014/02/10 11:58:26, 0] …/source3/nmbd/nmbd.c:902(main)
nmbd version 4.1.3-3.12.1-3127-SUSE-oS13.1-x86_64 started.
Copyright Andrew Tridgell and the Samba Team 1992-2013
[2014/02/10 11:58:26, 0] …/source3/nmbd/nmbd.c:941(main)
standard input is not a socket, assuming -D option
"
**/bin/systemctl status smb.service **
"
smb.service - Samba SMB Daemon
Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled)
Active: active (running) since Mon 2014-02-10 11:58:31 BRST; 27min ago
Process: 8427 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 8428 (smbd)
CGroup: /system.slice/smb.service
├─8428 /usr/sbin/smbd
└─8431 /usr/sbin/smbd
Feb 10 11:58:31 linux-tc6s systemd[1]: Starting Samba SMB Daemon…
Feb 10 11:58:31 linux-tc6s smbd[8427]: [2014/02/10 11:58:31.412297, 0] …/source3/smbd/server.c:1278(main)
Feb 10 11:58:31 linux-tc6s smbd[8427]: standard input is not a socket, assuming -D option
Feb 10 11:58:31 linux-tc6s systemd[1]: Started Samba SMB Daemon.
"
**/bin/systemctl status nmb.service **
"
nmb.service - Samba NMB Daemon
Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
Active: active (running) since Mon 2014-02-10 11:58:26 BRST; 28min ago
Process: 8418 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 8419 (nmbd)
CGroup: /system.slice/nmb.service
└─8419 /usr/sbin/nmbd
Feb 10 11:58:26 linux-tc6s systemd[1]: Starting Samba NMB Daemon…
Feb 10 11:58:26 linux-tc6s systemd[1]: Started Samba NMB Daemon.
linux-tc6s:/home/brlight #
"
/etc/samba/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
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
[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
[shared]
path = /home/brlight/shared
writable = yes
browsable = yes
guest ok = yes
guest only = yes
create mode = 0777
directory mode = 0777
"
I had another look at your smb.conf and noticed that you didn’t specify the name of your server with the option “netbios name”.
If I remove that option from my smb.conf I get the same NT_STATUS_IO_TIMEOUT error as you, so that’s most likely the reason.
So add something like this to the “[global]” section of smb.conf:
netbios name = MYSERVER
(see my smb.conf for comparison)
Then restart smbd with “sudo systemctl start smb.service”, and try to connect again.
I’m using a Linux Mint (KDE 16) in a virtual machine as well as OpenSUSE 13.1 to make the samba configurations.
Both machines are configured in a NAT and are running on the same host using VMWare. The Linux Mint (KDE 16) runs samba smoothly and without problem.
**Configuration of Linux Mint (KDE 16) (/etc/samba/smb.conf) **
[global]
server string = %h server (Samba, Linux Mint)
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n
*Retype\snew\s*\spassword:* %n
*password\supdated\ssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
panic action = /usr/share/samba/panic-action %d
idmap config * : backend = tdb
[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
printable = Yes
print ok = Yes
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
**Setup OpenSUSE 13.1 (/etc/samba/smb.conf) **
[global]
map to guest = Bad User
printcap name = cups
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path = \\%L\profiles\.msprofile
logon drive = P:
logon home = \\%L\%U\.9xprofile
domain logons = Yes
os level = 65
preferred master = Yes
domain master = Yes
idmap config * : backend = tdb
cups options = raw
[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = No
[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes
[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
create mask = 0600
printable = Yes
print ok = Yes
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
[share]
comment = share
path = /home/brlight/share
read only = No
inherit acls = Yes
Yet I notice that when disconect the host network OpenSUSE’s samba back to work. In my view, this should be no problem since being OpenSUSE on a NAT it communicates “directly” with the host not being seen by the host network.
I imagine that this problem has something to do with the way the samba of each of these distributions communicates through the network. Maybe OpenSUSE is trying to using some “Windows” network resource instead of working stand alone like Mint.
Maybe it’s something related to the "Domain Controller " , " WINS " or " NetBIOS " settings.
Anyway, I never saw a samba generate so much trouble! I’m a bit tired! =/