FW: [Samba] Accessing Samba share with Win2k

[Neil Muller]

Have you looked at setting options like "force user" and "force group"? There
are similar options for "create mode", "directory security mask", "create mask".

Neil


Quoting Janyce Wynter <janycewynter at cnwl.igs.net>:

> That's not the problem.
> 
> The same usernames & passwords have been created everywhere. SEEING the
> shares 
> isn't the problem. The problem is that files written to the public share
> should 
> be written as the user smbuser:smb, just like on the Win98 and WinME
> computers 
> (and not as user Janyce).
> 
> Janyce
> 
> On July 2, 2002 2:56 AM, Neil Muller [SMTP:neil at neologix.net] wrote:
> > On Sun, 2002-06-30 at 15:16, Janyce Wynter wrote:
> > > I'll keep that under consideration (I'm a bit rusty at rpm's). But
> given 
> the
> > >
> > > way the file ownership seems to be working, I think it's more of a
> Win2k
> > > configuration issue. I think I need to tell my Win2K machine
> (blackhawk)
> > > that
> > > Janyce is a member of the smb group on the samba server baldeagle.
> (And I
> > > don't
> > > know how to do that.)
> > You need to add your user to the smbpasswd file
> >
> > eg. smbpasswd -a <username>
> >
> > If the username and password are the same as the user on your w2k
> > machine and both machines are in the same workgroup and you have
> > encrypted passwords enabled in smb.conf then you should be able to
> see
> > your samba shares from w2k. See
> > http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection.html (or
> pdf
> > if you prefer).
> >
> > Neil
> >
> >
> >
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
> 
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
> 
> 
>