Hi Yves, I guess I have some bad news for you. Oh and you know about "don't shoot the messenger" ...
What you are trying to achieve is not possible with the supplied communication channels (TcpChannel or HttpChannel) because the connection from the server to the client will quite likely be blocked by the client's firewall or http proxy. It should however be possible to design and develop a two-way remoting channel - something I have on my definite todo list for the future ... Sorry for the bad news, -Ingo Author of "Advanced .NET Remoting" http://www.dotnetremoting.cc > -----Original Message----- > From: Yves Gagnon [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 28, 2002 8:00 PM > To: [EMAIL PROTECTED] > Subject: [DOTNET] REMOTING problem inside and outside a network > > > Hi, > > I have a problem to know how to work around a remoting > problem. I have a > client who connects to a server application outside a network (by > internet) and the client transfer to the server an object (marshing > object) who contains a reference to an interface of an other object > inside the client. The server uses this interface to communicate with > the client. The connection process worked fine, but when the server > tries to communicate with the client we received an error message. > > I know that the problem come with the ip address of the client remote > object that is the one inside the network and this address is not > recognize outside the network. The question: how to be able > to construct > the remote object to be able to contains a valid connection for the > server ? > > Thank you > > Yves Gagnon > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
