On Thu, 17 Sep 2009 16:42:50 +0100
Alex Crow wrote:
>
> > >
> > >
> > I'm not sure that Samba checks the Linux groups but Linux does. In a
> > Windows domain, all the accounts reside in the Domain. It may be
> > checking the Linux accounts for shares on the DC, but wouldn't be able
> > to
> >
> >
> I'm not sure that Samba checks the Linux groups but Linux does. In a
> Windows domain, all the accounts reside in the Domain. It may be
> checking the Linux accounts for shares on the DC, but wouldn't be able
> to on a member server. Perhaps one of the Linux gurus could answer your
Chris Osicki wrote:
On Wed, 16 Sep 2009 18:03:48 -0400
Gary Dale wrote:
Chris Osicki wrote:
Hi
I'm using Samba 3.0.33 on Solaris10 and have the following problem.
In the smb.conf I have
workgroup = CORPROOT
security = domain
and users authenticated to CORPROOT domain can
On Wed, 16 Sep 2009 18:03:48 -0400
Gary Dale wrote:
> Chris Osicki wrote:
> > Hi
> >
> > I'm using Samba 3.0.33 on Solaris10 and have the following problem.
> > In the smb.conf I have
> >
> > workgroup = CORPROOT
> > security = domain
> >
> > and users authenticated to CORPROOT domain c
Chris Osicki wrote:
Hi
I'm using Samba 3.0.33 on Solaris10 and have the following problem.
In the smb.conf I have
workgroup = CORPROOT
security = domain
and users authenticated to CORPROOT domain can connect shares
w/o problems, [homes] for example.
Now I would like to create a shar
Chris Osicki wrote:
Hi
I'm using Samba 3.0.33 on Solaris10 and have the following problem.
In the smb.conf I have
workgroup = CORPROOT
security = domain
and users authenticated to CORPROOT domain can connect shares
w/o problems, [homes] for example.
Now I would like to create a shar
Hi
I'm using Samba 3.0.33 on Solaris10 and have the following problem.
In the smb.conf I have
workgroup = CORPROOT
security = domain
and users authenticated to CORPROOT domain can connect shares
w/o problems, [homes] for example.
Now I would like to create a share and restrict access t
