HP3000-L Archives

March 1997, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael Anderson <[log in to unmask]>
Reply To:
Michael Anderson <[log in to unmask]>
Date:
Fri, 21 Mar 1997 17:51:48 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (66 lines)
Richard Trapp RAT wrote:
>
> 1) I can't seem to get write access.  I think I need to include a
> user/password somewhere, but I don't know where.
>

Well ya don't need to include a user or password anywhere if you don't want
to. You can supply a user if you like, but I think a password has a place in
the config of samba. I could be wrong, that did happen once. ;-)

Example one: I setup a secure (Using MPE Security) "HOME" share for everyone,
see below.

[homes]
        comment = Home Directories
        read only = no
        browseable = yes
        create mode = 0750
        writable = yes

Notice path is not specified and user is not specified. It will default to
the user (USER.ACCT) who is connecting and the path will default to that
users home group as configured by the MPE account manager(AM).

The Netbios user name must be a valid MPE USER.ACCT unless you use the
users.map file. Example: I log on to a hp3000/928 here as "MICHAEL.LAN", and
it has a  machine name of "HP928". So from a WFW logon you have two fields to
enter your netbios username and your username password. Here you need to user
your MPE USER.ACCT has the netbios username and the MPE passwords (password
syntax is: [userpass,acctpass]) as the username password.

Then when you connect to the share \\HP928\MICHAEL.LAN" the connect dialog
will at that time ask you for the password for that share. The password here
is again the MPE USER.ACCT passwords in the same syntax as
[userpass,acctpass]

Limitation exist here for the wfw users because they are limited to only one
concurrent username. To change usernames in wfw you need to log off as one
user than log back on as another user. However I think NT has a nice
work-around for this. Or I guess you could add to the complexity and use the
users.map file.

Example two: I have a non public secure share for SOURCE.LAN user only!

[wfw_source]
        comment = Windows PC source code files.
        path= /LAN/wfw_source
        public = no
        user = SOURCE.LAN
        writable = Yes
        create mode = 700
        printable = no

Here the same rules apply the netbios user is SOURCE.LAN which will be the
MPE user.acct used by SMBD at connect time.


Hope this will help,


--
Michael "I can't dance" Anderson,

TIW Corporation, Inc.
Systems Programmer.

ATOM RSS1 RSS2