• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Devaka Cooray
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Saloon Keepers:
  • Tim Holloway
Bartenders:

Wrong IP address

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a Tomcat 6 running on port 8080 of the IP 192.168.1.250, this server is accessed by users on the local network via the internal IP and external access create a firewall redirection for access via port 9080 to be redirected to the 8080 192 168 .1.250.

Until then everything running smoothly, if not for the fact that a user who is accessing the application from outside the local network, using the public IP on port 9080, begins to receive Time out errors that "192.168.1.250 The server took too long to answer. "

That is, an external network user receives pages that link to the internal IP.

First doubt this is a problem Firewall or Tomcat?

Second question, how to prevent this from happening?
 
My pie came with a little toothpic holding up this tiny ad:
Paul Wheaton's 16th Kickstarter: Gardening playing cards for gardeners and homesteaders
https://coderanch.com/t/889615/Paul-Wheaton-Kickstarter-Gardening-playing
reply
    Bookmark Topic Watch Topic
  • New Topic