[SOLVED] Apparently I need lots of help creating a Samba server (Slackware64 13.37)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Apparently I need lots of help creating a Samba server (Slackware64 13.37)
So I've spent the last week trying to get a computer configured to operate as a server for my small home network of Windows 7 computers, and to be honest, it's been extremely frustrating. It took me ~5 days (starting June 30) just to get the Slackware computer to boot and since then I've been trying to get Samba working, to no avail. Yesterday I rage-quit and wiped everything I've done to the computer and decided that I really didn't need a home server...
But that itch still requires some scratching apparently...
So once I begin again, I should be able to get the OS operational within a few hours since I've learned from the constant mistakes and little system-specific things that prevented me from getting a properly running OS originally. However, I'm still at a loss as for trying to get Samba working the way I'd like. I went through tons of tutorials (including a bunch of threads from LQ and AlienBOB's Samba wiki entry, amoung others that were OS agnostic) and was met with failure every single time. Since I nuked the system yesterday, I'll have a fresh Slackware install to work on.
Here is what I would like to accomplish:
1) The share itself will directory to which a hard drive dedicated to storage will be mounted to (which shouldn't be overly hard, but I think I may need help in getting file permissions correct)
2) The Samba share should be read/write for any Windows 7 PC that happens to connect to my LAN, complete with no authentication windows or configuration of Windows 7 computers needed. Access from the Windows 7 computers should be as easy as point and click.
I went through AlienBOB's stuff once already, I guess I could give it another shot. You mention that you added the first small section of your post to bottom of the smb.conf file; did you leave the rest of it as it is in default?
I went through AlienBOB's stuff once already, I guess I could give it another shot. You mention that you added the first small section of your post to bottom of the smb.conf file; did you leave the rest of it as it is in default?
Yes I did.
AlienBOB's stuff was the only one that was ever useful to me. I couldn't understand most of the others.
edit / note:
You can run the commands off one at a time and it will do the same thing.
I use the scrip because Its just faster for me during one of my "high speed bork, hose & reloads".
Correct me if I'm wrong but if you want the Samba share to be discovered properly you need to start ntpd on the same box that Samba is running?
To start it
Correct me if I'm wrong but if you want the Samba share to be discovered properly you need to start ntpd on the same box that Samba is running?
To start it
Code:
/etc/rc.d/rc.ntpd start
To start it every boot
Code:
chmod +x /etc/rc.d/rc.ntpd
Hmmmmm.... I'm no one to be correcting anybody about computers but:
I have 6 boxes and 2 laptops that I setup with the above script and all can find each other.
However, I'll add:
/etc/rc.d/rc.ntpd start
chmod +x /etc/rc.d/rc.ntpd
to my little script if that will make it better.
Thanks!
Hmmmmm.... I'm no one to be correcting anybody about computers but:
I have 6 boxes and 2 laptops that I setup with the above script and all can find each other.
However, I'll add:
/etc/rc.d/rc.ntpd start
chmod +x /etc/rc.d/rc.ntpd
to my little script if that will make it better.
Thanks!
You might want to wait for a confirm/deny from somebody with a little more clout. I just have this memory of bashing my head against smb.conf and then starting ntpd and everything suddenly working.
You might want to wait for a confirm/deny from somebody with a little more clout. I just have this memory of bashing my head against smb.conf and then starting ntpd and everything suddenly working.
Yeah, I did my share of head bangin till I found AlienBOB's page.
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 386
Rep:
Quote:
Originally Posted by spudgunner
So I've spent the last week trying to get a computer configured to operate as a server for my small home network of Windows 7 computers, and to be honest, it's been extremely frustrating. It took me ~5 days (starting June 30) just to get the Slackware computer to boot and since then I've been trying to get Samba working, to no avail. Yesterday I rage-quit and wiped everything I've done to the computer and decided that I really didn't need a home server...
@Spudgunner,
Do you still need help with this? I love using Slackware64 13.37 as a Samba server for windows clients because it takes less than 5 minutes to setup and its stable as an ox.
Let me know if you're still having trouble and I'd be glad to help you out.
@ spudgunner
As I recall, when I first starting using samba one major boo boo I did was having the same host name on some of my boxes and of course they couldn't find each other till I gave them all different host names.
All of my boxes are on the same domain name tho.
Here is what I would like to accomplish:
1) The share itself will directory to which a hard drive dedicated to storage will be mounted to (which shouldn't be overly hard, but I think I may need help in getting file permissions correct)
2) The Samba share should be read/write for any Windows 7 PC that happens to connect to my LAN, complete with no authentication windows or configuration of Windows 7 computers needed. Access from the Windows 7 computers should be as easy as point and click.
that's pretty easy: let's assume you want your shared directory to be /home/samba
then go in /etc/samba, move away your smb.conf file (backup it somewhere), create a pristine one copying it from smb.conf-sample and edit it.
change the line
Code:
security = user
to
Code:
security = share
then, you will find in the same file this section
Code:
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
uncomment it (copy it before, as you like), rename the share and make it point at your folder
Code:
[myshare]
comment = My shared folder
path = /home/samba
read only = no
public = yes
you can also add a line
Code:
browseable = yes
if you want the share to be browseable through the network.
then
Code:
/etc/rc.d/rc.samba restart
and you're done
for more informations and details, as written on top of smb.conf-sample, see the Samba-HOWTO-Collection pdf or the Samba Guide (with many practical examples).
ntpd should be needed only if you want windows machines to join your samba domain and you use the samba machine as a domain controller with profile folders and stuff.
Thanks for all the awesome replies, it looks like I know what I'll be doing when I get home from work tonight!
@slackass: Please don't be offended, but I'll be giving your method a try after I try what ponce posted, only for the fact that his is much less complex. Whether or not I get his working, I'll be trying yours next because your (AlienBOB's) method allows for the creation of user-specific shares down the road, and I'd like to keep that option open. I am going to be leaving out all of the printer-related stuff though. None of my machines have the same host name and there no domain/domain controller to speak of (though I could make one, but I'd rather use dd-wrt that's on my router than the server box). I'm assuming that you use your Samba setup with Windows 7 computers on the network and it's all good (although since security=user still, I imagine you would have dialog boxes popping up on the Windows machines)? One more question, don't the lines
go in smb.conf and not in your script (did you make a mistake as to where you put ##end in your comment)? Thanks.
@thund3rstruck: Thanks for the offer of help, I'll give the methods that have already been posted a shot and if none of them work then I'll come-a-knockin'.
@vdemuth: Webmin looks like an awesome tool. If you or anyone else has used it, how has it been?
@ponce: I was so close to your solution! The only thing I immediately see that I missed was changing the ownership of the share folder and I used the [public] template rather than the [tmp] template. Just to be safe, once I make that directory, would I chown before I mount my storage device to it or after? Thanks.
Just to be safe, once I make that directory, would I chown before I mount my storage device to it or after? Thanks.
after, and if it already contains files/folder add a -R to the chown.
if your storage device is fat/vfat/ntfs formatted and you can't change the ownership (but you should also on those filesystem using mount options), you have to mount it with 777 permissions (ntfs-3g already does it).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.