After some discussions on Developmentor's DOTNET list, regarding the use of Windows Authentication in .NET remoting, I figured it should be possible to build a replacement TCP remoting channel that used the SSPI API during the connection phase to accomplish this. So, this is one of the things I'd like to try out in the coming weeks (that is, if I ever get some extra free time).

OTOH, SSPI is one of those APIs that fall under my horrible APIs category [1], so I'm not precisely thrilled about the prospect... but even so, using my WSSPI library should make it much easier.
While I get that time, I'm going through Jonathan Hawking's NamedPipeChannel sample, and waiting on Ingo Rammer's Advanced .NET Remoting book. Damn that's one I really could use right now... thank god it's coming out this week!

[1] Keith Brown might disagree, though...

Tomas Restrepo

Software developer located in Colombia. Sr. PFE at Microsoft.