6:24 a.m.
Hi,
As predicted I'm back with another unbelievably trivial question but I
cannot find an answer. I am trying to get SAMBA shares working and failing
miserably and I wanted to check the server name but having looked in every
corner of the desktop and searched the help files I can find no clue as to
how to find it or better yet change it.
Any help would be appreciated.
Cheers,
Bob.
11:47 a.m.
On Tuesday April 29 2008 10:07:36 am Bob Latham wrote:
> Things to keep in mind (approaches will vary depending on
> whether you're using KDE or Gnome):
How do I find out?
well, there are all sorts of ways, but, probably the easiest is
to just check down at the bottom of the login screen when you're
asked for your password, there should be some options down there
you can select and one is probably called 'Session' or something
like that, and it will pop up and offer you whatever desktops
you've got installed as selections to boot into - if you don't
know what you've got, it's probably Gnome, because KDE would
have required that you go into customization options when you
installed your system and consciously select it - that is,
unless you installed from the live kde-cd - if you have panels
both at the bottom and top of your screen, then it's almost
surely Gnome
> snip............
> gets you into the redhat firewall configuration utility if
> you're not using any others such as Shorewall or Firestarter
> Test each machine you want to participate in your network to
> see if you can ping it from the others, and whether it can
> ping the others...
do you know how to ping?
> There are Selinux related commands you
> must run depending on what you want to do - watch your
> Setroubleshoot warnings and messages to see if you're
> getting smb and nmb related denials.
> Finally, you may run
> into some rather esoteric issues if you're attempting to run
> the latest KDE4 with DCOP errors - check your system logs
> for DCOP related errors if you think you've got everything
> else right, and if you're running some flavor of KDE4...
Now that got complicated and I don't understand that bit. I
have now moved on a little but am now getting an error....
SELinux AVC Denial - flashing banner I can't stop!!!!!
SELinux is preventing the Samba daemon from reading user's
home directories.
Don't worry about the DCOP stuff. I doubt you're going to have
that issue. What version of Fedora are you running? Bets are off
if it's F9...
On the Selinux warnings, just click on the little star icon that
should be appearing near your flashing error message - it should
open up a window with some informative messages about the
problem and suggestions on commands to run to fix them
I'm stumped again!
I suppose I should do some reading to find out what on earth
SELinux is and then how to switch some of it off.
Flipping complicated just to share a folder this linux stuff.
<smile>
even Windows is complicated the first time you ever try to use
it - Linux is takes a bit more tweaking but you should be able
to get it -
--
Claude Jones
Brunswick, MD, USA
5:04 p.m.
On Tue, 2008-04-29 at 12:24 +0100, Bob Latham wrote:
Any help would be appreciated.
A problem I've commonly seen just popped into mind: People's machine's
only referring to themselves as "localhost", and users expecting to be
able to access it *as* localhost from another machine.
You're not doing that, are you?
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
2:10 a.m.
In article <200804291247.10870.cjones(a)levitjames.com>,
Claude Jones <cjones(a)levitjames.com> wrote:
On Tuesday April 29 2008 10:07:36 am Bob Latham wrote:
and offer you whatever desktops you've got installed as
selections to
boot into - if you don't know what you've got, it's probably Gnome
Well Gnome is the only option other than default system session.
> > snip............
>
> > gets you into the redhat firewall configuration utility if
> > you're not using any others such as Shorewall or Firestarter
> > Test each machine you want to participate in your network to
> > see if you can ping it from the others, and whether it can
> > ping the others...
do you know how to ping?
Yes. Well on everything except Linux it seems as when I just tried it I
found it worked fine but I could not find a way to stop it pinging. Not
even the escape key did anything. That just seem like being different for
the sake of it even if it means being really awkward. In the end I quit
the terminal and restarted it. I think that's stopped it but I'm not sure.
> I have now moved on a little but am now getting an error....
>
> SELinux AVC Denial - flashing banner I can't stop!!!!!
I've got rid of the flashing banner but not the problem.
> SELinux is preventing the Samba daemon from reading user's
> home directories.
Any suggestions how to work out what I need to kill in SELinux to let me
share a folder?
What version of Fedora are you running? Bets are off
if it's F9...
Looking at the iso file I downloaded as I cannot find any way to look this
up inside the desktop, the file says "fedora-8-live-i686.iso". I expect
that means Fedora 8.
On the Selinux warnings, just click on the little star icon that
should be appearing near your flashing error message - it should
open up a window with some informative messages about the
problem
Yes, I've stopped the banner now and as I wrote earlier it says "SELinux
is preventing the Samba daemon from reading user's home directories."
and suggestions on commands to run to fix them
It seems to offer no suggestions about how to get around that.
even Windows is complicated the first time you ever try to use
it - Linux is takes a bit more tweaking but you should be able
to get it -
Thanks again.
Bob.
7:02 a.m.
On Wed April 30 2008, Bob Latham wrote:
Yes, I've stopped the banner now and as I wrote earlier it says "SELinux
is preventing the Samba daemon from reading user's home directories."
> and suggestions on commands to run to fix them
It seems to offer no suggestions about how to get around that.
So, you're running Gnome, is what those options are telling you, and others
have explained the use of 'Ctl-c';
I don't use Gnome, but, I'm sure that setroubleshoot works the same under
Gnome as it does under KDE; when I get the flashing banner, on my desktop, a
star icon appears in my lower right panel in what is sometimes called the
system tray area - it is gold in color and five pointed. Clicking on that
should open a GUI with several sections to it. The top will describe your
problem in summary; the second will be a more detailed description; the third
should offer you command suggestions for allowing access:
For example, I was getting this:
Summary
SELinux is preventing the samba daemon from serving r/o local files to remote
clients.
Detailed Description
SELinux has preventing the samba daemon (smbd) from reading files on the local
system. If you have not exported these file systems, this could signals an
intrusion.
Allowing access
If you want to export file systems using samba you need to turn on the
samba_export_all_ro boolean: "setsebool -P samba_export_all_ro=1". The
following command will allow this access:setsebool -P samba_export_all_ro=1
So, running that command changed the selinux policies to allow the access; you
have to be root to run that command
If you can't see the star icon, look in your menus for setroubleshoot and that
should open the window I'm talking about...
--
Claude Jones
Brunswick, MD, USA
9:03 a.m.
In article <200804300802.24466.cjones(a)levitjames.com>,
Claude Jones <cjones(a)levitjames.com> wrote:
On Wed April 30 2008, Bob Latham wrote:
So, you're running Gnome,
So it seems yes.
is what those options are telling you, and others have explained the
use
of 'Ctl-c';
They have.
I don't use Gnome,
[Snip]
Summary SELinux is preventing the samba daemon
Thanks to everyone's help I'm now past that problem and have managed to
get a share working to my RISC OS machine but not Windows XP which refuses
ro connect. I need to read loads on samba to find out why. I suspect it is
to do with authenticating users.
[Snip]
If you can't see the star icon, look in your menus for
setroubleshoot
and that should open the window I'm talking about...
Thanks Claude, I'm slowly getting there.
Cheers,
Bob.
4:59 a.m.
On Wed, Apr 30, 2008 at 09:05:39AM +0100, Bob Latham wrote:
In article <20080430074959.GA31344@th-shell-1>,
Chris G <cl(a)isbd.net> wrote:
> On Wed, Apr 30, 2008 at 08:10:41AM +0100, Bob Latham wrote:
> "on everything except Linux"? I suspect by that you mean Windows! :-)
I can see why you would say that. In truth, I do use Windows when I have
to but by choice I use RISC OS. RISC OS does ping continuously but can be
stopped with the escape key, simple and logical. I've also used ping on
Apple but it was a while back and I cannot remember anything about it.
> On everything (including Linux) that I have worked on a ping command
> by default continues for ever.
It isn't the default on windows is it? Doesn't that do 5 cycles?
Oops, yes I agree, I meant to say on everything else other than
Windows that I have worked on.
> To stop it you do just the same as you would on the Windows (!)
> command line, hit CTRL/C.
I've never ever used that. Didn't know about it - thanks. How obscure!
It's been just about universal since the days of using teletypes as
terminals (which I remember quite well), CTRL/C sends an interrupt to
the currently running process.
As someone else pointed out using ESCape as an interrupt/break
character is 'obscure' as it's intended as a character escape, not a
process 'escape'.
--
Chris Green
3:13 a.m.
In article <1209541742.3104.7.camel(a)suspishus.lan.cameratim.com>,
Tim <ignored_mailbox(a)yahoo.com.au> wrote:
On Wed, 2008-04-30 at 08:10 +0100, Bob Latham wrote:
It's stopped the way that just about everything
command-line-based has
been stopped for the last 40 years or so: CTRL C
Thanks for that, never used it once.
> Any suggestions how to work out what I need to kill in SELinux
to let
> me share a folder?
On FC7 there's a SELinux management system adminstration GUI, and
in
there's a boolean sub-section which let you set options related to what
will be allowed with Samba. There's probably something similarly named
on FC8.
There is indeed, its just a question of working out which item or items is
causing the problem.
Sounds like it might be worth your while to get one of those
pocketbook
Fedora things from a news agent, the ones that are about the size of the
Readers Digest, and come with install discs. They're cheap, and usually
come with basics for beginners.
Didn't know that thanks.
Cheers,
Bob.
3:05 a.m.
In article <20080430074959.GA31344@th-shell-1>,
Chris G <cl(a)isbd.net> wrote:
On Wed, Apr 30, 2008 at 08:10:41AM +0100, Bob Latham wrote:
"on everything except Linux"? I suspect by that you mean
Windows! :-)
I can see why you would say that. In truth, I do use Windows when I have
to but by choice I use RISC OS. RISC OS does ping continuously but can be
stopped with the escape key, simple and logical. I've also used ping on
Apple but it was a while back and I cannot remember anything about it.
On everything (including Linux) that I have worked on a ping command
by default continues for ever.
It isn't the default on windows is it? Doesn't that do 5 cycles?
To stop it you do just the same as you would on the Windows (!)
command line, hit CTRL/C.
I've never ever used that. Didn't know about it - thanks. How obscure!
Cheers,
Bob.
2:49 a.m.
On Wed, Apr 30, 2008 at 08:10:41AM +0100, Bob Latham wrote:
> do you know how to ping?
Yes. Well on everything except Linux it seems as when I just tried it I
found it worked fine but I could not find a way to stop it pinging. Not
even the escape key did anything. That just seem like being different for
the sake of it even if it means being really awkward. In the end I quit
the terminal and restarted it. I think that's stopped it but I'm not sure.
"on everything except Linux"? I suspect by that you mean Windows! :-)
On everything (including Linux) that I have worked on a ping command
by default continues for ever.
To stop it you do just the same as you would on the Windows (!)
command line, hit CTRL/C.
--
Chris Green
2:49 a.m.
On Wed, 2008-04-30 at 08:10 +0100, Bob Latham wrote:
Yes. Well on everything except Linux it seems as when I just tried
it
I found it worked fine but I could not find a way to stop it pinging.
Not even the escape key did anything. That just seem like being
different for the sake of it even if it means being really awkward. In
the end I quit the terminal and restarted it. I think that's stopped
it but I'm not sure.
It's stopped the way that just about everything command-line-based has
been stopped for the last 40 years or so: CTRL C
The escape key wasn't actually meant for breaking out of things, it was
meant for escape codes (escape, plus something else, is a code).
Any suggestions how to work out what I need to kill in SELinux to
let
me share a folder?
On FC7 there's a SELinux management system adminstration GUI, and in
there's a boolean sub-section which let you set options related to what
will be allowed with Samba. There's probably something similarly named
on FC8.
Sounds like it might be worth your while to get one of those pocketbook
Fedora things from a news agent, the ones that are about the size of the
Readers Digest, and come with install discs. They're cheap, and usually
come with basics for beginners.
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
11:17 a.m.
On Tuesday 29 April 2008 06:24:48 am Bob Latham wrote:
Hi,
As predicted I'm back with another unbelievably trivial question but I
cannot find an answer. I am trying to get SAMBA shares working and failing
miserably and I wanted to check the server name but having looked in every
corner of the desktop and searched the help files I can find no clue as to
how to find it or better yet change it.
You can change the name of the samba server in the /etc/samba/smb.conf file,
tag 'netbios name' section 'global':
............
[global]
netbios name YOURDESIREDSERVERNAME
............
hth
best regards
Teo Fonrouge
9:07 a.m.
Thanks to Joachim, Chris, Tim and Claude who all answered my question,
what a helpful group of people. Cheers guys.
You don't make it clear what you think the relationship is
between your
problems with Samba shares and not knowing your server name.
Just checking everything that my limited knowledge can throw back at me. I
thought (wrongly ?) that \\servername\sharename was the core of SAMBA
sharing.
For some insights into various issues that come into play when trying
to
get Samba working see the recent thread on this list "Samba won't
dance"; you can find your Samba server name in the smb.conf file, which
is located in /etc/samba; there are a number of GUI's that you can use
to edit that file if you'd rather; 'system-config-samba' brings up the
minimalistic Redhat configuration utility; if you use the KDE desktop,
there's a comprehensive Samba configuration GUI built into the KDE
Control Center in the 'Internet & Network' section.
To be honest, I have no idea what GUI I'm using, I know that's sad but I'm
starting from nothing with linux.
Things to keep in mind (approaches will vary depending on whether
you're
using KDE or Gnome):
How do I find out?
You have to not only configure your Samba shares You have to make
sure
that the smb and nmb services are started
Ah. I had got as far as SMB services (guessed that much) didn't know about
nmb and have started that now.
- you may have a nice GUI
command called 'Services' where you can turn services on and off
Yes I have.
- look in your menus; else, 'man chkconfig' will explain to
you how to
use that command to turn services on and off You have to configure your
firewall to allow smb and nmb traffic, specifically on ports 137, 138,
139, and 445 - 'system-config-firewall'
Indeed it does and after reading this I have changed the settings to allow
SMB NMB.
gets you into the redhat firewall configuration utility if you're
not
using any others such as Shorewall or Firestarter Test each machine you
want to participate in your network to see if you can ping it from the
others, and whether it can ping the others... There are Selinux related
commands you must run depending on what you want to do - watch your
Setroubleshoot warnings and messages to see if you're getting smb and
nmb related denials. Finally, you may run into some rather esoteric
issues if you're attempting to run the latest KDE4 with DCOP errors -
check your system logs for DCOP related errors if you think you've got
everything else right, and if you're running some flavor of KDE4...
Now that got complicated and I don't understand that bit. I have now moved
on a little but am now getting an error....
SELinux AVC Denial - flashing banner I can't stop!!!!!
SELinux is preventing the Samba daemon from reading user's home
directories.
I'm stumped again!
I suppose I should do some reading to find out what on earth SELinux is
and then how to switch some of it off.
Flipping complicated just to share a folder this linux stuff. <smile>
Cheers,
Bob.
7:13 a.m.
On Tue April 29 2008, Bob Latham wrote:
Hi,
As predicted I'm back with another unbelievably trivial question but I
cannot find an answer. I am trying to get SAMBA shares working and failing
miserably and I wanted to check the server name but having looked in every
corner of the desktop and searched the help files I can find no clue as to
how to find it or better yet change it.
Any help would be appreciated.
You don't make it clear what you think the relationship is between your
problems with Samba shares and not knowing your server name. For some
insights into various issues that come into play when trying to get Samba
working see the recent thread on this list "Samba won't dance"; you can find
your Samba server name in the smb.conf file, which is located in /etc/samba;
there are a number of GUI's that you can use to edit that file if you'd
rather; 'system-config-samba' brings up the minimalistic Redhat configuration
utility; if you use the KDE desktop, there's a comprehensive Samba
configuration GUI built into the KDE Control Center in the 'Internet &
Network' section.
Things to keep in mind (approaches will vary depending on whether you're using
KDE or Gnome):
You have to not only configure your Samba shares
You have to make sure that the smb and nmb services are started - you may have
a nice GUI command called 'Services' where you can turn services on and off -
look in your menus; else, 'man chkconfig' will explain to you how to use that
command to turn services on and off
You have to configure your firewall to allow smb and nmb traffic, specifically
on ports 137, 138, 139, and 445 - 'system-config-firewall' gets you into the
redhat firewall configuration utility if you're not using any others such as
Shorewall or Firestarter
Test each machine you want to participate in your network to see if you can
ping it from the others, and whether it can ping the others...
There are Selinux related commands you must run depending on what you want to
do - watch your Setroubleshoot warnings and messages to see if you're getting
smb and nmb related denials.
Finally, you may run into some rather esoteric issues if you're attempting to
run the latest KDE4 with DCOP errors - check your system logs for DCOP
related errors if you think you've got everything else right, and if you're
running some flavor of KDE4...
--
Claude Jones
Brunswick, MD, USA
7:07 a.m.
On Tue, 2008-04-29 at 12:24 +0100, Bob Latham wrote:
As predicted I'm back with another unbelievably trivial question
but I
cannot find an answer. I am trying to get SAMBA shares working and
failing miserably and I wanted to check the server name but having
looked in every corner of the desktop and searched the help files I
can find no clue as to how to find it or better yet change it.
To check what it is, just look at a command prompt, it's usually there.
Or just typing in the "hostname" command will tell you, the machine name
will be the first word (up to the first dot), the rest is the domain
name.
You can tell Samba to use a particular machine name for itself, but
it'll have to resolve to an IP, its own IP for that to work. And that
resolution will have to work on all machines talking to each other with
Samba.
By default, Samba will use your machine's hostname. But, as I said
above, that name will have to resolve to an IP for all machines on the
Samba LAN.
If you want to change the machine name, then the hostname can make
temporary changes (they're not saved, it just changes for now), or you
can play with the /etc/sysconfig/network file for permanent settings.
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
6:34 a.m.
Bob Latham wrote:
Hi,
As predicted I'm back with another unbelievably trivial question but I
cannot find an answer. I am trying to get SAMBA shares working and failing
miserably and I wanted to check the server name but having looked in every
corner of the desktop and searched the help files I can find no clue as to
how to find it or better yet change it.
You mean /etc/sysconfig/network?
Any help would be appreciated.
Cheers,
Bob.
--
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
University of Kaiserslautern,Computer Center [RHRK],
Systems and Operations, High Performance Computing,
D-67653 Kaiserslautern, PO Box 3049, Germany
--------------------------------------------------
Phone: +49-631-205-2438, FAX: +49-631-205-3056
7:05 a.m.
On Tue, Apr 29, 2008 at 12:24:48PM +0100, Bob Latham wrote:
Hi,
As predicted I'm back with another unbelievably trivial question but I
cannot find an answer. I am trying to get SAMBA shares working and failing
miserably and I wanted to check the server name but having looked in every
corner of the desktop and searched the help files I can find no clue as to
how to find it or better yet change it.
The command "hostname" at the commad line will give you the
system's
name.
To change it you need to edit /etc/sysconfig/network.
--
Chris Green
8 a.m.
On Wed, 2008-04-30 at 08:10 +0100, Bob Latham wrote:
In article <200804291247.10870.cjones(a)levitjames.com>,
Claude Jones <cjones(a)levitjames.com> wrote:
> On Tuesday April 29 2008 10:07:36 am Bob Latham wrote:
> and offer you whatever desktops you've got installed as selections to
> boot into - if you don't know what you've got, it's probably Gnome
Well Gnome is the only option other than default system session.
> > > snip............
> >
> > > gets you into the redhat firewall configuration utility if
> > > you're not using any others such as Shorewall or Firestarter
> > > Test each machine you want to participate in your network to
> > > see if you can ping it from the others, and whether it can
> > > ping the others...
> do you know how to ping?
Yes. Well on everything except Linux it seems as when I just tried it I
found it worked fine but I could not find a way to stop it pinging. Not
even the escape key did anything. That just seem like being different for
the sake of it even if it means being really awkward. In the end I quit
the terminal and restarted it. I think that's stopped it but I'm not sure.
ctrl-c will stop ping.
> > I have now moved on a little but am now getting an error....
> >
> > SELinux AVC Denial - flashing banner I can't stop!!!!!
I've got rid of the flashing banner but not the problem.
> > SELinux is preventing the Samba daemon from reading user's
> > home directories.
Any suggestions how to work out what I need to kill in SELinux to let me
share a folder?
> What version of Fedora are you running? Bets are off
> if it's F9...
Looking at the iso file I downloaded as I cannot find any way to look this
up inside the desktop, the file says "fedora-8-live-i686.iso". I expect
that means Fedora 8.
> On the Selinux warnings, just click on the little star icon that
> should be appearing near your flashing error message - it should
> open up a window with some informative messages about the
> problem
Yes, I've stopped the banner now and as I wrote earlier it says "SELinux
is preventing the Samba daemon from reading user's home directories."
> and suggestions on commands to run to fix them
It seems to offer no suggestions about how to get around that.
> even Windows is complicated the first time you ever try to use
> it - Linux is takes a bit more tweaking but you should be able
> to get it -
Thanks again.
Bob.
--
=======================================================================
Regression analysis: Mathematical techniques for trying to understand
why things are getting worse.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
5869
days inactive
5870
days old
17 comments
7 participants
participants (7)
-
Aaron Konstam -
Bob Latham -
Chris G -
Claude Jones -
Joachim Backes -
Teo Fonrouge -
Tim