I browsed the groups but non of the discussions came close to the
following issue.

We are having a custom cascading GINA for XP that allows fingerprint
logon. The fingerprint component runs as a COM server in a separate
process that gets started from the COM client which in turn is called
from GINA.
Everything works fine when until Remote Desktop session is made to the
system running our GINA. Then I see that the GINA is called again from
scratch (WlxNegotiate, WlxInitialize ... is being called) and the
workstation is locked (on the target PC where our GINA resides). When I
try now to unlock the target PC with Ctrl+Alt+Del a call is made to the
fingerprint component and at the call of CreateInstance the call fails
with the error message:
"No process is on the other end of the pipe." 0x800700E9.
I assume the try to call the COM server is always made localy on the
target pc independent of the fact that the credentials are being sent
from the client pc, or? Are any policies for running the COM changed
when Remote Desktop connection is received?

I would appreciate any tip what the reason for the error could be.

Igor Jovanovski