Linux Server - Samba Installation

[Fuzzygoth]

I am currently in work trying to setup a Linux Server to use samba
to create mappable shares on our network. Of course other than a
bit of Shell Scripting, MySql commands and basic system commands
I've never really been a Linux User per-say. We are using Fedora
and I am trying to determine if samba is already installed, using
the command rpm -qa | grep samba I get the following:

samba-client-3.4.7-58.fc12.i686
samba-domainjoin-gui-3.4.7-58.fc12.i686
samba-winbind-clients-3.4.7-58.fc12.i686
samba-common-3.4.7-58.fc12.i686
samba-doc-3.4.7-58.fc12.i686

I was expecting according to the book to see:

samba-3.4.7

I am assuming that because I'm using a diffrent version of linux
(Fedora 12) than the one in the book that the way the rpm query
might returns the results in a diffrent format.

So even though the rpm query can find these components, I am not
sure that samba is installed properly as when i do smbstatus I get
the following message.

-bash: smbstatus: command not found

So, doe's this mean I have to (re)Install samba? so I can configure
it, if so what are all those modules doing there *confused*.

Fuzzy

[scathefire]

rpm -q samba

if you get no results then its not installed

yum install samba

will install it, or tell you if it is all ready installed

[Mudgen]

You might also find samba-swat useful for configuring after installing the actual samba package (which you clearly don't already have installed, given your original post).

On my working home samba server running Fedora 12, I have (from "yum list installed samba*):

samba.i686 3.4.7-58.fc12 @updates
samba-client.i686 3.4.7-58.fc12 @updates
samba-common.i686 3.4.7-58.fc12 @updates
samba-swat.i686 3.4.7-58.fc12 @updates
samba-winbind.i686 3.4.7-58.fc12 @updates
samba-winbind-clients.i686 3.4.7-58.fc12 @updates

[matt2kjones]

The reason you see all the existing packages installed is because that machine only has the client tools side of samba.... which would allow it to join an existing windows domain or map shares off other windows machines or samba servers.

Like stated above, you need the actual samba package to be able to share folder from linux to other linux or windows machines

[Mudgen]

Generally you do want the client tools installed on the server, for testing and troubleshooting. If you can successfully perform client tests on the server but not from another machine, that tends to isolate the problem to network/firewall issues.