samba - Jan 2003 - Beginner with a beginner's question..

Hallo Samba mailing list


I am a VERY new user to Linux and have just installed it (SUSE version 8.1)
and can just about make my way around the machine although there a many
things that I still don't know how to do (eg. looking at the network
neighborhood the Linux machine should be able to see).

I have several Windows PCs (running maily NT and Win 98) and the first
obvious thing is to get these connected to the new Linux box (there is a
domain and a work goup defined but I thought it easiest to get it in the
workgroup first)

After some study I leared that SAMBA is responsible for all this so this
was installed (from SUSE CDs) and I tried following the docs delivered with
it and on the Web but this has proved unsuccessful first time around and
after several hours of sweating it out a helping hand seems required.


a: I have modifed the samba sonfi file at /etc/samba/smb.config to include
my workgroup called MJB but could not see any other changes needed (or
don't understand what else to change..)

b: I have tested the config with /usr/sbin/testparm which doesn't give any
errors (at least)

c: with smbclient -L LAPTOP3       (LAPTOP3 is a laptop in the work group
with Win 98 on it) I can enter its password and see its shares (NT
computers can not be accessed with their passwords though, but they do
allow a password attempt to be made).

d: I can ping the Linux box and from the Linux can ping other computers
(Browser works on the linux over ADSL modem - network uses DHCP so no fixed
IP addresses)

e: I try to start SAMBA using smbd -D and then nmbd -D (or rcsmb start,
which I assume is some sort of script delivered with the Linux installation
to do this simpler - instructed in the user's handbook). There is a message
to say that things have been started.


e: From Windows PCs I can not find the Linux PC in the network (it is
called Webserver in the hope that it will one day really be be able to run
a web server..).
I get the impression that there is no difference before or after starting
Samba (assuming that I have really started it).

I have sifted through FAQs and other help docs but can't seem to find
anything to steer me past this first hurdle.

Is anyone out there able to give a simple tip to a simpel beginner (without
frightening me with too much jargon) ? It must be very simple

Thanks

Mark


PS I originally tried editing the config file from the console (with root
password) by simply typing "edit smb.conf". An editor stared as well,
but I
don't know how to use it and also not how to close it ! I have now a
console open in editor mode which I can not manage to closed.. stupid eh
?....


M_J_Butcher@IEE.org

I think you should first learn how to use linux, than learn to use samba.

Learn about permissions!

Learn bash, vi, sed, grep, cat, less, find, cd, ls, chown, chmod, locate, and
cut.
All of these, except vi, have good man pages (man ls or man bash). There are
books on bash, vi, and sed, and they are needed.

Learn about permissions!

Learn how to print with linux. I don't mean set up a printer. I mean
learn how your printing software works. Printing problems will never go
away.

Learn about permissions!

It won't do you much good to use samba if you can't use your linux
box. Samba simply allows linux to interact with windows boxes. 

Joel


On Thu, Jan 23, 2003 at 05:52:45PM -0500, Mark Butcher
wrote:
> Hallo Samba mailing list
> 
> 
> I am a VERY new user to Linux and have just installed it (SUSE version 8.1)
> and can just about make my way around the machine although there a many
> things that I still don't know how to do (eg. looking at the network
> neighborhood the Linux machine should be able to see).
> 
> I have several Windows PCs (running maily NT and Win 98) and the first
> obvious thing is to get these connected to the new Linux box (there is a
> domain and a work goup defined but I thought it easiest to get it in the
> workgroup first)
> 
> After some study I leared that SAMBA is responsible for all this so this
> was installed (from SUSE CDs) and I tried following the docs delivered with
> it and on the Web but this has proved unsuccessful first time around and
> after several hours of sweating it out a helping hand seems required.
> 
> 
> a: I have modifed the samba sonfi file at /etc/samba/smb.config to include
> my workgroup called MJB but could not see any other changes needed (or
> don't understand what else to change..)
> 
> b: I have tested the config with /usr/sbin/testparm which doesn't give
any
> errors (at least)
> 
> c: with smbclient -L LAPTOP3       (LAPTOP3 is a laptop in the work group
> with Win 98 on it) I can enter its password and see its shares (NT
> computers can not be accessed with their passwords though, but they do
> allow a password attempt to be made).
> 
> d: I can ping the Linux box and from the Linux can ping other computers
> (Browser works on the linux over ADSL modem - network uses DHCP so no fixed
> IP addresses)
> 
> e: I try to start SAMBA using smbd -D and then nmbd -D (or rcsmb start,
> which I assume is some sort of script delivered with the Linux installation
> to do this simpler - instructed in the user's handbook). There is a
message
> to say that things have been started.
> 
> 
> e: From Windows PCs I can not find the Linux PC in the network (it is
> called Webserver in the hope that it will one day really be be able to run
> a web server..).
> I get the impression that there is no difference before or after starting
> Samba (assuming that I have really started it).
> 
> I have sifted through FAQs and other help docs but can't seem to find
> anything to steer me past this first hurdle.
> 
> Is anyone out there able to give a simple tip to a simpel beginner (without
> frightening me with too much jargon) ? It must be very simple
> 
> Thanks
> 
> Mark
> 
> 
> PS I originally tried editing the config file from the console (with root
> password) by simply typing "edit smb.conf". An editor stared as
well, but I
> don't know how to use it and also not how to close it ! I have now a
> console open in editor mode which I can not manage to closed.. stupid eh
> ?....
> 
> 
> M_J_Butcher@IEE.org
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

I've never worked with SuSE, but does "locate DIAGNOSIS.txt" file
turn
up anything?  It's a very good start.
> a: I have modifed the samba sonfi file at 
> /etc/samba/smb.config to include
> my workgroup called MJB but could not see any other changes needed (or
> don't understand what else to change..)
Did you give your samba machine a netbios name?
I guess in your case you'd pick something like "netbios name
webserver"
> c: with smbclient -L LAPTOP3       (LAPTOP3 is a laptop in 
> the work group
> with Win 98 on it) I can enter its password and see its shares (NT
> computers can not be accessed with their passwords though, but they do
> allow a password attempt to be made).
Can't help you here.
 
> e: I try to start SAMBA using smbd -D and then nmbd -D (or 
> rcsmb start,
> which I assume is some sort of script delivered with the 
> Linux installation
> to do this simpler - instructed in the user's handbook). 
> There is a message
> to say that things have been started.
Does a "ps ax|grep [sn]mbd" return anything?
This will list running processes name smbd or nmbd.  If there's nothing
returned, then the processes are dieing.

Does a "netstat -tln|grep ':139 '" return anything?
This lists -t (tcp) -l (listening) -n (number ports), and shows any
listening on that port.
> e: From Windows PCs I can not find the Linux PC in the network (it is
> called Webserver in the hope that it will one day really be 
> be able to run
> a web server..).
> I get the impression that there is no difference before or 
> after starting
> Samba (assuming that I have really started it).
Between ps and netstat, you should be able to find out if it stays
running.
 
> I have sifted through FAQs and other help docs but can't seem to find
> anything to steer me past this first hurdle.
DIAGNOSIS.txt
> PS I originally tried editing the config file from the 
> console (with root
> password) by simply typing "edit smb.conf". An editor stared 
> as well, but I
> don't know how to use it and also not how to close it ! I have now a
> console open in editor mode which I can not manage to 
> closed.. stupid eh
> ?....
This is probably either vi or emacs.  If a Ctrl-x does not seem to do
much except beep, it's vi.  If it's vi, press escape a few times to get
back to command mode (after a beep you're good), enter :w to write your
changes (if you want to save the file) and then :q to quit.  :q! quits
without saving changes.  If Ctrl-x doesn't beep at you it is probably
emacs, after you pressed Ctrl-x press Ctrl-c to quit.  You be prompted
about saving changes, etc.

You should look at editors and pick one that sounds like it's for you.
Learn it.  Until you do (and even after), consider using SWAT to manage
your smb.conf file.


~ Daniel







-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

Hi Jerry

Thanks Jerry.

Would you believe it, the thing started working just after sending the last
mail. I am not sure whether I really had a password issue or not but it was
probably because a LAN cable was loose in a hub and some one moved it just
as it was getting interesting. Anyway I realised sometime then that I could
no longer ping the Windows PC and after ensuring all was secure it worked.

I can now see and transfer data between PCs like there's no tomorrow.

My only restriction is that it doesn't work between Linux and NT PCs (they
can see each other but seem to hate having anything to do with each other).
My Win 98 PCs and Linux get on just fine. Maybe I can live with this for
the mean time and then while I'm learning Linux may find the utility I'm
missing....


Since things are communicating, I have started work on my second goal -
getting the Apache web server installed and operating. Thankfully this
worked first try and I have tranfered my HTML files to Linux and we can all
surf on to it locally. Once the wire wall issue is checked it should go
able to go public.

Next step is an Email server, which I understand is somewhat trickier -
we'll see.


By the way I see the mounting commands in the viewer software log files and
may well also do things by hand now that I know them and know that they
work - the viewer software is however useful because it works like it did
in Windows and delivers the command needed without the frustration of
sifting through (for me) complicated literature with a million options
(great for experts) but a jungle for newbies.

I also have nothing against learning Linux. I did learn a lot last year
when I compiled GNU software under CYGWIN (Bash shell for windows) - then I
had to learn enough to write script files and understand make files and
some of the utilities (does take some time...). One learns more every day
and has pleasure learning it - but the point is that a computer is there to
be useful and not just to be studied. SuSE and Red Hat seem to be doing
good jobs at making things simpler to use - the normal user probably
doesn't need to know any command line stuff to do things which he/she wants
to do (office, games, Internet etc.) I can imagine telling my little
daugher that she must first go away and read a book about bash, vi etc. and
then I will let her install her "Spelling program" - probably
wouldn't go
down too well and wouldn't help anyone.

Cheers

Mark