RE: Fwd: RE: [SLE] Using Samba

20 Jun 2005

      I am using 
On Saturday 18, June 2005 @ 11:16 PM, Jerome Lyles wrote:
...
On Saturday 18 June 2005 05:27 pm, Susemail wrote:
...
----------  Forwarded Message  ----------
Subject: RE: [SLE] Using Samba
Date: Friday 17 June 2005 03:01
From: Greg Wallace 
To: suse-linux-e@suse.com
On Thursday, June 16, 2005 @ 4:43 PM, Jerome wrote:
...
On Wednesday 15 June 2005 02:54, Greg Wallace wrote:
...
On Tuesday, June 14, 2005 @5:02 PM, Jerome wrote:
...
On Monday 13 June 2005 01:25, Greg Wallace wrote:
...
I share a linux directory with my Windows machine.  Try adding --
wins support = yes
security = share
to your [global] section.
Done
...
Using Yast I could not set privileges for 'nobody' but I did notice nobody
has 
a predefined password.  I've seen this before with other system users.
I've never been able to find out what the password is.  I'm going to delete
it 
to see if that helps.  Usually the system will recreate it though.  In this
case it's a six token password.
ps: Yast insists on a password so I'll use my user password instead of the
one supplied.
pps: It changed the password back to the system one (Suse 9.3) anyone know
what it is?
...
...
...
I don't even get a Login Window.  I click on My Network Places and
there's a folder there with the pipeline under it that you see on a
network
Me too.
...
...
I get this message when I access shareddocs:
\\Linux\shareddocs is not accessable.  You might not have permission to
use
this network resourse (Which is the core of my problem now).  The group
name
...
could not be found.
...
...
...
You probably have some additional setup work to do on Linux before you
...
*)  Set up the folder in Linux that matches the path= name.  Mine is
shareddocs (and at the root level; i. e., /shareddocs on Linux).  The
owner
...
...
of shareddocs is user nobody (built-in Linux user) and the group is
...
...
...
group I set up that matches my Windows workgroup name.
See smb.conf below.
...
*)  Make sure any users that will access the share are assigned to
...
...
...
group on your Linux machine.  I assigned the built-in "nobody" user to
the
...
...
group and, with the "guest account = nobody" option in Samba, that's
I wonder where it's looking?
the
that
the
...
id
I also added my Linux user id to that group and also root, giving me
access to the folder on the Linux side.
...
I holding off adding root for now.
...
Once all of that was done, I went to "My Network Places" and added
\\Linux\SharedDocs (yes, I named my Linux machine Linux -- lots of
imagination at work there huh!).  Now, if I double click on that
folder,
...
...
I'm looking at all of the files and directories in the Linux
shareddocs
directory from my Windows machine (sub-directories show up as
folders).
Hope this is enough to get you started.
Greg
Thanks Greg, is was enough to get me started (all of yesterday) and 
almost finished.  But there is still a permissions roadblock.
...
...
...
Xp shares using smb:// works just fine, I have learned today.  However
using
...
the Linux Desktop icon: Network Browsing, gets me to this address:
slp://awws/[awws://192.168.0.2:3703?name=MyVaio&version=2.0&guid=73780010-
...
...
28e9-1e0e-a750-9f349deee3b3]
...
That displays this message:
Service Attributes
awws://192.168.0.2:3703
Instead of the Windows share.
In the 9.3 Administration guide on p.542 it says:
security = share: 'A password is firmly assigned to a share.'
Do shares have passwords assigned to them automatically?
...
...
...
# smb.conf is the main Samba configuration file. You find a full
commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
# Date: 2005-04-04
[global]
  workgroup = MYHOME
  printing = cups
  printcap name = cups
  printcap cache time = 750
  cups options = raw
  printer admin = @ntadmin, root, administrator
  username map = /etc/samba/smbusers
  map to guest = Bad User
I don't have the line below, but I don't see why it would be a problem
...
include = /etc/samba/dhcp.conf
I don't have any of the lines from here..
...
logon path = \\%L\profiles\.msprofile
  logon home = \\%L\%U\.9xprofile
  logon drive = P:
  add machine script = /usr/sbin/useradd  -c Machine -d
/var/lib/nobody
...
-s /bin/false %m$
  domain logons = Yes
... to here
...
domain master = No
For the line above, I have
  Domain master = False
domain master = No - is the default
...
idmap gid = 10000-20000
  idmap uid = 10000-20000
  wins support = yes
The line below should say security = share
security = user - this is the default (Suse 9.3)
I did try share, no access.
...
I also have the following lines
unix extensions = Yes - tried this,no change
...
socket options = ISO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
  veto files = /* .eml/* .nws/riched20.dll/*.{*}/
  syslog = 0 - added this
  log level = 1 - added this
...
[shareddocs]
path = /home/adriel/shareddocs
  guest ok = yes
  guest account = nobody
  force group = MYHOME
I also have the following lines
  force create mode = 0060
  force directory mode = 0070
  create mask = 0770
  directory mask = 0770
  read only = no
Now, if I were using /home/adriel/shareddocs for my share, then if I did
cd /home/adriel
dir
I would see
drwxrwx--- ... nobody ... myhome ... shareddocs
drwxrwxr-x ... nobody ... myhome ... shareddocs
...
...
It being a linux share, in order to mount the directory you need x
privileges on that directory.  That security is enforced across to
Windows,
so windows cannot even look at what's in the directory unless it (nobody)
has that privilege.  I don't have to enter a password to display the
"share" on Windows.  I had, I think, the same errors as you when I first
started setting this up.  I believe you're definitely down to getting the
security right on Linux.  Once you do that, you should be able to change
to
that directory on Windows.
Greg Wallace
Hi Greg,
I have tried many things, starting with your suggestions.  Then I tried 
accessing the Samba Server on it's own host.  Sometimes I used 
smb//:adriel@linux/users or smb//:linux/users and sometimes I used the 
Network desktop Icon (remote:/).  I found that I cannot log on to the Samba
...
Server on it's own host: Access denied!  I hope this is a vital clue to 
someone.  There should be an obvious reason(s) (to someone) why I can't log
...
on to the Samba Server on it's own host using my own user and password on 
this system.
...
This will interest you Greg. When I use remote:/ (Network Desktop Icon) to 
access your example:
...
[shareddocs]
...
path = /home/adriel/shareddocs
  guest ok = yes
  guest account = nobody
  force group = MYHOME
  force create mode = 0060
  force directory = 0070
  create mask = 0770
  directory mask = 0770
  read only = no
I get this error Message:
Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: Invalid argument
...
I'm surprised too.  I'm using Suse 9.3.  What's the correct way to send a 
'full bug report'?
...
Still seeking access,
Jerome
Jerome:
     I was never able to get "security = user" to work, so, along the way,
you should occasionally switch that back to "security = share" to see if you
can get connected.  After that, you can work on getting "security = user" to
work as a separate task.  The difference is that you should get a prompt for
a user id and password with "security = share" (based on SAMS Teach Yourself
Samba in 24 hours).
     One thing I notice is that you are using --

username map = /etc/samba/smbusers, which contains, on my machine --

root = administrator admin
;nobody = guest pcguest smbguest
Linux: /etc/samba

I'm using

username map = /etc/samba/user.map, which has one line in it --

nobody=*

I'm guessing that that line says "map any user that comes in to nobody".

Greg Wallace