Linux – Access to Service from Remote and Local JBoss 7

jbosslinuxnetworking

I have two different servers (i.e. a tomcat on port 8082 and a jboss on port 9080) on a Suse Linux machine. The first one has been installed some time ago and the second one I just installed recently. Now I have problem to access the second one from another machine.

If I look at the netstat output there is a difference:

user@server:/etc> netstat -l -n|grep 8082
tcp 0 0 :::8082 :::* LISTEN
ser@server:/etc> netstat -l -n|grep 9080
tcp 0 0 127.0.0.1:9080 0.0.0.0:* LISTEN

it seems that the 9080 server is restricted to 127.0.0.1 whereas the first one has :::.

UPDATE:

I changed the standalone.xml configuration file from

<interface name="public">
    <inet-address value="127.0.0.1"/>
</interface>

to

<interface name="public">
    <any-address />
</interface>

but there is still a difference when I call netstat, and I can still not connect to the server from remote:

netstat -l -n |grep 9080
tcp        0      0 0.0.0.0:9080            0.0.0.0:*               LISTEN

Where does this difference originate and what is the semantic of this difference?

Best Answer

JBoss 4.2 and later only listens on localhost by default, you need to add -b 0.0.0.0 to your run.sh launcher (init scripts etc) to make it listen on all available interfaces.

Related Solutions

Linux port not accessible from remote machine

My guess is it's a firewall issue. To diagnose, either switch to root or use sudo to execute these commands described below:

Firstly, service iptables status will show you your current rules. Depending on how esoteric your firewall rules are, you may need to add them into the main question to debug but essentially you're looking for a line that accepts TCP port 8800 prior to a line that rejects all connections.

e.g.

Table: filter
Chain INPUT (policy ACCEPT)
num  target     prot opt source       destination
...
14   ACCEPT     tcp  --  0.0.0.0/0    0.0.0.0/0      state NEW tcp dpt:8800
15   REJECT     all  --  0.0.0.0/0    0.0.0.0/0      reject-with icmp-host-prohibited

If you don't have a REJECT line on your input chain, then the firewall is probably already turned off.

One way to get around this is obviously to turn off the firewall (service iptables stop) although this defeats the entire purpose of having a firewall.

If you need to add a new firewall rule, you have a couple of options:

Use the excellent Firewall Configuration tool (system-config-firewall) that ships with Fedora and can be found at the System->Administration->Firewall menu item in Gnome.
On the command line, insert a new rule before the REJECT rule by executing the following (uses numbers from my example above): iptables -I INPUT 15 -m state --state NEW -m tcp -p tcp --dport 8800 -j ACCEPT. NOTE that these changes are not permanent and will not persist beyond the next reboot.
Manually edit the /etc/sysconfig/iptables file and add a rule (-A INPUT -m state --state NEW -m tcp -p tcp --dport 8800 -j ACCEPT) to the firewall prior to the REJECT rule. Cycle the firewall service to pick up the changes via a service iptables restart. These changes will be applied every time the firewall service is started.

Windows – Dell M6600: “No internet access”, can browse internet, can remote into it, cannot activate office 2013, cannot join domain

Dealing specifically with the "No Internet Access" message, Windows uses NCSI (Network Connectivity Status Indicator) for this. This checks two things:

A request for http://www.msftncsi.com/ncsi.txt - Page called ncsi.txt containing the following line of text with no terminating new line or other non-printing characters: Microsoft NCSI
A request for DNS name resolution of dns.msftncsi.com - Resolution of the DNS name to: 131.107.255.255

If either of these fail, you get the "No Internet Access" message. I would guess that Office isn't even trying to register at this stage, you're getting a stock message based on NCSI having failed. I'd fix the NCSI issue first then try and register Office again.

Related Topic