Discussion:
[openjms-developer] rmi port and firewall problems-- inside firewall is OK send/receive
Luke P Immes
2004-01-27 21:56:53 UTC
Permalink
I am having difficulty connecting to jms server from OUTSIDE of
firewall.
I have 2 computers behind a firewall, 192.168.0.2 acting as receiver
and has jms server.
192.168.0.3 acts sender, for test. (Yes, I double checked these IP
numbers-- they are correct)
Note that these IPs are not public to the internet at large, nor should
they be.

Netgear firewall, 192.168.0.1, maps: incoming request on at
216.195.1.39 on port 1099 to 192.168.0.2
216.195.1.39 is a public ip (mine), and web server works just fine, to
verify ip is valid.
The mapping mechanism works just fine, because a web server (/= jms)
runs on 192.168.0.2, works
as expected. The web server host is listening on 192.168.0.2:8080.


openjms.xml file
Tim Anderson
2004-01-30 02:04:17 UTC
Permalink
This should have been sent to the openjms-user list.

You need to use the tcp connector rather than rmi, and
configure the <TcpConfiguration/> element in openjms.xml.

E.g
<Connectors>
<Connector scheme="tcp">
<ConnectionFactories>
<QueueConnectionFactory name="QueueConnectionFactory" />
<TopicConnectionFactory name="TopicConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>
...
<ServerConfiguration host="216.195.1.39"/>
<TcpConfiguration internalHost="192.168.0.2"/>

See http://openjms.sourceforge.net/config/reference.html#TcpConfiguration
for more details.

-Tim

-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net [mailto:openjms-developer-***@lists.sourceforge.net]On Behalf Of Luke P Immes
Sent: Wednesday, 28 January 2004 8:57 AM
To: openjms-***@lists.sourceforge.net
Subject: [openjms-developer] rmi port and firewall problems-- inside firewall is OK send/receive


I am having difficulty connecting to jms server from OUTSIDE of firewall.
I have 2 computers behind a firewall, 192.168.0.2 acting as receiver and has jms server.
192.168.0.3 acts sender, for test. (Yes, I double checked these IP numbers-- they are correct)
Note that these IPs are not public to the internet at large, nor should they be.

Netgear firewall, 192.168.0.1, maps: incoming request on at 216.195.1.39 on port 1099 to 192.168.0.2
216.195.1.39 is a public ip (mine), and web server works just fine, to verify ip is valid.
The mapping mechanism works just fine, because a web server (/= jms) runs on 192.168.0.2, works
as expected. The web server host is listening on 192.168.0.2:8080.


openjms.xml file
Luke P Immes
2004-02-01 23:47:03 UTC
Permalink
Tim,
Thank you for the new configuration. This seems llike a good solution,
and external ip and
internal ip. But, I tried this, and still
"host refused" from sender

If I place the receiver machine, outside of a firewall, at
ip=216.195.1.39
and sender is on same cpu at Ip= 216.195.1.39.
then sender and receiver code work as expected.
ip=localhost will work as well (as expected). I have not been able to
test when sender is a distinct public IP, becasue
I need access to one, furthermore my webserver requires firewall
configuration in order to work, which is how another
sender ( /= 216.195.1.39)
can access sender code (via java webstart).

So, what are my options? Run jms outside a firewall?
Thanks for your time. Any help would be appreciated.


On Thu, 2004-01-29 at 21:04, Tim Anderson wrote:


This should have been sent to the openjms-user list.

You need to use the tcp connector rather than rmi, and
configure the <TcpConfiguration/> element in openjms.xml.

E.g
<Connectors>
<Connector scheme="tcp">
<ConnectionFactories>
<QueueConnectionFactory name="QueueConnectionFactory" />
<TopicConnectionFactory name="TopicConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>
...
<ServerConfiguration host="216.195.1.39"/>
<TcpConfiguration internalHost="192.168.0.2"/>

See
http://openjms.sourceforge.net/config/reference.html#TcpConfiguration
for more details.

-Tim


