I'm just catching up on this thread, so pardon me if I've missed something.
If I understand your situation, at least one of your problem scenarios is when you pass an MBRO object as an input parameter to a remote method. When you do this, the client-side remoting runtime will marshal the object reference over to the server, where it is unmarshaled to build a proxy that the server can use to callback to the client through. When this type of thing fails on different machines, but works on the same machine, it's usually the result of having the client- & server-side code sitting on different sides of a firewall or network address translation (NAT) device like a router that's doing IP address translation. Can you give us a little more detail about the network topology? -Mike http://www.bearcanyon.com > > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Rebecca Lohr > Sent: Friday, September 12, 2003 8:42 AM > To: [EMAIL PROTECTED] > > Richard et al, > > When the call fails, I get an exception saying that an > internal error > occurred: > > System.Runtime.Remoting.RemotingException: Server encountered > an internal > error. For more information, turn on customErrors in the > server's .config > file. > > Server stack trace: > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
