dotnet remoting: We use .Net Remoting as our communication channel. In our config file we have
a remoting section to use Windows security.

<system.runtime.remoting>
<customErrors mode="off" />
<application>
<channels>
<channel ref="tcp" port="38415">
<serverProviders>
<provider
type="Microsoft.Runtime.Remoting.Security.SecurityServerChannelSinkProvider,
Microsoft.Runtime.Remoting.Security, Culture=neutral, Version=2.0.18.0"
securityPackage="ntlm" authenticationLevel="call"
authenticationHandler="MyCompany.Security.AuthenticationHandler,
MyCompany.Framework" />
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
<clientProviders>
<formatter ref="binary" />
<provider
type="Microsoft.Runtime.Remoting.Security.SecurityClientChannelSinkProvider,
Microsoft.Runtime.Remoting.Security, Culture=neutral, Version=2.0.18.0"
securityPackage="ntlm" impersonationLevel="identify"
authenticationLevel="call" />
</clientProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>

We are running into some issues trying to talk to a component on Server 2000
from a component on XP. Basically the authentication fails. Here is the
exception:
System.Runtime.Remoting.RemotingException: An error occurred while
processing the request on the server:
Microsoft.Security.SSPI.SSPIException: AcceptSecurityContext failed. Error
Code = '80090304'.

at Microsoft.Security.SSPI.ServerContext.Accept(Byte[] inToken)
at
Microsoft.Runtime.Remoting.Security.ServerStates.ClientTokenProcessingState.ProcessClientToken(

I can't find any info regarding this exception. The work around we have is
to reset the password from the XP machine. Our client is not too happy with
the solution. I will appreciate any info that might help us to solve this
issue.