This forum will be moving into a limited support mode where the product team will not be actively looking into posts from this forum. Feel free to use this forum to ask any questions you have on this technology to the community of the forum. As well, if you have concerns on this please post a comment and we may re-evaluate this decision.

Below are some of the top resources on .NET Remoting for you to use:

· MSDN SDK for Remoting

· File a Connect bug on .NET Remoting

· Best Practices for .NET Remoting

· Articles on .NET Remoting

· Top .NET Remoting books

· Top Blogs:

o Remoting Team Blog

o Manish Godse’s Remoting Blog

If you encounter a blocking issue please contact our support team here.

Some common problems encountered using .NET Remoting:

· No connection could be made because the target machine actively refused it

o A firewall is blocking the request.

o The server is not listening on the machine/port the client is trying to connect to.

· The input stream is not a valid binary format.

o The client and the server are configured with different formats (SOAP vs Binary)

o IIS sends back an error message as plain text which the binary formatter doesn't know how to handle. Try changing the formatter to SoapFormatter to solve IIS configuration issues.

· Server callingback to a client does not work

o Set TypeFilterLevel in the FormatterSinkProvider to full

o Take a look at: http://blogs.msdn.com/dotnetremoting/archive/2006/04/07/571020.aspx

· Everything works great for a while. Then after six or seven minutes I get the following exception

o Server Object TTL has expired

o Take a look at: http://msdn2.microsoft.com/en-us/magazine/cc300474.aspx#edupdate

· An Exception occurs when calling myServerObject.GetLifetimeService()

o Set TypeFilterLevel to full in the FormatterSinkProvider

· Multiple channel of same transport. (e.g Http unsecure and Secure). How do I custom pick a channel

o This is very difficult to predict. Try using different priorities

o Also try taking a look at: http://blogs.msdn.com/mahjayar/archive/2007/09/15/custom-pick-a-remoting-channel-based-on-remote-object-uri.aspx

· My client tries to use IPCClientChannel to connect to object on a different machine.

o Take a look at : http://blogs.msdn.com/mahjayar/archive/2007/09/23/implications-of-using-ipcserverchannel-when-connection-from-remote-clients.aspx

The complex and difficult topic like remoting should not be moved to limited support mode.

Couldn't agree more.

I don't believe that was a correct decision since in the business we have scenarios and situations where WCF is unable to support,such as this.