I have an application (C#, but I don't think that matters) using the standard .NET remote object creation, using Activator.CreateInstance (Type, Object[], Object[]). It works perfectly when the client and server are both on machines with only one network interface enabled and on the same subnet, but I'm working on an upgrade which will require the client to have two active NICs, and be able to remote from a server on either NIC (or both). I thought since the third argument to CreateInstance is the URL of the remote object server, it would be able to determine the appropriate network interface to use, but the method call times out and throws a TargetInvocationException. I can see by running EtherPeek that no network traffic is going out on either NIC when the remote object request is made, so it looks like the framework is just plain confused.
The opposite setup (one server publishing a remote object on multiple NICs) is easy and works fine, but I can't get this setup to work at all. Has anyone ever seen a situation like this before, and if so, figured out how to convince .NET to send the request out the right interface? Thanks much, Andy
