Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm presently being deluged with paper about Samba. everything about Samba. Too much about samba! I need a real-life grep tool!
All my documentation is about samba server though. is that what I need, or am i talking more along the lines of smaba client?
Basically, I want to install Samba on my linux desktop so that it can be networked with 1) my other desktop that is windows, 2) the LAN that currently exists that has both linux servers, windows servers, and a whole bunch of windows desktops, and 3) getting my windows desktop to see my linux desktop.
I assume that the connections for all these scenarios are TCIP-based. Or can be TCIP based, and therefor we go with Samba rather than mounting hard drives or the like.
So, to go back to my original question , would you then call my linux desktop a samba client or samba server?
and do i just set up samba as normal or is there something in particular I need to focus on , if we are not calling it samba server.
When your Windows machines "see" your Linux or when your windows machines access a share folder or maybe a printer in your linux machine, then you Linux machine is playing the role of a server. It is serving a shared folder, a shared printer...
When you want to access a shared folder in a windows machine, your linux is playing the role of a client.
Start by disabling the firewall in your linux machine and configure Samba as security=share.
over lunch , I was told that the easiest simplest way to do what i want to do was to either a) network into a linux box that already exists as a samba server, even though no one is using it right now or b) set up a "network group".
Does this not make more sense?
(frantically looking in the indexes of all my books now.. .)
I think that setting up a samba server is not hard. For start, there is just 4 settings you must change in global section of /etc/samba/smb.conf:
netbios name = THE_NAME_YOUR_LINUX_WILL_BE_SEEN_IN_WINDOWS
server string = Samba server on my linux
To add a read-only share to your new samba server,
comment = My first samba share
path = /path/to/your/share/on/linux
read only = Yes
browseable = Yes
and start your samba server.
The firewall issue I mentioned before is more trick. Windows need the broadcast packets and several TCP ports like 137, 138 and others I can't remober right now. So my advice to shutdown the firewall, at least in the internal interface.
alright. i've printed it out and added it to the pile.
what's the difference between Samba and NFS? (assuming NFS clienting can/does include Windows computers.)
You use NFS when you want to create a share between Linux machines.
You use SAMBA to configure your Linux machine to communicate with a Windows machine (initiated via the Windows machine).
You use SMBCLIENT when you to create a share from a Linux machine to a Windows machine.
I installed CentOS 4.2 (server) and installed the firewall. I set up my Linux side SAMBA via System Settings/Server Settings/SAMBA. The desktop installation did not have these options. I verified I could ping both my Windows machine and my Linux machine. I set up a password - using smbpasswd <username> on the Linux machine for the Windows user. At the Windows DOS prompt, I used the net use command to connect to my Linux machine. You can also use the Explorer/Tools/Map Network Drive option.
It may be easier, at first, to create a share on the Windows machine, then on the Linux machine, use the smbclient command - smbclient //<IP_of_Windows_machine>/<sharename>. You should be prompted for a password... if the connection is made and the share was setup properly. If this works, then test in the other direction.