File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JBoss/WildFly and the fly likes JNDI lookup problem from remote client present in External Network Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "JNDI lookup problem from remote client present in External Network" Watch "JNDI lookup problem from remote client present in External Network" New topic
Author

JNDI lookup problem from remote client present in External Network

ved gunjan
Ranch Hand

Joined: May 17, 2003
Posts: 86
Hi,

We are using JBoss 4.0.5.GA as our application server.

The scenario is like this.

Machine A) IP Address: 192.168.XXX.YYY. [It's the Server] On this Machine Jboss4.0.5.GA and MySQL are running.

The outside system (basically the external clients) refers to this machine through address 220.225.ZZZ.XXX. This is the public ip address.
i.e the external_host_name = 220.225.ZZZ.XXX.

Machine B) it's an external client. It is looking up for service which is running on Machine A through JNDI.
In the client code, the jndi provider URL is set up to "jnp://220.225.ZZZ.XXX:1099" when the initial context is created for the RMI access.

The client code which is running on Machine B) is doing a lookup for the service, using the following jndi.propterties:
Code:

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming rg.jnp.interfaces
java.naming.provider.url=jnp://220.225.ZZZ.XXX:1099

The two machines are running on different network.

When am running the code on the Machine B), and trying to access the service running on Machine A), it is throwing java.naming.CommunicationException: connection refused, cannot connect to url: 220.225.36.247.

Can any one guide me as to where we are going wrong and whether we are missing any setting in the JBoss Server?

I need this fix very urgently...please guide be to the solution.

Thanks and Regards.
Ved.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10067
    
163

the external_host_name = 220.225.ZZZ.XXX


Does



work from Machine B?

If it doesnt, then it might be a firewall issue.


[My Blog] [JavaRanch Journal]
ved gunjan
Ranch Hand

Joined: May 17, 2003
Posts: 86
Hi,
Yes telnet is working from machine B.
But still it is not able to listen.
What can be the problem and possible solution. Is there any server setting that needs to be configured.

Regards
Ved
Faisal Ahmed Siddiqui
Greenhorn

Joined: Jan 03, 2002
Posts: 29
make sure port#1100, through which RMI communication taken place, is opened.
I had the same problem on LAN with different networks.


Architect<br />SCJP<br />SCWCD<br />IBM-486
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: JNDI lookup problem from remote client present in External Network