You might try the brute force approach of reversing the interfaces, such
that the external IP is on eth0 and the internal IP is on eth1. Many
processes which are not multiple interface-aware will simply pick up the
address of the first interface they find. Note that this does not involve
reversing the physical cards or wires, just the interface labels.
Is your DNS valid and consistent, both forward and reverse?
As a general rule, when a machine is addressable by more than one IP
address, we like to configure DNS for an identical perspective both inside
and outside the firewall. The way we usually do this is by suffixing the
letter "i" and "e" to the respective hostname component. That is, for a
machine whose hostname is "aaa001," we would define in the zone file a
name "aaa001-i" which maps to the internal address only and a name
"aaa001-e" which maps to the external address only. We regard this is
enormously preferable to having desynchronized DNS zones, which is how
most people handle the situation. (This is especially important if there
are cryptograpic protocols in use, as with SSH, which will try to validate
the hostname, but that is beyond the scope of your problem with jBoss.)
Does the application work from outside if you put the internal interface
down before starting your services? Then the external interface would be
forced to be the first enumerated interface.
You may need to specify the RMI server address manually when starting Java
on the server if the system guesses wrong, editing run.sh:
java -Djava.rmi.server.hostname=212.172.122.17 ...
This is something of an RMI FAQ, and would be applicable to any situation
where multiple interfaces or even virtual interfaces with different IP
addresses are involved:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html#nethostname
Clearly, "no route to host" is a correct error message for an address like
192.168.0.100, which is a "fake net" guaranteed to be publicly unrouteable
by RFC1918/BCP0005. The problem is why the client is attempting to
connect to this IP address in the first place, and that seems almost
certain to be related to one or another of the directory services. If you
can look at the client's network table and see what port on the
unreachable address is being attempted, you should be able to see whether
this is related to web access (port 80 or 8080), in which case DNS is
likely at fault, or related to Java internals such as RMI (port 1099) or
JNDI (port 4444), in which case you have a property set wrong. At this
point, it is hard to tell from your description what sort of connection is
actually failing without more detailed information.
-- Mike
On 2001-06-22 at 11:21 +0200, Patrick Buchinger wrote:
> hi everybody!
>
> i have a server with 2 network cards in it, one is connecting to the
> internal network (let's say ip=192.168.0.100) and one is connecting to
> the internet (let's say ip=212.172.122.17).
> the os of the server is linux (kernel 2.2.16). the server also is the
> gateway from the internal network to the world (using NAT).
>
> now the problem is, when i try to connetct to jboss from outside the
> internal network (to ip 212.172.122.17), i always get a
> NoRouteToHostException to host 192.168.0.100!!??!!!
> is this a jboss problem or a server configuration problem? has someone
> ever made such a configuration successfully run with jboss?
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