-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net
[mailto:openjms-developer-***@lists.sourceforge.net]On Behalf
Of Luke P Immes
Sent: Wednesday, 28 January 2004 8:57 AM
To: openjms-***@lists.sourceforge.net
Subject: [openjms-developer] rmi port and firewall problems--
inside firewall is OK send/receive


I am having difficulty connecting to jms server from OUTSIDE of
firewall.
I have 2 computers behind a firewall, 192.168.0.2 acting as
receiver and has jms server.
192.168.0.3 acts sender, for test. (Yes, I double checked these
IP numbers-- they are correct)
Note that these IPs are not public to the internet at large, nor
should they be.

Netgear firewall, 192.168.0.1, maps: incoming request on at
216.195.1.39 on port 1099 to 192.168.0.2
216.195.1.39 is a public ip (mine), and web server works just
fine, to verify ip is valid.
The mapping mechanism works just fine, because a web server (/=
jms) runs on 192.168.0.2, works
as expected. The web server host is listening on
192.168.0.2:8080.


openjms.xml file
rmi configuration 192.168.0.3 port 1099
Tim Anderson
2004-02-02 02:20:16 UTC
Permalink
Did you open up port 3030 and 3035 in your firewall?

-Tim
-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net [mailto:openjms-developer-***@lists.sourceforge.net]On Behalf Of Luke P Immes
Sent: Monday, 2 February 2004 10:47 AM
To: openjms-***@lists.sourceforge.net
Subject: RE: [openjms-developer] rmi port and firewall problems-- proposedsolution still not working


Tim,
Thank you for the new configuration. This seems llike a good solution, and external ip and
internal ip. But, I tried this, and still
"host refused" from sender

If I place the receiver machine, outside of a firewall, at ip=216.195.1.39
and sender is on same cpu at Ip= 216.195.1.39.
then sender and receiver code work as expected.
ip=localhost will work as well (as expected). I have not been able to test when sender is a distinct public IP, becasue
I need access to one, furthermore my webserver requires firewall configuration in order to work, which is how another
sender ( /= 216.195.1.39)
can access sender code (via java webstart).

So, what are my options? Run jms outside a firewall?
Thanks for your time. Any help would be appreciated.


On Thu, 2004-01-29 at 21:04, Tim Anderson wrote:

This should have been sent to the openjms-user list.

You need to use the tcp connector rather than rmi, and
configure the <TcpConfiguration/> element in openjms.xml.

E.g
<Connectors>
<Connector scheme="tcp">
<ConnectionFactories>
<QueueConnectionFactory name="QueueConnectionFactory" />
<TopicConnectionFactory name="TopicConnectionFactory" />
</ConnectionFactories>
</Connector>
</Connectors>
...
<ServerConfiguration host="216.195.1.39"/>
<TcpConfiguration internalHost="192.168.0.2"/>

See http://openjms.sourceforge.net/config/reference.html#TcpConfiguration
for more details.

-Tim

-----Original Message-----
From: openjms-developer-***@lists.sourceforge.net [mailto:openjms-developer-***@lists.sourceforge.net]On Behalf Of Luke P Immes
Sent: Wednesday, 28 January 2004 8:57 AM
To: openjms-***@lists.sourceforge.net
Subject: [openjms-developer] rmi port and firewall problems-- inside firewall is OK send/receive


I am having difficulty connecting to jms server from OUTSIDE of firewall.
I have 2 computers behind a firewall, 192.168.0.2 acting as receiver and has jms server.
192.168.0.3 acts sender, for test. (Yes, I double checked these IP numbers-- they are correct)
Note that these IPs are not public to the internet at large, nor should they be.

Netgear firewall, 192.168.0.1, maps: incoming request on at 216.195.1.39 on port 1099 to 192.168.0.2
216.195.1.39 is a public ip (mine), and web server works just fine, to verify ip is valid.
The mapping mechanism works just fine, because a web server (/= jms) runs on 192.168.0.2, works
as expected. The web server host is listening on 192.168.0.2:8080.


openjms.xml file

Loading...