Linux

for a newbie, I'm surprized you didn't just use the rpm to install samba. Check to see if a directory mamed /etc/samba was created.
this directory should contain a file named smb.conf . There should be a file called smbpasswd and smbusers where theaccounts authorized to access samba shares are entered. smb.conf will contain you workgroup or domain name, your netbios name, your shares, your security setting, etc. There are examples listed in the file. Consider using the rpm from RedHat to install this software.

The simplest way would be;
1. download rpm version and install
rpm -Uvh samba-xxx.rpm
2. go to /etc/samba/smb.conf and edit for your network and share folder. You may need to spend some time to read the conf file. It explains to you how touse/configure conf file.
3. start samba service
/etc/rc.d/init/smb start

Good Luck
Lint.

That was rpm, not rpc. Go to RedHat's ftp site or rpmfind.net and download samba-2.2.7-2.i386.rpm.
RPM's are a little more fool proof than making a tarball. Log in as root (or SU) and type rpm -Uvh samba-2.2.7-2.i386.rpm (if the file you downloadedhas a different name, use it here). Once it installs, edit the file /etc/samba/smb.conf
The really important things to change are the
workgroup =
Set this equal to your windows workgroup name.

There are lots of comments in smb.conf explainighow each line works.

Once you save your file, type
service smb start
on the command line to start SAMBA.

This will get the server part of samba running.

The client side doesn't need setup if you use smbclient.

You do have to setup KDEfor lan browsing.

If you have a Windows NT network of Win95-98 network things should run well.

If you have a Win2000 workgroup, don't make the linux box master browser unless it's a PDC too.

Samba 2.x does NOT support Active Directory.

Hope this helps.

Sounds like you are trying to make your samba authenticate with W2K AD. If this is the case you will need to use a package called WINBIND. If you installed Samba when you installed RH8, then WINBIND will be installed also.

Here is an edited example of my smb.conf which allows users to use my samba shares while authenticating to my AD servers.

# === Global Settings === #
[global]
workgroup = [domain name]
server string = [AD SERVER]
hosts allow = 127. 128.27.
log file = /var/log/samba/%m.log
max log size = 0
security = DOMAIN
password server = [AD SERVERS]
encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
unix password sync= Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
pam password change = yes
; include = /etc/samba/smb.conf.%m
obey pam restrictions = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
; interfaces = 192.168.12.2/24 192.168.13.2/24
; remote browse sync = 192.168.3.25 192.168.5.255
; remote announce = 192.168.1.255 192.168.2.44
local master = no
; os level = 33
domain master = no
; preferred master = yes
; domain logons = yes
; logon script = %m.bat
; logon script = %U.bat
; logon path = \\%L\Profiles\%U
; wins support = yes
; wins server = w.x.y.z
; wins proxy = yes
dns proxy = no
; preserve case = no
; short preserve case = no
; default case = lower
; case sensitive = no

#=== Winbind Variables ===#
winbind separator = +
winbind uid = 10000-20000
winbind gid = 10000-20000
winbind cache time = 30
winbind enum users = yes
winbind enum groups = yes