ADC error 8286, but inter-org is enabled...

Trying to achieve co-existence between old Ex 5.5 org (in NT4) and new Exch
2003 org (in 2003 AD). All users migrated to AD, SID's preserved, mailboxes
in 5.5. When using ADC, the 5.5 to 2003 CA works fine, but the 2003 to 5.5 CA
generates error 8286 "will not replicate CN=username because source is a
custom recipient and destination is a mailbox. If this is a problem, consider
making the connection agreement inter-organizational". But it is
inter-organizational....we have selected that option in the agreement. Due to
this, we only get 2 of the 4 values that we need to see on the
ADC-Global-Names attribute (we get the EX5, Forest values but not the NT5,
forest values). Any history on this? Thanks for any input.

JimBartlett
Mon Oct 30 09:05:02 CST 2006

Sorry, tired.....error is 8260, not 8286

"Jim Bartlett" wrote:

> Trying to achieve co-existence between old Ex 5.5 org (in NT4) and new Exch
> 2003 org (in 2003 AD). All users migrated to AD, SID's preserved, mailboxes
> in 5.5. When using ADC, the 5.5 to 2003 CA works fine, but the 2003 to 5.5 CA
> generates error 8286 "will not replicate CN=username because source is a
> custom recipient and destination is a mailbox. If this is a problem, consider
> making the connection agreement inter-organizational". But it is
> inter-organizational....we have selected that option in the agreement. Due to
> this, we only get 2 of the 4 values that we need to see on the
> ADC-Global-Names attribute (we get the EX5, Forest values but not the NT5,
> forest values). Any history on this? Thanks for any input.

jude
Fri Nov 10 12:43:02 CST 2006

Hi Jim,

The error message you indicate seems to be a problem with the ADC sending
information back to the 5.5 server.

In the 5.5 server what LDAP port are you communicating with AD.

Also when the setup the connection agreement did you setup a 2-way agreement
or 2 1-way agreements

"Jim Bartlett" wrote:

> Sorry, tired.....error is 8260, not 8286
>
> "Jim Bartlett" wrote:
>
> > Trying to achieve co-existence between old Ex 5.5 org (in NT4) and new Exch
> > 2003 org (in 2003 AD). All users migrated to AD, SID's preserved, mailboxes
> > in 5.5. When using ADC, the 5.5 to 2003 CA works fine, but the 2003 to 5.5 CA
> > generates error 8286 "will not replicate CN=username because source is a
> > custom recipient and destination is a mailbox. If this is a problem, consider
> > making the connection agreement inter-organizational". But it is
> > inter-organizational....we have selected that option in the agreement. Due to
> > this, we only get 2 of the 4 values that we need to see on the
> > ADC-Global-Names attribute (we get the EX5, Forest values but not the NT5,
> > forest values). Any history on this? Thanks for any input.

JimBartlett
Fri Nov 10 12:48:02 CST 2006

We were using 2 one way connections, the only supported method for inter-org
migrations.

We have given up and gone the "standard" route and preserved the org name,
joining our Exch 2K3 to our existing 5.5 org. That has worked out fine. MS
refused to provide assistance, despite the ADC still being a supported
product.

Thanks for your reply.

Jim

"jude" wrote:

> Hi Jim,
>
> The error message you indicate seems to be a problem with the ADC sending
> information back to the 5.5 server.
>
> In the 5.5 server what LDAP port are you communicating with AD.
>
> Also when the setup the connection agreement did you setup a 2-way agreement
> or 2 1-way agreements
>
> "Jim Bartlett" wrote:
>
> > Sorry, tired.....error is 8260, not 8286
> >
> > "Jim Bartlett" wrote:
> >
> > > Trying to achieve co-existence between old Ex 5.5 org (in NT4) and new Exch
> > > 2003 org (in 2003 AD). All users migrated to AD, SID's preserved, mailboxes
> > > in 5.5. When using ADC, the 5.5 to 2003 CA works fine, but the 2003 to 5.5 CA
> > > generates error 8286 "will not replicate CN=username because source is a
> > > custom recipient and destination is a mailbox. If this is a problem, consider
> > > making the connection agreement inter-organizational". But it is
> > > inter-organizational....we have selected that option in the agreement. Due to
> > > this, we only get 2 of the 4 values that we need to see on the
> > > ADC-Global-Names attribute (we get the EX5, Forest values but not the NT5,
> > > forest values). Any history on this? Thanks for any input.