SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Rep:
smbhelp
Having some trouble getting samba to work. I've combed the man pages but can't find the key to unlocking whatever's holding me up here. From Windows, I can see the Linux host, but whenever I click on it a get a login box for <hostname>\Guest that I can't change, and no passwords work correctly. When I try smbclient from the Linux box just to test the shared area, I get "tree connect failed: NT_STATUS_WRONG_PASSWORD", no matter what p/w I use.
As far as I knw, I used most of the common smb options, and added a few I found while reading through this forum and other sites.
Just to clear up some of the verbage in the file: the valid users should be smbuser and root (for testing), the 'sambaland' share path is /usr/local/sambaland, and the host name is gandalf.
If you see any flaws in the file below, please let me know?
Thanks!
=====
# /etc/samba/smb.conf
=====================================
[global]
dns proxy = no
security = share
workgroup = istari
server string = gandalf
guest account = guest
share modes = yes
local master = no
name resolve order = host bcast
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
socket options = TCP_NODELAY
netbios name = gandalf
log file = /var/log/samba.%m
load printers = yes
os level = 20
max log size = 50
default = sambaland
ssl ca certdir = /etc/ssl/certs
[homes]
comment = Home Directories
browseable = no
writable = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
[sambaland]
path = /usr/local/sambaland
valid users = smbuser,root,@smbusers,@root
comment = samba share on gandalf
writeable = yes
public = yes
[cdrom]
comment = CDROM
path = /mnt/cdrom
read only = no
browseable = yes
public = yes
======
You need to add the users to you Linux box. For example if user "user1" wants to get into a samba share, you have to add an account to the linux box, like you do normally, and then do:
smbpasswd -a user1
to add him to the samba.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Thanks Figa... this may be on the right track, because I got 'half an error" when adding a user: # smbpasswd -a smbuser
New SMB password:
Retype new SMB password:
unable to open passdb database.
Added user smbuser.
Regardless, the user was added and I can now list the samba shares from the Linux box. But I think I have another problem: Workgroup Master
--------- -------
ISTARI RADAGAST
MYGROUP GANDALF
For some reason, my Windows network (istari) doesn't seem to be meshing with my Linux box (which is also in the domain istari).
I also set the smbclient -W as 'istari' but that doesn't seem to have made a difference, and I'm still geting the same 'guest' login box each time I try to click on the Linux server name from Windows.
Here is a compy of my smb file. It is very simple, maybe you should simplify yours too. With this one, you have to enter a username and password all the time, but you should not have any problem accesing the shares that you specify here.
# Global parameters
[global]
netbios name = DA_SERVER
server string = DA_SERVER
security = user
encrypt passwords = Yes
update encrypted = Yes
smb passwd file = /etc/samba/smbpasswd
name resolve order = host bcast
local master = No
lock dir = /tmp/samba
guest account = guest
hosts allow = 192.168.50.
[figa]
comment = figa
path = /home/figa
read only = No
guest ok = Yes
Two things that are different between our smb.conf files is the security = user, yours is set up as share, and the update encrypted = Yes, which is missing from yours. This, I think, is gonna keep the smbpasswd updated in case you shange the local passwords.
Also, make sure you include the netbios name. Another thing is that I don't have any printers defined, but I think what you have should work.
Oh!! I have just notice also that you don't have the hosts allow = 192.168.50. line, where you could specified individual ip addresses or a whole range like me. For example if you are using ips from the 10.0.0.1/10.0.0.224 the you should specifiy it like this 10.0.0. . Probably this will make a big difference. With samba, just keep it simple at first, try to have the shares working at first, then go on with the printers.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Yes, thanks Figa! I made all the changes you suggested, and I'm not sure which was the key, but I would guess it was changing 'security' from 'share' to 'user', as I'm now allowed to type in a user name from Windows, instead of getting the greyed-out box reading '<host>/Guest'.
Cool deesto. Im glad I was able to help you. enjoy samba now.
Another thing, are you able to share and use the printer from samba to windows? Thats the one thing I haven't been able to figure out, also I haven't really tried that much. But if you do, let me know, maybe you can help me there.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
I have only done it the other way around: that is, printing in Linux to a printer attached to a Windows machine and shared on the same network. This isn't all that simple either, and I currently don't have it working, but I've done it before (3 or 4 times, actually) and once it's working, it's stable.
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
So it seems! But I'm getting weird errors when choosing a driver, no matter which submenu I go into... Enter number: 53
Error: Your gs version doesn't have driver "stp" compiled in...
Select another driver or build a new gs version with complete or customized driver support.
Another result: Enter number: 15
You selected driver: pips/sc880
Driver pips/sc880 supports the following printer(s):
Epson Stylus Color 880 {png+pips}|pips/sc880
ERROR: additional filter 'pips-sc880' was not found;
can't create test page
Any ideas?
Distribution: FreeBSD, Fedora, RHEL, Ubuntu; OS X, Win; have used Slackware, Mandrake, SuSE, Xandros
Posts: 448
Original Poster
Rep:
Yup; that's what gave me this error: Enter number: 53
Error: Your gs version doesn't have driver "stp" compiled in...
Select another driver or build a new gs version with complete or customized driver support.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.