Yves, Might be 100% of nothing to do with your problem but...
Something I learnt the hard way about remoting (and in my case events, in your case callbacks?) is that you have to have all the assemblies for the client objects on the server side also - otherwise it has no "reference" to the assembly type it is calling back into. It gave me "file not found" exceptions - not sure what error you are getting - you didn't say. HTH Dino -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Yves Gagnon Sent: Wednesday, 29 May 2002 06:00 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 ? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.365 / Virus Database: 202 - Release Date: 24/05/2002 You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
