Secure TCP .NET Remoting Channel without Authentication

Question

I have a .NET 2.0 remoting application that needs to communicate between machines that may be on different domains or no domain at all. It is using the TCP channel.

Everything works fine until I enable encryption, then when connecting I get the error "The server has rejected the client credentials." I have done quite a bit of searching, and I have not been able to find a solution that works for me.

I have tried playing around with all kinds of channel settings and have not had any success.

My remoting object has its own built-in authentication, so I don't need Windows to do any kind of authentication.

Botton line question is:

"Can I enable encryption on a .NET remoting TCP channel without Windows trying to authenticate the client's credentials?"

Answer 1

After quite a bit of research I came to the conclusion that this can't be done without some major custom coding using .NET remoting.

I decided to move the project to WCF which does allow the use of SSL apart from any kind of authentication. After moving to WCF everything works like a charm.