How to make my localhost available over my Windows local network

[pgcohn]

Hi, I saw a similar posting on the forum, but since my problem is slightly different, I decided to open a new discussion.  I hope that´s ok.

I am developing and deploying an application on a Windows 7 based machine and I can access it only through "localhost" or 127.0.0.1. I cannot access it through the local IP address, i.e. 192.168.1.100.  Needless to say, I cannot access jboss AS from any other computers in my network.

Since I am still developing, I am using eclipse to launch the server and deploy the application.

Could you please advise on how to configure jboss as to allow local and remote connections by means of IP address on Windows ?

(I tried to execute "run.bat -b 0.0.0.0" from a command window as advised on the similar posting I mentioned above, but got the messages "Could not locate run.jar" and "Please check that you´re in the bin directory when running this script"... I was in the bin directory...)

Thanks,

Paulo

[nickarls]

is your JBOSS_HOME env var set?

[jaikiran]

Actually it's recommended not to set the JBOSS_HOME env variable. The run script sets it correctly. What however needs to be set is the JAVA_HOME environment variable (I guess, that's what Nicklas meant) and that should point to your JDK/JRE installation directory. What's the output of:

echo %JAVA_HOME%

[pgcohn]

Hi Niklas and Jaikiran,

both JBOSS_HOME and JAVA_HOME are set.  The output for JAVA_HOME is:

C:\Java\jdk1.6.0_23

and JBOSS_HOME:

C:\Users\Paulo\jboss-6.0.0.20100911-M5

Please note that I am able to run the server and I can run the application locally if I browse to "http://localhost:8080/myproject" or "http://127.0.0.1:8080/myproject".  The problem arises when I try to use the server´s IP address, e.g. 192.168.1.100, instead of localhost or 127.0.0.1.

Regards,

Paulo.

[nickarls]

192.168.x is a private block and isn't visible from external networks.

[pgcohn]

Thats´s right. I´m trying to connect from other computers in my local, internal network.

[peterj]

There must be a faulty path somewhere. The best way to locate it is to go into run.bat and comment out the "@echo off" statement in the first line, then run it again with the -b 0.0.0.0 (or -b 192.168.1.100). If from the output you get you cannot solve the problem, post the full command prompt output, starting from the command you entered.

[nickarls]

Is your network setup in any way special? Multiple network cards? Running inside a virtual machine etc? What does your ipconfig/ifconfig -a say?

[pgcohn]

Thanks Peter and Niklas ! That was right.  My JBOSS_HOME env var was unproperly set after all.

Regards,

Paulo

[peterj]

As Jaikiran noted, you should never set JBOSS_HOME - it will be set automatically to the proper value. (But that sort of makes me question why the run scripts allow JBOSS_HOME to be externally set...)

[pgcohn]

Hi, Nicklas. Nothing special in my network really. It´s a very small network that I use for development and tests. A wifi router connected to a cable modem and 3 PCs in the local network. That´s all.  It seems the whole problem was due to  JBOSS_HOME incorrectly set.  As soon as I fixed it, run -b 0.0.0.0 worked as you suggested. I have now removed the JBOOS_HOME variable as suggested by Jaikiran and Peter. Thank you for your help.

[pgcohn]

Yes, I removed the JBOSS_HOME definition altogether and it worked very well. I also wonder why the manual says at the very beginning that this variable should be set. Thank you for your help.

[nickarls]

I must confess I have always set JBOSS_HOME out of habit since I generally only use one version at a time and set it manually if I need to.