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
Cheers,
Sacha
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Giorgio Ponza
> Sent: vendredi, 21. mars 2003 11:00
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JBoss behind firewalls
>
>
> SOrry, i'm only a programmer, so i have to ask to the person.
> I know the pc has an internal IP that is mapped outside with
> another IP
> (public)
> Have i to ask more to the sys admin?
>
> tx for answer
> Giorgio
>
>
> From: "Sacha Labourey" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, March 21, 2003 10:20 AM
> Subject: RE: [JBoss-user] JBoss behind firewalls
>
>
> > What do you do with your firewall? i.e. you simply block
> ports or you also
> > do some kind of NAT (static, dynamic, etc.)?
> >
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
