Unable to reach client pc on certain ports

[sbuster]

I have a simple home network with a windows and fedora clients. I'm running fedora 13, but I"m having problems connecting to the pc on certain ports from my windows pc. I can connect from windows to fedora using VNC, and even connect to my postgresql database. However, can not get connected to my Apache Tomcat or JBoss server.

When I first installed the OS I went through and configured the firewall but have since disabled it (stopped service). However, I still can't get to the app/web servers.

Not sure what to do.

Thanks

[Keldorn]

Hi!
Please show

netstat -tunpl

output

[sbuster]

you want me to run this from the linux or windows pc?

[Keldorn]

on linux -)

[xprezons]

JBoss and Tomcat need to be told to listen to the external interface as well. AFAIK, by default, they start up to listen to the loopback interface only. Have a look at the JBoss / Tomcat startup script to be sure.

JBoss startup command org.jboss.Main -b <IP address> (specify the bind address)

Another option - http://ubuntuforums.org/showthread.php?t=1039140 [use this only to test. This approach is not recommended as a long term solution.]

[sbuster]

Ok, so this seems to be specific to JBoss. I updated my hosts fle (as indicated in the other post) but still can't seem to get to the web server even if I initiate the request (http://192.168.1.102:8080) on the same linux pc (ie, connecting to itself). I've obviously got something wrong in my network device.

hosts file:
127.0.0.1 localhost.localdomain localhost linux
192.168.1.102 localhost.localdomain localhost linux

[jpollard]

I would suggest removing the names associated with 192.168.1.102
entry. the name localhost is/should be reserved for the local host interface,
127.0.0.1. Giving both IP numbers the same name can cause some confusion, as some utilities will do a reverse lookup to try and verify
the name... and here, they can get confused.

Second, some configuration files (such as apache) will get the wrong
IP number when you want it to use the external IP number (the 192.168...
will not be located using a host name).

[xprezons]

Originally Posted by jpollard

Giving both IP numbers the same name can cause some confusion, as some utilities will do a reverse lookup to try and verify
the name... and here, they can get confused.

Thanks for pointing out, jpollard. Sorry, I should have added that caveat in the first place. It's in there now.

@sbuster It's also worth posting the output Keldorn suggested.
Can you access Tomcat / JBoss using the loopback URL (http://localhost:<port>)?
Can you see the startup log for Tomcat / JBoss? Can you put it up somewhere like PasteBin?