linked server from sql 2000 to sql 2005

Hi all,
I'm trying to set up a linked server from a SQL Server 2000 (SQLSource)
to a SQL Server 2005 (SQLDest), but when I try to launch a query from my
computer to the SQLSource and it access the SQLDest, I get the "Error 18456:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
I have enabled the remote conections in the SQL Server 2005 box, and I
have setup the SPNs (to the service account and to the servers accounts) to
allow delegation with no success.
What am I doing wrong?
Any comment could be very helpful. Thanks you very much in advance.
Kind Regards.
JavierYou must execute sp_addlinkedsrvlogin procedure.
And you must mapping loginid and password betwen local and remote.
"Javier Pavon"?? ??? ??:

> Hi all,
> I'm trying to set up a linked server from a SQL Server 2000 (SQLSource)
> to a SQL Server 2005 (SQLDest), but when I try to launch a query from my
> computer to the SQLSource and it access the SQLDest, I get the "Error 1845
6:
> Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
> I have enabled the remote conections in the SQL Server 2005 box, and I
> have setup the SPNs (to the service account and to the servers accounts) t
o
> allow delegation with no success.
> What am I doing wrong?
> Any comment could be very helpful. Thanks you very much in advance.
> Kind Regards.
> Javier|||Hi
Thanks for your answer, but I need to use the user's security context in
the connection, I have an AD group with privileges to the SQL Server 2005 an
d
I can't create a login mapping for each of its members.
Best regards.
"hongju" wrote:
[vbcol=seagreen]
> You must execute sp_addlinkedsrvlogin procedure.
> And you must mapping loginid and password betwen local and remote.
> "Javier Pavon"?? ??? ??:
>|||In addition to spn requirements, there are also delegation
requirements. You can find more information in books online.
Check 2005 BOL for the topic: Configuring Linked Servers for
Delegation.
Check 2000 BOL for the topic: Security Account Delegation
-Sue
On Thu, 4 May 2006 03:46:02 -0700, Javier Pavon
<JavierPavon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi
> Thanks for your answer, but I need to use the user's security context in
>the connection, I have an AD group with privileges to the SQL Server 2005 a
nd
>I can't create a login mapping for each of its members.
> Best regards.
>"hongju" wrote:
>|||Hi
Thanks for your help, only one question... It should be necessary to
install de SQL Server 2005 Native Client in the SQL 2000 box? It still is no
t
working for me after follow the steps in bol.
Regards.
"Sue Hoegemeier" wrote:

> In addition to spn requirements, there are also delegation
> requirements. You can find more information in books online.
> Check 2005 BOL for the topic: Configuring Linked Servers for
> Delegation.
> Check 2000 BOL for the topic: Security Account Delegation
> -Sue
> On Thu, 4 May 2006 03:46:02 -0700, Javier Pavon
> <JavierPavon@.discussions.microsoft.com> wrote:
>
>|||You'd want to install the native client.
Are you getting the same error? If not, what is the error
text and error number?
There are some issue with DTC that you could be hitting as
well but it's hard to say without the full text of the error
you are hitting.
-Sue
On Mon, 8 May 2006 00:25:02 -0700, Javier Pavon
<JavierPavon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi
> Thanks for your help, only one question... It should be necessary to
>install de SQL Server 2005 Native Client in the SQL 2000 box? It still is n
ot
>working for me after follow the steps in bol.
> Regards.
>"Sue Hoegemeier" wrote:
>|||Thanks for your interest, Sue. I'm getting the same error, "Error 18456:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
Do you know if there any issue on installing the Native client in a SQL
Server 2000 SP4 machine?
Regards and thanks again.
"Sue Hoegemeier" wrote:

> You'd want to install the native client.
> Are you getting the same error? If not, what is the error
> text and error number?
> There are some issue with DTC that you could be hitting as
> well but it's hard to say without the full text of the error
> you are hitting.
> -Sue
> On Mon, 8 May 2006 00:25:02 -0700, Javier Pavon
> <JavierPavon@.discussions.microsoft.com> wrote:
>
>|||You can install the client on an a 2000 SP4 machine.
It looks like the delegation isn't working correctly or
isn't setup right if you are still getting that error. Those
can be hard to pin down. There is a windows server utility
that will log details on Kerberos errors - I've had to use
that in the past. Can't remember where I got it though -
maybe someone else can remember. Usually, it's been issues
with the spn, having duplicate spns, etc.
-Sue
On Mon, 8 May 2006 23:17:02 -0700, Javier Pavon
<JavierPavon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks for your interest, Sue. I'm getting the same error, "Error 18456:
>Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'"
>Do you know if there any issue on installing the Native client in a SQL
>Server 2000 SP4 machine?
>Regards and thanks again.
>
>"Sue Hoegemeier" wrote:
>|||Thanks you Sue,
I'm working on that, I've seen that the connection isn't being made by
Kerberos, I have to look into it.
Best regards
"Sue Hoegemeier" wrote:

> You can install the client on an a 2000 SP4 machine.
> It looks like the delegation isn't working correctly or
> isn't setup right if you are still getting that error. Those
> can be hard to pin down. There is a windows server utility
> that will log details on Kerberos errors - I've had to use
> that in the past. Can't remember where I got it though -
> maybe someone else can remember. Usually, it's been issues
> with the spn, having duplicate spns, etc.
> -Sue
> On Mon, 8 May 2006 23:17:02 -0700, Javier Pavon
> <JavierPavon@.discussions.microsoft.com> wrote:
>
>sql