I'll try to make it as short as possible. I installed Fedora 15 5 days ago after using debian-based distros for a few years, and until now I've had the habit of sharing many files (mostly multimedia) on my home network, except since I'm the only one using Linux, I have to do it using Samba.
In Ubuntu, Xubuntu and Linux Mint, this worked like a charm.
Two things have changed this week: I switched to Fedora 15 like I said before, and I bought a new USB external HDD. I previously used a 500 GB Western Digital, and changed for a 1.5 TB SAMSUNG which is linked to my station via USB. The drive works well and I cp'd the 450 gigs of the ancient drive within the new one without a problem.
Ever since I managed to set up fedora and GNOME 3 as I would like it, I've been trying to setup the network sharing via Samba, and that's a genuine 4-day long headache now.
Thing is, yesterday, it worked. After setting everything right, creating an automount of the external HDD in a maybe-too-much permissive folder, allowing Samba through the firewall, getting to know that buddy called SELinux I had never met before and which I struggled to tame ; after setting everything up, it worked seamlessly, I streamed music from the Windows PCs of my network and began watching a film.
Except I had a problem which had nothing to do with Linux: letting the USB drive plugged in on startup prevented the BIOS phase from going well, and my station was stuck on my motherboard splashscreen. To fix this, I had to disable the USB Legacy in my BIOS. Did the trick. Yesterday night, I rebooted like that, and everything was fine.
This morning, Fedora wouldn't boot. Since the new BIOS parameters didn't switch the drive on on startup, fstab was trying to mount a drive which wasn't there, and thus crashed, switching to emergency mode.
Had to remove the ftsab line concerning the USB drive for Fedora to boot again.
Alrite, that's fixed, I thought ; I just changed the fstab options adding noauto,user, etc. and I thought it would be ok, but it ain't.
It's now been 3 hours without me finding any clue as to how to get this working.
IMO, the problem comes from the fact that Samba is missing the right to access the drive. Samba seems to be OK: from the Windows station I can see my Linux station on the network map, I can access it entering the Smbuser I created for this, and the "ext-hdd" dir is present (that's the alias I used in the Samba config files), but when I try to access it, Windows says it can't access it.
I'll try to add as many pieces of information as possible that might be useful:
[norfen@norfens-station ~]$ getsebool -a | grep samba
samba_create_home_dirs --> on
samba_domain_controller --> on
samba_enable_home_dirs --> off
samba_export_all_ro --> on
samba_export_all_rw --> on
samba_run_unconfined --> on
samba_share_fusefs --> on
samba_share_nfs --> on
use_samba_home_dirs --> off
virt_use_samba --> on
[norfen@norfens-station media]$ ls -al
drwx------. 1 norfen norfen 4096 Aug 6 17:23 SAMSUNG
Samba and Samba-client are ticked as Trusted Services in the Firewall.
My simplified /etc/samba/smb.conf:
workgroup = WORKGROUP
server string = Samba Server Version %v
security = user
comment = External HDD on Norfen's Station.
path = /media/SAMSUNG
read only = no
browseable = yes
valid users = sarafinah
(Note: sarafinah is the user supposed to access the files on the network, she exists both as a Fedora user and a Samba user).
Thanks in advance to whoever will try and help me, and I hope a similar post doesn't already exist but I doubt it since I've been looking for answers for 4 days.