.NET Remoting Client's Problem when running on the machine with Multi NICs

Question

I built a .NET Remoting Client which works quite fine on the machine of single NIC, and lots of testing messages received via remoting event.

But when additional NIC was added, the Client seemed to be able to connect the remoting Server, but the testing messages cannot arrive anymore.

From debugging, the server end did trigger the event but the client didn't get that. Checking from google and find that a similar problem report: http://www.eggheadcafe.com/community/aspnet/2/10061570/reply.aspx

I just wonder if any solutions?

Thanks in advance!

Answer 1

This was some problem for me also.

The nature of this problem is how client registers the event handlers on the server. When adding an event handler the client is sending the IP address of the "binded" address. This is static non public field in the TcpChannel class (thank you reflector). You need to explicitly bind the client to the ip address that the server will be able to reach. The config file for the client should be something like this.

<channel ref="tcp" port="0" bindTo="your.ip.address.here" >