Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat not allowing other machine clients

 
Ankur Gargg
Ranch Hand
Posts: 55
Java jQuery Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ranchers

I deployed an application succesfully on Tomcat6.
I am able to access it using http://localhost//first/index.html

Howevere when I atry to access from other machines using URL
http://169.144.15.4/first/index.html(where this is my ip on which tomcat server is started)
I get operation timed out.
Can anyone tell me what I need to change and where?

Thanks
Ankur Garg
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13056
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The first thing to suspect is a firewall on your server machine.

Bill
 
Ankur Gargg
Ranch Hand
Posts: 55
Java jQuery Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I allowed incoming requests on port 80 on server.

I read somewhere some changes in server.xml.

But somehow not able to reach to the changes that need to be done..
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18012
47
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As it comes from the factory, Tomcat doesn't listen on port 80, it listens on port 8080. And yes, that is set in the server.xml file.

However, you cannot just change server.xml. On many OS's, port 80 (all ports < 4096) is a privileged port and the only applications that can use it have to have root privileges. Since Tomcat cannot jail itself, that means that a Tomcat running on port 80 is a serious security risk.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic