No, I guess that is the problem. The proxy embeeds the ip address of the server (to be able to remotly contact it) AS SEEN by the server, not the client. As both IP are different, it fails.
One solution would be to set the java.rmi.server.hostname property to a HOSTNAME (and NOT an IP address) on the JBoss server and have this hostname resolve correctly to an IP address on both the local net and the remote net (each net has its own resolution protocol).
Local machine may resolve MyServer to 192.168.1.1 and remote machine may resolve MyServer to 194.35.94.34
Sacha, we are still using 2.4.3, so the story may have changed. But aren't the ports defined in the various config files just used to do lookups and establish a connection? We found that when a client actually invokes a method on an EJB, that happens on a per-instance defined high-numbered port, like 32436. This makes it almost impossible to firewall, since all high-numbered ports have to be open. To my knowledge (which admittedly isn't that great in this area), I thought RMI worked like many TCP protocols: "you contact me on this well known port, and I'll let you know the random port number over which we will converse henceforth."
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
