Unable to keep external IP

Hi

We are testing a Stand Alone application connecting to a remote (thru internet) EJB module.

We had tested the application client on our network, and it did worked fine. When trying to run the client on the remote computer we received an Exception message (IOP00410201). We did a basic configuration, which includes setting our ADSL modem/router to redirect port 3700 to the SJAS server and changed the remote application client InitialContext properties,

Properties were changed as follow:

properties.setProperty("java.naming.factory.initial",

"com.sun.enterprise.naming.SerialInitContextFactory");

properties.setProperty("java.naming.factory.url.pkgs",

"com.sun.enterprise.naming");

properties.setProperty("java.naming.factory.state",

"com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");

properties.setProperty("org.omg.CORBA.ORBInitialHost", sicflex.no-ip.com);

properties.setProperty("org.omg.CORBA.ORBInitialPort", 3700);

The received exception: IOP00410201 (COMM-FAILURE), displays the server's network ip: 192.168.1.2, which is unreachable from an external connection.

It seems that after stablishing initial communication, our server notifies the remote client with a new Ip address (the server's internal ip).

How can we keep the connection that we had stablish at InitialContext?

Thanks

Federico

[1423 byte] By [freddyforjavaa] at [2007-11-27 6:38:14]
# 1

We took the converter example from the tutorial, and ran on remote client using appclient (yes, we've set the config/sun-acc.xml).

First we try with port closed 3700, the corba exception shows a correct attempt to connect.

WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_C

LEAR_TEXT; hostname: sicflex.no-ip.com; port: 3700"

hostname is right

then we've opened the port and got the same error, but different hostname

WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_C

LEAR_TEXT; hostname: 192.168.1.2; port: 3700"

We made a simple port redirector and run it on the remote machine, and what we find out is that corba sends back the context with the WRONG hostname. So the initial communication is established but afterwards the client will not be able to connect to the port again, cause is unavailable.

Any ideas?

freddyforjavaa at 2007-7-12 18:06:50 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...