Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hello all!, maybe we all can learn from this thread as I will write all the steps I have taken so far in order to set up Samba here at work for File server purposes. This is the first time I touch Samba, sorry for any misunderstandings.
I'm testing this in a computer lab with a workgroup called: Lab
This is what happens when I add smbclient:
By using the command: smbclient -U rguisbert -L SAMBA
Domain=[LAB] OS=[Unix] Server=[Samba 3.0.22]
Sharename Type Comment
--------- ---- -------
music Disk
everyone Disk
apps Disk
IPC$ IPC IPC Service (Samba 3.0.22)
ADMIN$ IPC IPC Service (Samba 3.0.22)
Domain=[LAB] OS=[Unix] Server=[Samba 3.0.22]
Server Comment
--------- -------
LAB4 Computer Lab
SAMBA Samba 3.0.22
Workgroup Master
--------- -------
LAB LAB4
When I try to access the folder apps from my WinXP machine I get a prompt:
user: \\Samba\gwguest
password:
There is no username gwguest in my WinXP machine or in the Linux box! I tried many password and nothing
When I try to access the folders everyone and music from my WinXP machine I get:
\\Samba\music is not accessible. You might not have permission to use this network resource. Contact the network administrator of this server to find out if you have access permissions.
Same case for the everyone folder.
I did:
1. Restart Samba
2. sudo useradd rguisbert
3. sudo smbpasswd -a rguisbert
And repeated this for all users. What is the problem?? We want to make a swicth to Linux but it seems very confusing!!
This might not be exactly what you want, but the following smb.conf with Samba 3.0.20a on FC3 with a 2.6.14.3 kernel allows all windows machines on my LAN to access my Linux machine's defined share without having the windows users having to type passwords or anything:
I have a similar problem, and I tried the solution you suggested but I still Samba won't allow access to folders.
When I try to access to my shared folders from a Win98 or a WinXP or a Windows Vista, I get an error message that says that I have no permission, or that the folder can't be accessed.
I copy my smb.conf here. Maybe you can give me a hint?
-----------------------
[global]
workgroup = LOSMONTE
netbios name = PABLO
server string = Compu de pablo
log file = /var/log/samba.log
max log size = 500
log level = 2
hosts allow = 192.168.1.2 127.0.0.1 192.168.1.3 192.168.1.4 192.168.1.5 192.168.1.6
security = share
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384
local master = yes
os level = 99
preferred master = yes
domain logons = no
wins support = yes
browseable = yes
lanman auth = yes
lm announce = yes
[Incoming]
comment = Musica de Pablo
case sensitive = no
guest ok = yes
;msdfs proxy = no
path = /home/pablo/Incoming
read only = yes
browseable = yes
public = yes
[ACER]
comment = Musica de Mariana
guest ok = yes
path = /home/pablo/Desktop/ACER
browseable = yes
writeable = yes
create mode = 0666
directory mode = 0777
public = yes
I have found in the past that alot of my access problems with Samba where not due to Samba's configuration, but because of how SELinux is configured out of the box in Fedora 6 if you are using Red Hat. If you are not using SELinux you should check what your distro is using. In any case, in Fedora, you can configure SELinux via the control panel to allow samba through. Once that configuration is in place, most Samba access problems go away.
Have you tried to configure security for USER instead of SHARE. Then use SWAT to add users to your SMB configuration (restart). You can also make all of this transparent between your Win boxes and your samba server if the usernames/password across both are the same.
Yep. I finally did it. Thanks for the tip, but I read your reply when I had already solved my problems. I had to create UNIX users, and smb users, and resolve their permissions, etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.