Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I'm just trying to set up a simple file server on my OpenIndiana box, but no matter what tutorial or smb.conf setting I seem to try I get the same problem.
First, my latest smb.conf:
Code:
[global]
netbios name = CASPER
workgroup = LAN
server string = File Server
log file = /var/samba/log/smbd.log
max log size = 100
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
security = share
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
[media]
comment = Media Files
path = /share/media
public = yes
read only = no
[sam]
comment = Sams Files
path = /share/userfiles/sam
valid users = sam
public = no
writable = yes
printable = no
I also made sure to add both the unix user and smb user to the server. I have the same user name "sam" on my windows desktop, and ubuntu laptop, and I used the same password. Ive tested the accounts and they seem to work fine. I can login to the unix account and samba shows that it has a user named sam
The problem:
The server and shares show up just fine, and the media share is readable (not writable but that most likely just a permission thing and not the issue at hand). The problem is with the private share "sam", heres what happens:
Local Test:
[QUOTE]sam@casper:~$ /usr/bin/smbclient //192.168.0.1/sam
Enter sam's password:
Connection to 192.168.0.1 failed (Error NT_STATUS_CONNECTION_REFUSED)[/CODE]
From my Ubuntu laptop:
Quote:
sam@osaka:~$ smbclient //192.168.1.13/sam
Enter sam's password:
session setup failed: NT_STATUS_LOGON-FAILURE
And from my Windows Vista desktop I just get a login unsuccessful message.
From my tests it seems that samba refuses to use any sort of user other then the guest account.
I tried it with "security = user" but run into the same issue, just when I connect to the server instead of the share, so it efectivlly blocks me from the media share as well.
Im probably missing something simple thats preventing the authentication, anyone care to point it out?
Ok, this is weird. This is only one of three forums I posted this to and I have yet to get a reply from anyone. Does no one use Samba? should I be looking at something else?
I know this is possible since thats the whole point of samba authentication, and Ive followed the examples to the letter. What the hell is going on with this thing?
weird, I could have sworn I ran this before but I don't recall getting this error before:
Code:
sam@casper:~$ /usr/bin/smbpasswd
Old SMB password:
New SMB password:
Retype new SMB password:
SAMR connection to machine NT_STATUS_ACCESS_DENIED failed. Error was 127.0.0.1, but LANMAN password changed are disabled
Ok, ran as root:
Code:
# smbpasswd -a sam
New SMB password:
Retype new SMB password:
no errors came up but I still cant access the share, sames issues as before
Yes and yes, same password, and the workgroup is LAN
However...
Code:
# testparm smb.conf
Load smb config files from smb.conf
rlimit_max: rlimit_max (256) below minimum Windows limit (16384)
params.c:OpenConfFile() - Unable to open configuration file "smb.conf":
No such file or directory
Error loading services.
I realize this is an old thread, but it showed up high in search results and seems to lack a conclusion.
I had similar problems, but setting the system date on the serving CentOS box to today's date (from 2004!) may have been the solution for me, and the reason why clients weren't being happily connected.
I know this is an old thread but I just came accross it while trying to solve the same problem. So for the benefit of others that might happen accross it.
The answer:
Problem is caused by SELinux, it can be turned off temporarily with 'setenforce 0', if that works turn it back on with 'setenforce 1' and correct the problem properly by setting the context of the Samba share directory to samba_share_t.
I know this is an old thread, but it continues to rank highly in search results for this issue.
I had the same problem - when Samba security was set to 'share' on my Linux box, authentication failed when attempting to access a password protected share from Windows 7, even though username and password were both entered correctly.
A partial clue came from a Microsoft support article named 'Cannot Connect to Password-Protected Share on Windows 95/98 Computer', since Win95/98 also use 'share level' security.
Basically, to access the password-protected Samba share in Windows 7, when the 'Enter Network Password' box pops up, instead of just entering the Linux user account name you need to enter name of Linux box\Linux user account name.
So if the Linux box is named 'dragon', the user account is named 'bob' and the password is 'penguin' you would enter:
Username: dragon\bob
Password: penguin
have you checked the actual directory permissions on samba server...?
does user sam have read/write access to directories ?
what are directory permissions please elaborate ..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.