FC4 and SAMBA

[bviper13]

my smb.conf is extremely basic, pretty much the default:
-------------------------------
#======================= Global Settings =====================================
[global]

workgroup = home
server string =
; hosts allow = 192.168.0. 192.168.1. 192.168.2. 127.
; printcap name = /etc/printcap
; load printers = yes
; printing = cups
cups options = raw
; guest account = pcguest
log file = /var/log/samba/%m.log
max log size = 50
; security = user
; password server = <NT-Server-Name>

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no

#============================ Share Definitions ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
username map = /etc/samba/smbusers
[homes]
comment = Home Directories
browseable = no
writeable = 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
; writeable = no
printable = yes

[bviper13]

In FC3 all I had to do was create a samba user with same name and password as an existing linux user on the system, which also matched the user/pass on the WinXP box. Simply log into the PC and the home directory of the user would be accessible. You don't even need a samba share for it. Since the user and password are the same, you only need to login to Windows.

[masterlodi]

mib4 - thankyou!

I executed

setsebool samba_enable_home_dirs=1

as root and all works perfectly!!!

[bviper13]

could you post your smb.conf masterlodi?

[masterlodi]

bviper13, I have posted my smb.conf at

http://forums.fedoraforum.org/showpost.php?p=281892&postcount=6

if that helps at all?!

[jamier]

Man...I had erased my installation of FC4 that I did an upgrade with because I figured something got goofed up in the upgrade, but all I typed was "setsebool samba_enable_home_dirs=1" and I was also able to get my SMB shares to work.

[jamier]

On a quick side note. That only allowed my smb share with a home directory as you can tell the command. I had to type "setsebool -P smbd_disable_trans 1" to allow smb to work with my other drives that are not in the home directory.

http://www.nsa.gov/selinux/list-archive/0501/10197.cfm

[Diziet Asahi]

There is a GUI to configure SELinux policy, it's in System Settings > Security Level > tab SELinux, unfold samba in the bottom panel.
To share home directories, click on "Allow Samba to share user dir".
To share another dir, i had to click as well Disable SELinux protection for smbd/nmbd deamons"

[hlslaughter]

i've got the same problem after upgrading to FC4 and trying to use my FC3 samba settings.

i finally started from scratch with a bare bones conf file.

i determined that samba actually does work, but only with shares located on my /dev/sda drive. if i try to share off my other '/dev/hd*' drives, i get something like:

[2005/06/24 10:08:51, 0] smbd/service.c:make_connection_snum(615)
'/extra2/' does not exist or is not a directory, when connecting to [baa]

i've tried all variations of permissions and etc...., the exact same everything will work on a share on /dev/sda* and **not** on /dev/hd* (either of my two ide drives)

it really smells like a samba bug to me. i've never seen behavior like this before. i'm not aware of any interloping apps such as selinux or a firewall that would care where a samba share was located physically.

[hlslaughter]

hey, it works now!!

my particular 'fix' was either random chance or:

- navigate to: system settings -> security
- click on selinux tab
- go to samba section
- check all options
- reboot

don't know why/how this works or if it's even the reason samba shares all work for me now. but it seems to have been the 'solution'.

hope that helps someone...

[gavinw6662]

mib4 - thankyou!

I executed

setsebool samba_enable_home_dirs=1

as root and all works perfectly!!!

Worked for me too, I just installed FC4 yesterday

[davidgurvich]

To fix the selinux problem '/sbin/fixfiles relabel' . This will reset permissions on various files controlled by selinux. This may take some time as all your files are relabeled.

[gavinw6662]

To fix the selinux problem '/sbin/fixfiles relabel' . This will reset permissions on various files controlled by selinux. This may take some time as all your files are relabeled.

Will that work even though SElinux defaults with home_dirs_enable to off?? I don't think fixfiles will solve that. You have to enable it correct??

[foolish]

Start system-config-securitylevel and simply oncheck the samba checkboxes in the SELinux configuration.

[timeforsmilin]

I am having the same headache with Samba and FC4. Now, the security won't even open, which I read last night is due to FC4 naming of ports. If it gives them an unrecognized name, the gui won't open. Would someone please tell me where to edit this file directly. I think that if I remove the ports that I opened, 137, 138, 139, 445, 601, 901, that at least the gui should open again. Right now, my XP machines are just plain denied access.

Thanks for any help!