Eating some Samba humble pie

[steelaworkn]

So, I can see the Windows machines from my Fedora 16 box with no problem. I can also copy files from them. They just can't see mine.

My /etc/samba/smb.conf file is really messing me up. I can't seem to get it. I've looked at the manual and various sites. I am beginning to understand the basics of it all, but still get get it tweaked to where it is working. All are W7 boxes except mine. Here is my current config file:

[global]

workgroup = Fitzhome
netbios name = dadsfedora
server string = Samba Server %v
guests ok = yes
guest only = yes
security = share
browseable = yes

[Public]

path = /home/jeff/public
security = domain
guests ok = yes
guests only = yes
read only = no
browseable = yes

So basically, I just need a basic home Samba set up to where the can see my files in /home/jeff/Public. Any suggestions?

[glennzo]

I seem to remember reading that sharing /home is a PITA. Hope I'm wrong,

Not to come off sounding like a wise guy but have you looked at the log files, especially /var/log/samba/samba.log. Also /var/log/audit/audit.log might hold some clues. SeLinux issue possibly?

[RHamel]

I think you have to

[global]
wins support = Yes

[steelaworkn]

Originally Posted by glennzo

I seem to remember reading that sharing /home is a PITA. Hope I'm wrong,

Not to come off sounding like a wise guy but have you looked at the log files, especially /var/log/samba/samba.log. Also /var/log/audit/audit.log might hold some clues. SeLinux issue possibly?

I just now saw the Selinux alert. Bummer. I was able to do it on F13. I'll take a look and the log and see.

[leigh123linux]

I don't eat ****

yum erase samba\*

Then use nfs

http://support.microsoft.com/kb/324089

[steelaworkn]

Just looked for the logs you mentioned and they do not exist...bummer and adding "wins support = yes" does not work. Windows still cannot see my Fedora box.

Can't be that complicated. Just can't figure it out yet. Any other suggestions?

---------- Post added at 01:34 AM ---------- Previous post was at 01:34 AM ----------

Thanks Leigh, I posted seconds after you. I'll give that a shot.

[leigh123linux]

Any use?

http://danwalsh.livejournal.com/14195.html

[steelaworkn]

samba is in all things on my box. To erase it means to erase everything that is everything. Looks like the very substance that holds all things together. Can't be erased without causing mucho damage.

[glennzo]

What I've done with my home server is to set up Samba so that Windows boxes can access shared folders on the Fedora 14 server. Here's my smb.conf:

#======================= Global Settings =====================================
[global]

# ----------------------- Network-Related Options -------------------------
#
workgroup = JOHNSON
server string = Samba Server Version %v
netbios name = ZEPPELIN

# --------------------------- Logging Options -----------------------------
#
log file = /var/log/samba/log.%m
max log size = 50

# ----------------------- Standalone Server Options ------------------------
#
security = share

#============================ Share Definitions ==============================
[quicken]
comment = Quicken backups
path = /mnt/disk3/qback
browseable = yes
writable = yes
public = yes
guest ok = yes

[photos]
comment = Family photo folder
path = /mnt/disk3/photos
browseable = yes
writeable = yes
public = yes
guest ok = yes

[backup]
comment = Backup folder
path = /mnt/disk3/backup
browseable = yes
writeable = yes
public = yes
guest ok = yes

Allow both "sambas" in the firewall configuration. This works for me.


For Linux to Linux I'm working on NFS and some simple mounts.

[steelaworkn]

That might work for me, Glen. Thanks. I just crashed my system and am in the process of restoring it. Learning some lessons. Trashed the kdebase and everything with it. Still have my files. Just trying to get the login screen back.

[bbfuller]

You may also be running into problems with SELinux.

There's a gui for that which will show you the samba options that are blocked, with the ability to change them.

On KDE installs from a live CD at least, it's not installed by default:

yum install policycoreutils-gui

It's the "boolean" tab which is interesting in this case.

[Anniedog]

On my network I have always had to set a machine as a samba server not samba client in order for other computers to see and access any shares. So it is wins support yes as in previous post. I historically, and for reasons I can now no longer remember, edit /etc/nsswitch.conf to include in the hosts allow line "wins".

SElinux I always have to change, various options there for file sharing permissions etc
Firewall I always have to set this for both samba server and samba client with additionally the setting for a shared printer if attached.

Currently just catching up on things with F16, after missing the last release but the above seems to be working for me ok on the couple of F16's I am playing with. (Really not comfortable with GNOME 3, seems a real performance hit to me so far and been having all sorts of stability problems though samba has luckily not been one of them yet though I running with share permissions only at the moment).

[steelaworkn]

I'm back. I did "yum erase samba" and it is truly the glue that holds KDE together. After busting my brains over it, the solution was "yum group install KDE". And I'm back up and running. I'm not sure really what to do. Wondering if Gnome does a better job of networking than KDE.

[beaker_]

Wondering if Gnome does a better job of networking than KDE.

You lost me there. I think you're saying, 'samba's worked out.' If not, then either system-config-samba works good enough. kde's module also works but makes a couple old assumptions. Anyway, if you're referring to browsing, then it doesn't work because dolphin uses wins for name resolution. Which fedora doesn't use by default.

[steelaworkn]

Originally Posted by beaker_

You lost me there. I think you're saying, 'samba's worked out.' If not, then either system-config-samba works good enough. kde's module also works but makes a couple old assumptions. Anyway, if you're referring to browsing, then it doesn't work because dolphin uses wins for name resolution. Which fedora doesn't use by default.

Samba sees the other computers on my network and I can access those files, but when it comes to sharing my Fedora files on the network, Samba does not work. It could be in the Selinux policy, I'm not sure.

Yes, I am referring to browsing from the perspective of the Window's machines. They cannot browse my Fedora shared files which are located at /home/jeff/Public. They can see that they are available, but when the click on "Public" they get a permission message and they are blocked from the "Public" folder. So, could be Selinux. I'll have to look at that one.