Displaying 10 results from an estimated 10 matches for "ravasio".
2013 Jul 22
1
Dependency upon raised error/exception messages.
Hey everyone,
first of all, thank you for the tremendous work and effort on making Rails
more awesome every day.
I''ve brought up this "issue" on Github last Friday. [1] Steve Klabnik told
me to bring the discussion here, as it''s more appropriate.
The thing is, there is some amount of logic scattered around Rails (and its
tests) that depends upon error/exception
2017 Oct 20
0
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On Fri, 20 Oct 2017 15:02:45 +0200
Giuseppe Ravasio via samba <samba at lists.samba.org> wrote:
> Hi,
> we are testing a new AD domain that will replace our old NT4 one, and
> we are setting up a new cifs vserver of our Netapp filer (running
> Clustered Dataontap 9.2).
>
> The new AD domain was a clean deployment created us...
2017 Oct 23
0
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On Mon, 23 Oct 2017 09:11:23 +0200
Giuseppe Ravasio <giuseppe_ravasio at ch.modiano.com> wrote:
> On 10/20/2017 05:48 PM, Rowland Penny via samba wrote:
> >> So I tried what is suggested in this thread:
> >> https://lists.samba.org/archive/samba/2016-April/thread.html#199609
> >
> > I really should have said...
2017 Oct 23
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On 10/23/2017 09:29 AM, Rowland Penny via samba wrote:
> All that using '--use-rfc2307' does is allow the use of rfc2307
> attributes such as 'uidNumber' and 'gidNumber', it does not
> populate any of the rfc2307 attributes.
>
> DCs works slightly different from Unix domain members, they use
> 'xidNumber' attributes in idmap.ldb, these attributes
2017 Oct 24
0
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On Tue, 24 Oct 2017 12:27:18 +0200
Giuseppe Ravasio <giuseppe_ravasio at ch.modiano.com> wrote:
> On 10/23/2017 10:26 AM, Rowland Penny via samba wrote:
> > OK, have you tried asking the Netapp company, 'how do I use this
> > with Active Directory' ?
>
> In this specific case no, but I already tried to open CIFS...
2017 Oct 23
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On 10/20/2017 05:48 PM, Rowland Penny via samba wrote:
>> So I tried what is suggested in this thread:
>> https://lists.samba.org/archive/samba/2016-April/thread.html#199609
>
> I really should have said there that using '513' wasn't a good idea ;-)
ok I'll revert to 100 ;-)
> The only way to get the same IDs everywhere is to use the winbind
>
2017 Oct 20
0
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On Fri, 20 Oct 2017 16:47:43 +0200
Giuseppe Ravasio <giuseppe_ravasio at ch.modiano.com> wrote:
> Sorry for eventually wrong AD terminology!
Don't worry about it, it is just confusing when you call a DC, a PDC,
call it your first DC or anything, just don't call it a PDC ;-)
>
> > You haven't fixed the 'xidNumber...
2017 Oct 24
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
On 10/23/2017 10:26 AM, Rowland Penny via samba wrote:
> OK, have you tried asking the Netapp company, 'how do I use this with
> Active Directory' ?
In this specific case no, but I already tried to open CIFS support cases
but at the end they tell me that It works as expected with a MS DC and
that Samba DC is not supported by them.
I cannot omit that I use Samba because they always
2017 Oct 20
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
Hi,
we are testing a new AD domain that will replace our old NT4 one, and we
are setting up a new cifs vserver of our Netapp filer (running Clustered
Dataontap 9.2).
The new AD domain was a clean deployment created using "samba-tool
domain provision --server-role=dc --use-rfc2307 ...".
All seems to work well and the Netapp filer joins the domain without
errors and seems to run fine.
2017 Oct 20
2
Samba 4.6.7 AD, Netapp CDOT 9.2 and missing "Domain Users" membership
Sorry for eventually wrong AD terminology!
> You haven't fixed the 'xidNumber:100 issue', giving 'Domain Users' the
> ID of '513' is not a good idea and I think you may have just changed
> '100' in idmap.ldb to '513'
>From the AD DC (;-)) shell the user was missing the "Domain Users" group
and we tought that could be a xidNumber