2005 Cluster linked server issue

We have a two node cluster with two SQL 2005 instances installed.  For the
most part things work.  This morning we had Instance1 on Node1 & Instance2 o
n
Node2.  When I created a linked server on Instance1 pointed at Instance2
(under the aforementioned node conditions) & set the security context to use
the current login's security context, it didn't do that.  Instead when linke
d
server commands were issued, it tried to connect to Instance2 using NT
AUTHORITY\ANONYMOUS LOGON.

When we put both Instance1 & Instance2 on Node1, everything works.  When we
put both Instance1 & Instance2 on Node2, everything works.  But when the
instances are on different nodes, the linked server stuff gets screwy.

Anyone have any ideas?  Another thing I'll throw in is that I only get
the error when connecting to Instance1 from another machine (my
workstation, app server, etc.) & running a linked server query.  When I
connect to Instance1 locally on that box, the linked server query
performs fine.  It's almost as if when my windows credentials travel
from my workstation to Node1 and then to Node2, things get messed
up....


CB  wrote:
> We have a two node cluster with two SQL 2005 instances installed.  For the
> most part things work.  This morning we had Instance1 on Node1 & Instance2
 on
> Node2.  When I created a linked server on Instance1 pointed at Instance2
> (under the aforementioned node conditions) & set the security context to u
se
> the current login's security context, it didn't do that.  Instead when lin
ked
> server commands were issued, it tried to connect to Instance2 using NT
> AUTHORITY\ANONYMOUS LOGON.
>
> When we put both Instance1 & Instance2 on Node1, everything works.  When w
e
> put both Instance1 & Instance2 on Node2, everything works.  But when the
> instances are on different nodes, the linked server stuff gets screwy.