.NET Remoting switching channels by itself.

Posted by Casper on Stack Overflow See other posts from Stack Overflow or by Casper
Published on 2010-05-12T12:40:29Z Indexed on 2010/05/12 12:44 UTC
Read the original article Hit count: 343

Filed under:
|
|

Hi.

We are having an odd problem with .NET Remoting. Basically, we have a server which registers two TcpChannels with ChannelServices.RegisterChannel(): one listens on port 50000, the other one listens on port 15000. We then have a client that registers a TcpChannel to be able to communicate with the server. We retrieve a an object from the server by calling Activator.GetObject() with the URI "tcp://serverip:50000/objectname" and this works fine, the client connects to the server on port 50000 and gets the object. However, when we start calling methods on that object, the connection to the channel on port 50000 is dropped, and a new connection is made to the channel on port 15000 automatically. This poses a real problem for us since we don't want traffic on port 15000 because that channel may not be bound to the same network adapter as the port 50000 channel on the server or that port may not be open in the firewall, which causes the remoting calls to fail naturally.

This is very strange to us since the client has no knowledge in our code that there exists another channel on the server on port 15000 or what IP it listens on, yet it attempt to connect to it.

Any help on this is greatly appreciated, /Casper

c

© Stack Overflow or respective owner

Related posts about .NET

Related posts about remoting