Linux Samba Server -- HELLLLLLLLPPPPPPPP!!!!!!!!

You are going about it the hard way :-)

Included with the RedHat distribution there are several smaba-related packages. The ones you will want to install are:

samba
samba-server
samba-client

This will give you everything you need to turn your linux box into a smb/cifs file server.

If you want to set it up to use the w2k server you mentioned you need to provide some more info. (what domain-type, do you want useraccounts from the domain server)

On the other hand if all you want to do is to use a share from the domain server, just use:
mount -t smb //server/share /mnt/here

You might need to pass along options, like usernames and passwords:

mount -t smb -o username=dinges,password=intheclear ...

There are loads more options, but figuring those out I leave up to you:

man smbmount

Here is some more info....  I am relatively new to the Linux OS.  I am very aware of the exciting capabilities that Linux has to offer, including the samba services.  The small network I am attempting to create includes Windows 2000 Adv server as a domain controller, with Win2k Pro, Win 98, and Win NT as clients.  My goal is to have the clients authenticated to the nework through the 2000 server.  All I want the Linux samba server to do is be a file server to the 2000 server clients. Now this may sound stupid, and extremely noob of me, but the #mount command says to me Linux.  The 'mount -t smb -o.......' that you mentioned; is this command to be used on the Linux machine or the Windows server clients?  Another noob commentn....In the fourtyseven times I have installed Linux this past week, I don't recall seeing the individual packages that I need to install.  I have seen some packages that have the word Samba in them, but during the install, I haven't actually seen the individual packages, samba, samba-server, or samba-client.  Are these packages all grouped into one, or are they individual packages that I need to install seperately.  I am simply looking for a brief step-by-step, i.e.  install Linux, be sure to install these packages, create an account that matches one of your windows 2000 client accounts, use this command, on Linux, to mount the share, use this command, on windows, to access the share, blah, blah, blah.  Thanks for your help.  Seriously...thank you.

I think that this might just do it for me.  I will give this a try when I get home tonight.  Thank you so much for your help.  I will let you know how it goes.  Thanks again.

Alright, everything is going great with the setup.  I followed your directions.  All Samba services are installed, the services are starting up and all that.  I made the changes to the /etc/samba/smb.conf file, and ran testparm -x.  Everything is good with the file except I get a message that says, "winbind separator = + might create some problems."  Secondly, I can't seem to connect to my Window 2000 Domain Controller, with the samba machine.  Here is the network config for both machines, (Win2k & Samba machines).

WIN2k - FQDN = dc1.techfair.com
            Netbios name = TECHFAIR
            IP address = 192.168.0.201
            SNM = 255.255.255.0
            Default Gateway = 192.168.0.1
            DNS = 192.168.0.201

Samba - Name = SambaSrvr
            IP address = 192.168.0.202
            SNM = 255.255.255.0
            Default Gateway = 192.168.0.1

I can ping the Win2k machine from the Samba machine and visa versa.  I think somewhere my name resolution is failing.  Am I forgetting to set something up on either machine?

Progress....I'm making progress.

Thanks

Also, I cannot see the Samba server in 'Network Neighborhood'.

When I say that I am having problems connecting I mean that the,
#smbpasswd -j techfair.com, is failing to find the DC for the specified domain.

Well, the step you are having problems with is sort of essential :-(

First: the config and setup that I show here are for classic domains!! So not for AD-domains!! Integrating samba/linux into AD is not a trivial task.

In case you are using classic domains:

If you think you have some sort of name resolution problem try the following:

nmblookup -M -- -
the output of this command should tell you whether there is a so called masterbrowser on your local subnet. (you need one and it should be there)

nmblookup TECHFAIR
the output for this command should be a list of all the netbios names that techfair is responsible for: it's own name and the domain name