ED]
> > Sent: Sunday, March 16, 2003 11:24 PM
> > To: Ken Cross
> > Cc: 'Multiple recipients of list SAMBA-TECHNICAL'; 'Andrew Bartlett'
> > Subject: Re: [PATCH] Joining domains specifying auth realm
> >
> >
> > On Sat, 2003-03-15 at 03:
Phone 865.675.4070 ext 31
[EMAIL PROTECTED]
> -Original Message-
> From: Andrew Bartlett [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 16, 2003 11:24 PM
> To: Ken Cross
> Cc: 'Multiple recipients of list SAMBA-TECHNICAL'; 'Andrew Bartlett'
> Sub
On Sat, 2003-03-15 at 03:01, Ken Cross wrote:
> Let's try this again. The previous patch I submitted didn't work in
> some configurations. (ads->auth.realm needs to be preserved over the
> ads_connect call.)
If it's not preserved, won't it be free()ed in the process?
And shouldn't change the co
Let's try this again. The previous patch I submitted didn't work in
some configurations. (ads->auth.realm needs to be preserved over the
ads_connect call.)
This patch is for SAMBA_3_0.
Ken
Ken Cross
Network Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PR
On Wed, 2003-03-12 at 02:06, Ken Cross wrote:
> Here's a patch for net_ads.c that will allow the realm to be specified
> with -U, such as:
>
> net ads join -U [EMAIL PROTECTED]
>
> This is for SAMBA_3_0 -- I presume it's very similar for HEAD.
>
> I noticed that net is getting this message:
>
t; Sent: Thursday, March 06, 2003 3:38 PM
> To: Ken Cross
> Cc: 'Multiple recipients of list SAMBA-TECHNICAL'
> Subject: Re: Joining domains specifying auth realm
>
>
> On Fri, 2003-03-07 at 03:44, Ken Cross wrote:
> > Samba-folk:
> >
> > I've
On Fri, 2003-03-07 at 03:44, Ken Cross wrote:
> Samba-folk:
>
> I've run into a problem that I'd like to throw open for a general
> solution.
>
> The problem is joining an Active Directory, say AD1.COMPANY.COM, but
> specifying a different authentication realm for the username/password,
> say AD2
Samba-folk:
I've run into a problem that I'd like to throw open for a general
solution.
The problem is joining an Active Directory, say AD1.COMPANY.COM, but
specifying a different authentication realm for the username/password,
say AD2.COMPANY.COM. For instance, this currently fails:
net ads j
