Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 am running Fedora Core 5 on my Linux box and want to use it as a file server to house the my documents folders from my Windows PCs. I have shares created and can see them in network neighborhood on the Windows computers, but it says it is not accessible, I may not have permission, and the network path was not found. It doesn't even prompt me for a username and password. I did use smbpasswd -a to create usernames and passwords. I have been using SWAT to modify the smb.conf file. Also, my public shares will not allow me write access from the Windows PCs. Sigh... thanks in advance for the help. Here is my smb.conf file:
[global]
netbios name = NO-NO
server string = Linux file server
guest account =
unix password sync = Yes
log file = /usr/local/samba/var/%m.log
max log size = 50
load printers = No
dns proxy = No
ldap ssl = no
admin users = neddis
hosts allow = 192.168.0.0/255.255.255.0
[homes]
comment = Home Directories
path = /home/%u
read only = No
max connections = 10
browseable = No
[music]
comment = Music
path = /public/music
write list = neddis
read only = No
[download]
comment = Downloaded Files
path = /public/download
write list = neddis
read only = No
[temp]
comment = Temporary files
path = /public/temp
read only = No
Ok, now I swear I didn't change ANYTHING at all and when I do 'service smb status' I get 'smbd dead but pid file exists' and 'nmbd (pid 3333) is running'. What happened? I did some searching online found that other people have deleted smbd.pid and that fixed it. I have deleted the smbd.pid file several times and that does not help. Smb is also supposed to be generating a log file, but it's not in the location I specified in smb.conf. I am ready to beat this thing with a big stick. Thanks.
I just happened to look on the monitor of the linux box I am trying to work with (I have been using SSH to do all of this remotely). I think samba is dumping log info to the screen instead of a file. It says something like this:
First, run the "testparm" program whenever you edit the "smb.conf" file. It will check it for correctness.
The log message that you see looks like an SELinux message. If you are using SEL then check that samba is allowed to read it's own configuration files and write to the log file.
After running "service smb status" and getting the message that it was dead, did you run "service smbd start".
you can temporarily set SELinux to permissive with
setenforce 0
From gnome in FC5 you can disable SELinux for Samba through security settings (sorry, in Windows at the moment), but don't know how to do it from the terminal.
See if it works after the temporary disable and let us know what happens
Last edited by billymayday; 07-19-2006 at 01:33 AM.
It didn't work - the same thing happened. It put the 'audit: (numbers here) avc: denied' error on the host computer and won't start smbd. I even modified the SELinux config to disabled (and rebooted) and the same thing happens. I am totally stumped. On another thread I found out a possibility of why I couldn't aceess my home directories, but I can't test it because I can't get smb to start! This all started when I used yum to update my whole FC5 installation.
Since you are using swat, see if you can install the samba-docs package. It includes a large number of man pages, and either pdf or post script versions of three Samba Books including Bruce Perens' Samba 3 by Example. One of the example configurations could serve as a template. Using "security = server" is not recommended. Also, if some of the computers on the network are XP Home Edition, then you can't use "security = domain" as they are unable to join domains. ( Microsoft crippled networking in the Home edition to force companies to purchase the more expensive Professional Edition).
I do have that docs package and have been referring to it. testparm says the smb.conf file is ok. I just can't get samba to start now. I think it's an SELinux problem. I will start another thread for that though - http://www.linuxquestions.org/questi...d.php?t=465422
I haven't tried the unix password sync option, but looking at the example config that comes with samba, you need more around this option than you seem to have. Here is what the sample says.
Quote:
# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; 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*
Well, thanks a bunch for all the help. It was SELinux causing me to not be able to access my folders. I will take a look at that linux home networking site though, that looks like something I definitely need to read. As for getting rid of the audit error, I have no idea what I did to fix it. It didn't go away when I disabled SELinux, but something I did after that made samba able to load again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.