sorry, laptop died... let's try this again.
1) [./ntsysv] I use this to make sure that the smb process is set to start
when I boot the server.
2) [reboot] I know that there is some HUP kill restart type thing that
could kickstart the processes without rebooting, but I alway forget what it
is, so I just reboot.
3) [edit the /samba/smb.conf file to allow share level security] There is a
way to do this through a web interface called SWAT, but I haven't figured
out what RedHat did with swat in this latest version.
There is a smb.conf faq somewhere at www.samba.org, which you will
want to look over.
make sure that you create the shares there are some examples in
smb.conf...just make a share called [sharename] and set the path to the
desired directory.
4) [adduser] make sure that you have a unix user assigned to have access to
the server on the net. I do this, because I have user level and domain
security running. It's not a bad idea to have users setup for future work
that you might do.
5) [smbadduser] this will create a smb user id and password entry. again,
this is not needed for share level security, but it's still a good idea to
have the accounts ready for logging and the like.
6) [samba restart] this should restart smbd and nmbd. if it doesn't the do
a ./smbd restart and an ./nmbd restart.
7) At this point you should be able to see the server from the client.
Ping samba.server
from the client (win 95/98) go to search (for computers) then type
in the ip address of the server and hit go.
This should bring up the server with shares. If so, you are almost
there.
Open and share and copy/delete/mkdir etc...if any of this fails,
check the permissions on the directory and files on the server.
issues:
a) encrypted passwords. win98/NT/2000/XP use encrypted passwords, so that
has to be selected in smb.conf.
b) make sure that the workgroup in smb.conf is the same as the client
(usually workgroup).
c) I tend to put host entries in the Samba hosts and client hosts file to
make browsing more enjoyable.
d) work on the smb.conf file to make sure that everything is dialed in for
your needs.
e) Take some time and think about security. I don't like share level, I
have a firewall on the samba server and I have every user create a home
directory for their own stuff.
f) Buy some Pizza for the samba team...I'm not sure why you're supposed to
do this, but I'm always seeing notes from them requesting pizza...I guess
it's good Karma.
Hope this helps.
If not, there are tons of good reference works that go through step-by-step
trouble shooting of Samba at the samba site and in reference books.
carl
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 10:26 AM
To: [EMAIL PROTECTED]
Subject: RE: samba and windows shares
I installed RH 7.3 last weekend and Samba was working great! I'm not sure
what you went through to set up the service, but for me it was as easy as
this:
1) ./ntsysv (check to make sure thja
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 13, 2002 10:02 AM
To: [EMAIL PROTECTED]
Subject: samba and windows shares
Hi guys
has anyone got samba 2.2.4 and swat to work with windows.
simply I'm trying to get windows to see the linux share folder. linux can
see windows share and write to it.
any tips much appreciated
redhat 7.3. 2.4.18.4
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
